nuts-foundation / nuts-foundation/nuts-node
Use JWT as accessToken format to allow for metadata
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
Some PEPs accept requests with accessTokens issued by multiple Authorization servers. In order for them to use the correct handler and introspection endpoint, they need some meta data, like the issuer of the accessToken. This could be achieved by embedding the secret string into a JWT which allows for some extra claims.
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 tracing the PEP request path that consumes accessTokens and the handler and introspection selection described in the issue. Define the expected JWT metadata for tokens from multiple Authorization servers, then verify that each request selects the correct handler and introspection endpoint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100