nodeSolidServer / nodeSolidServer/node-solid-server
Dereference client id document as described in Solid-OIDC spec
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Description
While testing an application, we tried to send an authorization request to solidcommunity.net (which runs on the NSS I believe) while using a client id that pointed to a. client id document as described in section 5 and 5.1 of the solid OIDC spec.
This resulted in an Unauthorized error. I tried the exact same request with a dynamically registered client and it worked, so it seems that solidcommunity.net (and therefore the NSS) don't yet support these client id documents.
I was unable to find any issues pertaining to this in either repo.
Am I correct in assuming this is not implemented yet?
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
Start by tracing NSS authorization request handling and compare the client ID document flow described in sections 5 and 5.1 of the Solid-OIDC specification with the dynamically registered client flow. Reproduce the request against solidcommunity.net; done means an authorization request using a client ID document is accepted rather than returning Unauthorized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100