Custom confirm template about django-oauth2-provider HOT 5 OPEN

You should be able to override provider/authorize.html template with the vanilla Django template override mechanisms. IIRC, the rest of the views simply return redirects or HTTP error codes, so there isn't much point in customizing those templates.

Please note that this project is dead - use Django OAuth Toolkit if you can. I am on mobile so please forbive me for any spelling errors and for not linking to DOT.

from django-oauth2-provider.

I found a way, overriding url and specifing my own template.

This line must be placed before oauth urls

url(r'^oauth2/authorize/confirm/?$', login_required(Authorize.as_view(template_name='oauth2/authorize.html'))),  # This one overrides template.
url(r'^oauth2/', include('provider.oauth2.urls', namespace='oauth2')),  # OAuth URLs

Actually I'm planning to switch to Oauth Toolkit since it has some options I need, I didn't know this project has dead. I'm using this since I found it in tastypie cookbook section.

from django-oauth2-provider.

Yep, that is the vanilla Django template override mechanism. 👍

Do you remember which section of the Tastypie, cookbook section that linked here? Sounds like their documentation could use an update.

Also, the Tastypie author has expressed some concerns with the future of Tastypie, so you may want to consider using an alternative REST framework like DRF or Restless.

from django-oauth2-provider.

Oh, I didn't know it's called "vanilla Django template override mechanism", good to know 👍

And about cookbok, they refer to an old tutorial here

Actually we're planning to migrate to django rest framework. But I'm still making some changes using old libraries meanwhile since project owner needs to show a demo soon.

from django-oauth2-provider.

It's not really called that, it's just the normal way to override templates with Django. I'll see what I can do about updating that documentation to point elsewhere. The fewer links to this (dead) project, the better.

And if anybody has the proper access, this issue can be closed.

from django-oauth2-provider.