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

[OIDC] Config inheritance for multi-tenancy OIDC #12268

Closed
canidae opened this issue Sep 22, 2020 · 0 comments
Closed

[OIDC] Config inheritance for multi-tenancy OIDC #12268

canidae opened this issue Sep 22, 2020 · 0 comments
Labels
area/oidc kind/enhancement New feature or request
Milestone

Comments

@canidae
Copy link

canidae commented Sep 22, 2020

Some configuration duplication may be avoided for multi-tenacy OIDC if configuration options were inherited from the default OIDC config.
If configuration is not to be inherited, a better error message should be given to the user upon missing configuration values for a tenant. Currently it will only say for example Both 'auth-server-url' and 'client-id' or alternatively 'public-key' must be configured when the quarkus-oidc extension is enabled, but it doesn't say which tenant is missing these values.

This issue was raised after a discussion here: #12254

@canidae canidae added the kind/bug Something isn't working label Sep 22, 2020
@sberyozkin sberyozkin added kind/enhancement New feature or request area/oidc and removed kind/bug Something isn't working labels Sep 23, 2020
@gsmet gsmet changed the title [OIDC] Config inheritance for multi-tenacy OIDC [OIDC] Config inheritance for multi-tenancy OIDC Oct 1, 2020
@gsmet gsmet added this to the 1.9.0 - master milestone Oct 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/oidc kind/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants