Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Support for True Multi-tenancy #26

Open
clintonb opened this issue Dec 18, 2016 · 3 comments
Open

Add Support for True Multi-tenancy #26

clintonb opened this issue Dec 18, 2016 · 3 comments
Labels
enhancement Relates to new features or improvements to existing features

Comments

@clintonb
Copy link
Contributor

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 omab/python-social-auth#552.

@clintonb clintonb added the enhancement Relates to new features or improvements to existing features label Dec 18, 2016
@jadavbheda
Copy link

This request seems to be created a while ago. I wonder if community has anything already build or started efforts to build truly multi-tenant. If there is any we would love to contribute. Any pointers would be appreciated.

@ilavenilp
Copy link

+1

1 similar comment
@k2glyph
Copy link

k2glyph commented Aug 1, 2020

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Relates to new features or improvements to existing features
Projects
None yet
Development

No branches or pull requests

4 participants