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

Add authorization_endpoint field in Dex's configuration #202

Open
DnPlas opened this issue Jul 5, 2024 · 1 comment
Open

Add authorization_endpoint field in Dex's configuration #202

DnPlas opened this issue Jul 5, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@DnPlas
Copy link
Contributor

DnPlas commented Jul 5, 2024

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

  1. 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

@DnPlas DnPlas added the enhancement New feature or request label Jul 5, 2024
Copy link

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5965.

This message was autogenerated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant