Context
Adding the authorization_endpoint field in the configuration will allow OIDC clients, such as oidc-gatekeeper, to automatically know the endpoint they should use for starting the Authorization Code Flow.
This is useful because by having this information available in Dex's .well-known endpoint will allow reducing the required configuration for oidc-gatekeeper, as it will automatically infer it.
What needs to get done
- Add
"authorization_endpoint": "/dex/auth"as part of these lines
Definition of Done
The .well-known endpoint shows this information and OIDC clients can use it. To verify this we can curl -v <dex-issuer-url>/dex/.well-known/openid-configuration
Context
Adding the
authorization_endpointfield in the configuration will allow OIDC clients, such as oidc-gatekeeper, to automatically know the endpoint they should use for starting the Authorization Code Flow.This is useful because by having this information available in Dex's
.well-knownendpoint will allow reducing the required configuration for oidc-gatekeeper, as it will automatically infer it.What needs to get done
"authorization_endpoint": "/dex/auth"as part of these linesDefinition of Done
The
.well-knownendpoint shows this information and OIDC clients can use it. To verify this we cancurl -v <dex-issuer-url>/dex/.well-known/openid-configuration