Our django based products have several APIs.

Some use DRF, some not.

Up to now the DRF based APIs use the authentication 
(authentication_classes) which gets explained here:
 
   http://www.django-rest-framework.org/api-guide/authentication/

The other APIs use Django.

Things work, there are no bugs. But I don't like the design/architecture.

Nevertheless I would like to have one way to do auth.

Solution Variant1: Use DRF for all API calls.

Solution Variant2: Do Auth exclusively via Django, do not use  
authentication_classes.

Solution Variant3: Convince the django core developers to integrate 
authentication_classes

Solution Variant4: Extract authentication_classes from DRF into a small 
re-usable app and use this.

What do you think?

Regards,
  Thomas Güttler

BTW: This is only about Auth, not about permission checking.

-- 
You received this message because you are subscribed to the Google Groups 
"Django REST framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-rest-framework+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to