-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
Oauth2 #1675
Comments
Okay - it's possible that we're at a point where we should move the built-in OAuth2 into a separately maintained repo given that there's now various options. Eg we might want to instead recommend Django OAuth toolkit as the default option since it's really well maintained and documented. In the meantime I'm going to close the issue as it's not a bug in REST framework - I'd suggest following up with @caffeinehit as the best option, or possibly starting a thread on the discussion group |
Thanks Tom! If I may have a word. I find |
Okay, noted. I don't currently use either, so useful to know. |
It's not a DRF issue.
But strictly related for those who'd like to use the out of the box Oauth2.
The original django-oauth2-provider has some issues with Django 1.7.
It still use minetype that is no more supported by Django 1.7
This guy posted a solution that worked for me: caffeinehit/django-oauth2-provider#84
But no one from @caffeinehit seems took in charge this issue.
Plus when I make an authentication it do not create and do not give me back the
"refresh_token"
. Maybe I'm missing something or maybe this is another bug using Django 1.7Thanks for your help and your great work!
The text was updated successfully, but these errors were encountered: