Many of these auth systems are client/server, not going to be the simplest thing to configure the entire stack for simple projects/tutorials/testing environments and so on. I can definitely see having.a pluggable alternative to the contrib.auth package that implements all the client-side stuff, though. When setting up or modifying a project, select the alternative package, and be as agnostic as possible about the auth server-side; a service like Auth0 or AWS Cognito if someone has access to it, a separate private domain auth server, Google/Facebook/OpenAuth. A protocol like OpenID Connect has the virtue of working with lots of different auth services, so an OpenID Connect client might fit the bill.
-- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/564f2e06-6b36-4797-8897-01a0c5a55251%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
