-
Notifications
You must be signed in to change notification settings - Fork 407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use /authenticate instead of /authorize #220
Labels
Comments
I do too. I have a branch that is refactoring the authentication workflow a bit since it's pretty outdated. So stay tuned |
Great. Looking forward to it! |
Has this been implemented? |
What about it ? |
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
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.
The text was updated successfully, but these errors were encountered: