You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: