Support multiple OIDC PKIs in the Gateway
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
Is your feature request related to a problem? Please describe.
OIDC validation key source: oidc.jwks.uri
allows to define only one URL, which mean that resource can validate only against one OIDC provider.
At the same time oauth2.client allows to define multiple OIDC providers.
Describe the solution you'd like
Convert oidc.jwks.uri to list so that there possible to define multiple keys
oidc.jwks.uri:
- okta-keys-url
- entra-keys-url
Willingness to help
Always happy to help
Additional context
Gloud-Gateway,Gateway
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Gateway configuration and OIDC validation entry point that consume oidc.jwks.uri; no file or test is named in the issue. Trace how the current single key source is loaded and used, then update the relevant tests to cover the two-URL YAML example and validation against both configured providers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100