Describe the bug
When reviewing the response of the well known config endpoint at /gatekeeper/api/.well-known/openid-configuration the endpoint to get jwks should be jwks_uri as described in section 3 on the spec. At the moment the field is labelled jwks_endpoint.
To Reproduce
Steps to reproduce the behaviour:
Go to <DOMAIN>/gatekeeper/api/.well-known/openid-configuration (domain is wherever your gatekeeper instance lives)
Look at jwks_endpoint
See error
Expected behaviorjwks_endpoint should be labelled jwks_uri.
Describe the bug When reviewing the response of the well known config endpoint at
/gatekeeper/api/.well-known/openid-configuration
the endpoint to get jwks should bejwks_uri
as described in section 3 on the spec. At the moment the field is labelledjwks_endpoint
.To Reproduce Steps to reproduce the behaviour:
<DOMAIN>/gatekeeper/api/.well-known/openid-configuration
(domain is wherever your gatekeeper instance lives)jwks_endpoint
Expected behavior
jwks_endpoint
should be labelledjwks_uri
.