nuts-foundation / nuts-foundation/nuts-node
Auth v2: Complicated/confusing error message when RequestServiceAccessToken specifies non-existing URL
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
Server responds with 404, leading to the following log:
{"error":"failed to retrieve remote OAuth Authorization Server metadata: invalid client call\nserver returned HTTP 404 (expected: 200)","level":"warning","module":"Auth/iam","msg":"RequestServiceAccessToken failed","operation":"RequestServiceAccessToken","operationID":"RequestServiceAccessToken","requestURI":"/internal/auth/v2/zbj-tst/request-service-access-token","time":"2025-02-04T10:22:14Z","user":null}
invalid client call is a weird message
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 at the RequestServiceAccessToken operation and trace how remote OAuth Authorization Server metadata errors are assembled when the specified URL returns HTTP 404. Done means a non-existing URL produces a clear, accurate error without the confusing "invalid client call" text; add or update coverage if the relevant tests are found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100