django-allauth VS django-oauth-toolkit

If you don't want to use Pegasus or another paid product (presumably because of the cost), the packages I'd reach for are django-allauth for login/user stuff and dj-stripe for the Stripe integration. As for teams, there wasn't a library I was happy with so I rolled my own for Pegasus, but some people like django-tenants. It's too heavyweight for my taste as it requires a more complex dev/test/infrastructure setup with Postgres schemas, as opposed to having a single-database and handling multitenancy in the application layer. But there are pros and cons to both approaches.

django-allauth - authorisation with email and social media accounts

Complete user authentication (Log-in/Log-out, ...) via Django Allauth

I've been screwing around with https://github.com/pennersr/django-allauth/. I got it up and running; was able to get Discord and Twich oauth2 working on it without much issue, Steam's OpenID implementation is really giving me a hard time though.

Usually when people talk about oauth with django, they mean letting users access a django app using oauth and django-allauth is often a good choice for that, but if you're accessing an API that doesn't sound like what you're after.

When I started web development with Django. I thoroughly didn't know about the django-allauth package. I had knowledge of MVC and some core parts of Django. During college projects I had been working on a demo project and done user authentication and all manually. That time one of my seniors advised me to use django-allauth. I did some research and configured django-allauth with my project within a couple of minutes. For me it was an invigorating thing.

Although the answer given below solved my problem, I just want to share that I ended up using django-allauth instead of social-auth. And the latest version of django-allauth appears to be the best Django authentication app.

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.