opened
boris-petrov1214
username_0
linkedin announced the breaking change in their developer program, will that affect the library?
issue
created
xeroxoid
username_1
It seems that it has...
comment
created
xeroxoid
username_1
So to get your app to work you have to limit your scope to the now allowed permissions. i.e.:

````javascript
  ...
  linkedinStrategy = new LinkedInStrategy({
      clientID: config.linkedin.clientID,
      clientSecret: config.linkedin.clientSecret,
      callbackURL: config.linkedin.callbackURL,
      scope: ['r_basicprofile', 'w_share', 'r_emailaddress' ],
      passReqToCallback: true
    },...
  ...
````

So no more leeching on them profiles :)
comment
created
sidonaldson
username_2
Yup, so "r_contactinfo" is now allowed only for authorised partners. I guess they want you to still use linkedin ;)
comment
created
chewedon
username_3
I'm using Sailsjs. 

The call to: 

    login: function(req, res) {		
		passport.authenticate('linkedin', function(err, user, info) {
			// The request will be redirected to LinkedIn for authentication, so this 
    		        // function will not be called. 
		});
    }

Does not redirect the user to the Linkedin login prompt for the user to enter email and password, could it be related to Linkedin's server changes or am I using this library in a wrong way ?

At the moment, my browser just hangs there, spinning and never completing the request for an access token.
comment