django-oauth-toolkit VS django-graphql-auth

View on GitHub

Just to be clear: I'm asking for LDAP to be one possible choice. If an installation wants to use LDAP BIND they can use that, or if the want to use SAML they could use that, or OATH. But not at the same time: you get to choose one.

Django Authentication system for example has a User object that allows different backends to feed into it:

* https://django-auth-ldap.readthedocs.io/

* https://django-oauth-toolkit.readthedocs.io/

* https://stackoverflow.com/questions/22668434/saml-with-djang...

You would need to store whatever identifier the oauth provider gives you along with access and refresh tokens. That said, I wouldn't try to implement this from scratch, since it is not trivial. Try django-oauth-toolkit

Thankfully you don't need to implement this giant standard yourself. You can use the excellent Django OAuth Toolkit package. They also have a specific section in their documentation for using it with DRF.

I would suggest token auth as it is stateless, secure and can be used on multiple devices. OAuth/OAuth2 is the industry standard at the moment but you can also use a simple JWT token signature. On top of this, Django REST framework offers a lot of libraries for this purpose e.g. django-rest-framework-simplejwt, django-rest-framework-social-oauth2, django-oauth-toolkit, and more.

We use Django extensively in our platform to run many different aspects of our business. We use our own platform to build, pack and deploy our Django-based Single-Sign-On Identity Service that is based on this open-source: https://github.com/PedroBern/django-graphql-auth

After reading about the differences between JWT and the default DB based session mechanism which Django uses the latter seems the safest and simplest in many respects. Without graphql, logging in and signing up is easy with the default django forms and views. With graphql, I wasn't sure. In my research for handling authentication with graphql I stumbled upon django-graphql-auth (https://github.com/PedroBern/django-graphql-auth) but it seems to be based on jwt. I cannot seem to find anything else similar which supports the default django session mechanism.