We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Claims mapping seems currently applies to all suppliers in georchestra.gateway.security.oidc.claims :
georchestra.gateway.security.oidc.claims
https://github.com/georchestra/georchestra-gateway/blob/main/docs/authzn.adoc#claims-configuration
Note that mapping only works with roles, organizationid (cn) and user id
If geOrchestra want to allow many providers from /login page, this config seems limited.
/login
Indeed, each provider can return custom claims not aligns with sandard OpenID claims.
A custom claims mapping (one by provider) seems required If a platform allows you to connect with several providers.
The text was updated successfully, but these errors were encountered:
See a61a98c#diff-634e11ac8d1e6af611f3363d4560bb7e9c3a8c482565ac3ae71de26b43319a67R231
Sorry, something went wrong.
No branches or pull requests
Claims mapping seems currently applies to all suppliers in
georchestra.gateway.security.oidc.claims:https://github.com/georchestra/georchestra-gateway/blob/main/docs/authzn.adoc#claims-configuration
If geOrchestra want to allow many providers from
/loginpage, this config seems limited.Indeed, each provider can return custom claims not aligns with sandard OpenID claims.
A custom claims mapping (one by provider) seems required If a platform allows you to connect with several providers.
The text was updated successfully, but these errors were encountered: