-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
document usage of CAS as oauth2 / OIDC provider #29
Comments
Also there are known bugs with the provided configuration (cas as oauth2 provider using the gateway, and as pure oidc provider it does not even work). |
CAS as oauth2 is somehow 'documented' in the form of a docker composition here: https://github.com/georchestra/sample-docker-composition/tree/main/gateway/oauth2 And using a third-party OIDC here: https://github.com/georchestra/sample-docker-composition/tree/main/gateway/oidc For now, configuring CAS as OIDC provider is complicated (needs to go through https, mismatch between localhost vs "real" / actual endpoint ...). |
As in the following PR on the gateway:
georchestra/georchestra-gateway#83
Also it might be of interest to document how to bypass the consent screen when selecting a oidc/oauth2 provider, see the
bypassApprovalPrompt
on the official docThe text was updated successfully, but these errors were encountered: