openedx / openedx/auth-backends
Add Support for True Multi-tenancy
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24
- Forks
- 23
- Avg merge
- 12h 5m
- Merged PRs (30d)
- 1
Description
We currently use the same OAuth credentials for all tenants on our IDAs. This works because the auth service (LMS) is not truly multi-tenant. Just because LMS is not truly multi-tenant doesn't mean our IDAs cannot be.
Most of the IDAs use the Django sites framework coupled with a custom model (e.g. SiteConfiguration). We should properly codify this implementation in https://github.com/edx/edx-django-extensions. Once that is done, we can create a new strategy that is multi-tenant-aware.
If we ever get to the point of separating users, we should explore a new storage backend as well as discussed in https://github.com/omab/python-social-auth/issues/552.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how the IDAs currently use shared OAuth credentials, the Django sites framework, and the SiteConfiguration model. Read the proposed implementation target in edx-django-extensions and the strategy documentation, then review python-social-auth issue 552 for the user-separation context. Done requires a codified multi-tenant implementation and a corresponding multi-tenant-aware strategy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100