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

authorize endpoint doesn't seem to support "token" response type (implicit grant) #119

Open
eswenson1 opened this issue Feb 24, 2015 · 7 comments

Comments

@eswenson1
Copy link

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.

@blag
Copy link

blag commented Feb 25, 2015

Duplicate of #42, and already solved with PR #59.

Also, this project is dead. If you would like to see any progress, please contribute issues and PR's to the two most lively forks:

Thanks!

@eswenson1
Copy link
Author

@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?

@glassresistor
Copy link
Contributor

Eric please use this instead
https://django-oauth-toolkit.readthedocs.org/en/0.7.0/

I should really remove myself from watching this everyone should just move
to toolkit its working for us great.

On Wed, Feb 25, 2015 at 5:37 PM, Eric Swenson [email protected]
wrote:

@blag https://github.com/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?


Reply to this email directly or view it on GitHub
#119 (comment)
.

Mikela

@nicholasserra
Copy link

@blag why not just assign some maintainers, or transfer this to someone willing to continue it? I'd be interested if so. Thank you.

@nicholasserra
Copy link

Or maybe cc @andy-a . Not sure who owns this at this point. Thanks!

@blag
Copy link

blag commented May 2, 2016

@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.

@nicholasserra
Copy link

@blag thanks for the info :D

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