shortuuid VS django-allauth

Unlike many people here, I don't like to write hundreds of mediocre posts. Instead, I prefer very few posts, that unfortunately are still mediocre.

If you're tired of all the perfection that exists on the internet, where every piece is deeply insightful and changes your life, I'd encourage you to read my articles, which only promise to shorten it:

https://www.stavros.io/

I use shortuuid[0] for that stuff, which also omits the capital letter I, and has some other niceties (I wrote the library). It works really well, and I like how small the IDs are.

[0] https://github.com/skorokithakis/shortuuid

skorokithakis: developer of django-annoying and shortuuid

https://github.com/skorokithakis/shortuuid#usage

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.