nuts-foundation / nuts-foundation/nuts-node
Check oauth metadata if actions are supported
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
The oauth client and server metadata indicate what combination of parameters/operations are supported by the client/server. We often don't confirm that the other party actually supports what we are presenting.
Below is a list of parameters for AuthorizationServerMetadata that are never read for options that we do use.
Issuer(should match the party we assume we fetched the metadata from)ResponseModesSupportedResponseTypesSupportedGrantTypesSupportedPresentationDefinitionUriSupported(not even set)VPFormatsSupportedRequestObjectSigningAlgValuesSupported
Parameters that are read might not be used everywhere they should.
The same probably goes for the OAuthClientMetadata.
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 where AuthorizationServerMetadata and OAuthClientMetadata are defined and consumed. Compare the listed supported parameters with the options used by the OAuth client and server, then identify the tests covering metadata handling; done means unsupported combinations and mismatched metadata are consistently detected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100