Use /authenticate instead of /authorize

[hsukenooi]

I like /authenticate better because it'll automatically log people in who meet the criteria (below) rather than taking them to the Linkedin login dialog and asking for their credentials. That's only necessary the first time.

Taken from Linkedin's Blog Post: https://developer.linkedin.com/blog/oauth-now-authentication

This 'authenticate' endpoint functions identically to the authorization endpoint except for one scenario. If the following are all true:

1. The current user is logged into LinkedIn.
2. The current user has already granted an access token to the requesting application.
3. The access token has not expired.

Then we will automatically (and immediately) redirect to the callback URL you specify, without interruption. This provides a great user experience - just a one click login! If any of the above conditions are not true, the member will see the normal authorization flow.

[hexgnu]

I do too.

I have a branch that is refactoring the authentication workflow a bit since it's pretty outdated. So stay tuned

[hsukenooi]

Great. Looking forward to it!

[ghost]

Has this been implemented?

[lcezermf]

What about it ?

[hexgnu]

Hey All,

I don't actively maintain this project.

If you want to submit a Pull Request I can take a look or if someone wants to volunteer they can take over maintenance of this gem.