quarkus-oidc management of properties with discovery #22806
-
|
Hello, I was wondering if, when discovery of the URLs are enabled thanks to a well-known URI and the proper properties, URLs set in properties such as JWKS_uri should act as overriding instead of being simples fallbacks. I'm trying to manage the fact that our access_token are signed by a certificate that differs from our id_token. I'd like to use the discovery, except for that specific parameter that I'd like to override. Proposal: When discovery is enabled, oidc properties are override instead of fallbacks. If so, I'd be pleased to make the developments for this feature :) |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
/cc @pedroigor, @sberyozkin |
Beta Was this translation helpful? Give feedback.
-
|
I think it makes sense and would not break anything - the users either use the discovery or disable it and manually set all the required properties, when both the discovered and manually configured properties are available then the preference should indeed be given to the ones set up locally. Please go ahead with creating a PR, thanks |
Beta Was this translation helpful? Give feedback.
-
|
@egavard-lmfr FYI, #26762 |
Beta Was this translation helpful? Give feedback.
Hi @egavard-lmfr
I think it makes sense and would not break anything - the users either use the discovery or disable it and manually set all the required properties, when both the discovered and manually configured properties are available then the preference should indeed be given to the ones set up locally.
Please go ahead with creating a PR, thanks