Skip to content
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

Authorization Code Grant #28

Open
ProbablePrime opened this issue Feb 9, 2017 · 3 comments
Open

Authorization Code Grant #28

ProbablePrime opened this issue Feb 9, 2017 · 3 comments

Comments

@ProbablePrime
Copy link

The OAuth 2 Authorization Code Grant appears to not be implemented?

Is this on the roadmap?

Spec: https://tools.ietf.org/html/rfc6749#section-4.1

@ctrix
Copy link

ctrix commented Mar 3, 2017

+1 for this.

@svrooij
Copy link

svrooij commented Apr 27, 2017

The code grant might not be implemented by design!

The code grant requires the client to be able to keep the secret SECRET, hence the name. A client-side application cannot keep this secret a secret. The code grant flow is designed for server-side applications, like a PHP application.

@PostImpatica
Copy link

@svrooij @ProbablePrime Actually the new recommendation for SPA's is that you use the Authorization Code grant type but leave off the last step of requesting a token with the secret. See this article: OAuth2 Simplified

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants