Keycloak Integration #7039
Unanswered
durga-prasad-redy
asked this question in
Ask Questions, Get Answers
Replies: 1 comment
-
From where did you get these settings? Configuring them does nothing in Opencast. Opencast does not implement the OIDC flow itself. Instead, you can use something like oauth2-proxy to direct users through the OIDC flow. After that, oauth2-proxy can send a JWT (the ID token) to Opencast. See JWT documentation. The original JWT PR also has an example setup. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone,
I’m currently trying to integrate Keycloak (OIDC) as the authentication provider for Opencast, but I’m running into some issues with configuration and would really appreciate guidance from anyone who has successfully set this up.
What I’ve Tried So Far
Running Opencast in Docker (official images).
Configured custom.properties with OIDC settings:
org.opencastproject.security.openid.client_id=opencast
org.opencastproject.security.openid.client_secret=********
org.opencastproject.security.openid.provider=/realms/
Keycloak realm, client, and roles are already created.
Verified that the Keycloak client allows confidential access and uses openid-connect.
Issues Faced:
Login redirect dosent work , open still uses its internal iam.
Environment:
Opencast version: 18.0
Keycloak version: 24.0
Deployment: Docker Compose
Any help, pointers, or example configs would be amazing! 🙏
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions