Skip to content
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

Open
pmauduit opened this issue Aug 27, 2024 · 2 comments
Open

document usage of CAS as oauth2 / OIDC provider #29

pmauduit opened this issue Aug 27, 2024 · 2 comments

Comments

@pmauduit
Copy link
Member

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 doc

@pmauduit
Copy link
Member Author

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).

@pmauduit
Copy link
Member Author

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 ...).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant