nodeSolidServer / nodeSolidServer/node-solid-server
Expired access token results in a 401 on a public resource
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Description
To reproduce: Make an authenticated request (with an expired bearer token) to a public resource.
Since authentication and token validation happens before access control, the authentication layer throws a 401 unauthorized / invalid token.
But there may be developer expectation that a public resource should not even check or validate authentication, so this 401 may be unexpected.
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
No file, test, or entry point is named. Reproduce the request with an expired bearer token, then clarify whether public resources should bypass token validation or still return 401; completion requires an agreed behavior and verification of that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- api, authentication
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100