-
Notifications
You must be signed in to change notification settings - Fork 259
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
authorize endpoint doesn't seem to support "token" response type (implicit grant) #119
Comments
@blag Thanks very much for letting me know. What is the likelihood that either of these fork owners will take over the PyPi component and update it? Isn't the PyPi version still based on cafeeinehit's repo? |
Eric please use this instead I should really remove myself from watching this everyone should just move On Wed, Feb 25, 2015 at 5:37 PM, Eric Swenson [email protected]
Mikela |
@blag why not just assign some maintainers, or transfer this to someone willing to continue it? I'd be interested if so. Thank you. |
Or maybe cc @andy-a . Not sure who owns this at this point. Thanks! |
@nicholasserra: You'd have to ask CaffineHit or one of their employees. I am not affiliated with them in any way, nor am I responsible for this project, and I don't have any permissions to do anything in this repo except create/comment on issues. I used this app once and I occasionally tell people to use other forks/projects. 😄 I am now using Django Oauth Toolkit and can attest that it's awesome! Highly recommended. |
@blag thanks for the info :D |
When response_type = token is provided to the authorize endpoint, the resulting redirect after authorization confirmation is a "code" (just like response_type=code). It would appear the implicit grant flow as described in section 4.2.1 of RFC 6749 is not implemented.
The text was updated successfully, but these errors were encountered: