#31727: Open ID Connect Support
----------------------------------------+------------------------
Reporter: pandichef | Owner: nobody
Type: New feature | Status: new
Component: contrib.auth | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
----------------------------------------+------------------------
In the past, I would write giant monolith project with many Django apps.
These would be routed to www.mysite.com/app1, www.mysite.com/app2, etc.
Today, I find it much easier to maintain small projects with one or two
Django apps. I "route" these at the DNS level i.e., app1.mysite.com,
app2.mysite.com, etc.
The only problem is the User table i.e., it's the same people that use all
the subdomains. It would be great if app1.mysite.com could authenticate
from www.mysite.com via Open ID Connect. I've rolled out custom solutions
in the past, but this seems pretty fundamental in the era of loose
coupling and I think it should be baked into Django.
--
Ticket URL: <https://code.djangoproject.com/ticket/31727>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.2c3f6cad7e5034a2593bc6ce47bf39fc%40djangoproject.com.
