How to make Django-CMS and Open Edx use same authentication for users?

[Aman]

We are looking to develop a Django project in which we need to integrate three different Django packages namely a CMS (Django-CMS or Wagtail), a LMS (Open edX) and a support/ticketing system.

Since Django-CMS, Open Edx have their own user authentication, but we want them to share a common authentication (username, password, user profiles), so that a user logged into one section of website is able to move to other sections smoothly.

How to make these different packages share same authentication? Is there any guidelines or procedure to integrate these different Django Packages?

[Clinton Blackburn]

The LMS is already setup as an OAuth 2.0 provider. It also has support for OpenID Connect (which we'd like to deprecate in favor of OAuth 2.0 + JWT). You can see the existing authentication backends at https://github.com/edx/auth-backends. If you'd like to see it in action, use Devstack (https://github.com/edx/devstack). The Credentials Service (https://github.com/edx/credentials) is our smallest IDA. I recommend using it as an example, if you want to dig deeper into the code.

Additionally, I have a prototype of a Wagtail-based marketing site at https://github.com/edx/marketing-site/pull/2. The basic Django project on the master branch has support for OpenID Connect.

Clinton

[Aman]

Thanks a lot for your reply Clinton. Is it possible to have authentication shared between a Open edX running on one VM, and another VM hosting a CMS? 

Reason is I don't want to add wagtail to the same Virtual Machine where Open edX is hosted. I will really appreciate your reply. 

[Clinton Blackburn]

Yes. One trait of single sign-on is that the OAuth provider is independent of the clients.

[Pengcheng Liu]

Hi Clinton,

Thanks for sharing, it is really useful.

Pengcheng

在 2017年11月9日星期四 UTC+8上午12:41:51，Clinton Blackburn写道：