Opened 5 years ago
Closed 5 years ago
#31727 closed New feature (duplicate)
Open ID Connect Support
| Reported by: | pandichef | Owned by: | nobody |
|---|---|---|---|
| Component: | contrib.auth | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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.
Note:
See TracTickets
for help on using tickets.
Duplicate of #3213.