Description of the related problem to solve
When using an OIDC provider with a custom implementation the jwks endpoint might point to an invalid key set. It should be possible to specify the JWKS URI. If it is specified it should be used instead the one specified in the OIDC discovery document.
Describe a possible solution
Identity SDK and starter supports setting a jwks uri.
Acceptance criteria
[ ] JWKS url can be specified via CAMUNDA_IDENTITY_ JWKS_URL in autoconfiguration
[ ] JWKS url can be specified in Identity Configuration
[ ] When the JWKS url is specified, it is used to retrieve the JWKS instead of the url that is set in the discovery document.
Security considerations
E2E test cases
Additional context
:robot: This issue is automatically synced from: source
Description of the related problem to solve When using an OIDC provider with a custom implementation the jwks endpoint might point to an invalid key set. It should be possible to specify the JWKS URI. If it is specified it should be used instead the one specified in the OIDC discovery document.
Describe a possible solution Identity SDK and starter supports setting a jwks uri.
Acceptance criteria
CAMUNDA_IDENTITY_ JWKS_URL
in autoconfigurationSecurity considerations
E2E test cases
Additional context
:robot: This issue is automatically synced from: source