OpenConext / OpenConext/OpenConext-oidcng
Make jwks_uri configurable
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4
- Forks
- 6
- Avg merge
- 5d 32m
- Merged PRs (30d)
- 3
Description
We would like to be able to serve the well-known endpoint and the jwks data from a different domain (to work around cookie-blockers). Proxying the existing file from a different domain should Just Work, except that the jwks-endpoint has the OIDCng-servername hardcoded. Can we make that configurable?
The other endpoints (authz, token, userinfo, introspect, etc) should not change.
Contributor guide
No contributing guide indexed for this repository
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 JWKS endpoint and the hardcoded OIDCng-servername used in its response. Make that value configurable for the well-known and JWKS data served from another domain, then verify that the authz, token, userinfo, and introspection endpoints remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100