A number of modern User Management systems use OpenID Connect exclusively for 3rd party authentication vs. the base OAuth2. The social_core package employed by edx-platform provides the means of integrating with those systems via class OpenIdConnectAuth(BaseOAuth2). As the current master edx-platform code requires that the 3rd party auth packages implement BaseOAuth2 and there seems to be not much extra for the social_core consumer app to do calling OpenIdConnectAuth vs. BaseOAuth2 - sounds like simply replacing references to BaseOAuth2 with OpenIdConnectAuth in edx-platform would be a reasonable path to try. However, as edx-platform works with a number of super classes relatively to BaseOAuth2 in various forms, there are quite a few places that need to be reviewed and interrogated applying the OpenIdConnectAuth "upgrade". Has anyone succeeded running, e.g., social_core.backends.google_openidconnect.GoogleOpenIdConnect as the 3rd party auth method from edX or has a clear scope of how the 3rd party auth info is being processed by the edx-platform, from the setup through the auth completion, relatively to the use of BaseOAuth2 and its super classes? This link is very detailed but quite outdated, unfortunately:
http://johnmcox.blogspot.com/2014/05/understanding-edx-third-party.html <http://johnmcox.blogspot.hk/2014/05/understanding-edx-third-party.html> -- You received this message because you are subscribed to the Google Groups "General Open edX discussion" group. To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/7f57a2f8-888e-4589-bcc1-9505bdeb3ed6%40googlegroups.com.
