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.

Sign up for GitHub

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

Jump to bottom

Support for JWKS URI #451

Open
guicassolato opened this issue Jan 4, 2024 · 0 comments
Open

Support for JWKS URI #451

guicassolato opened this issue Jan 4, 2024 · 0 comments
Labels
area/api kind/enhancement New feature or request participation/good first issue Good for newcomers size/medium size/small

Comments

@guicassolato
Copy link
Collaborator

Currently, the AuthConfig API (v1beta2) allows specifying an issuerURL from which a JWKS is discovered, using OpenId Connect Discovery. Alternatively, the documentation mentions a jwksUrl field that was never delivered.

To support JWT issuers that do not implement OpenId Connect Discovery, the AuthConfig API should allow specifying an alternative JWKS URL.

This will also start paving the way for Kuadrant to support Gateway API JWT policies in the future, which could be then fully implemented as Authorino AuthConfigs by adding support as well for JWKs stored in Kubernetes Secrets.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/api kind/enhancement New feature or request participation/good first issue Good for newcomers size/medium size/small
Projects
Kuadrant
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@guicassolato