Paul, I reviewed what I've done for my POC for Keycloak OIDC some time ago:
1) coded my own method as a close copy of the Google one, put it into
"mycustom/keycloak/KeycloakOpenIdConnect" file in the EDX Platform
2) Added this parameters that make their way into lms.env.json
EDXAPP_THIRD_PARTY_AUTH_BACKENDS: ['mycustom.keycloak.KeycloakOpenIdConnect',
'third_party_auth.lti.LTIAuthBackend']
EDXAPP_SOCIAL_AUTH_OAUTH_SECRETS: { keycloak-openidconnect: '<code
censored>' }
3) After the app start with the new configuration above, navigate to the
Django Admin, e.g.,
http://myurl:18000/admin/third_party_auth/oauth2providerconfig/ Click on
“Add Provider Configuration … ” at the top right Check “Enabled”, enter the
name – it shows on the icon in the default implementation, check “Visible”
Select Backend name from the dropdown: “keycloak-openidconnect” should be
available, enter the same exact string into the Provider slug Enter Client
ID “myid” – same as defined in the Keycloak Realm Client setup, leave the
Secret blank and enter Kecloak URL into Other Settings: { "BASE_URL":
"http://myurl:8080"; }
This "BASE_URL" is a Settings parameter I use in my custom provider
program, the Client ID would also be Keycloak specific. I eventually coded
a management method to automate this vs. going through the Admin console.
I think that's pretty much all I've done (lots of debugging along the way
across multiple packages)
Stan
On Saturday, November 17, 2018 at 3:15:24 AM UTC+8, Paul Kimmel wrote:
>
> Stan:
>
> Got the third party auth configuring individual providers--no 500. My OIDC
> provider doesn't show up though. Is that configured in a different list or
> in a different place in the lms.env.json file?
>
> Paul
>
>
>>>
>>>
--
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/210777d5-aafb-4b1c-a8f9-361e9de5bb97%40googlegroups.com.
