nodeSolidServer / nodeSolidServer/node-solid-server
Authorise null to access your pod
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Description
On a sign in, I'm seeing this:
https://github.com/crspybits/SolidAuthSwift/blob/main/Docs/README/AuthorizeNull.png
@wrmack looked and says this comes from appUrl.origin.
https://github.com/crspybits/SolidAuthSwift/issues/1
Is there a reason it isn't coming from client_name in the registration request?
Thanks!
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 reproducing the sign-in flow shown in AuthorizeNull.png and inspect where appUrl.origin is used. Compare that value with client_name in the registration request, using the linked SolidAuthSwift issue for context. Done means determining the intended source for the displayed authorization identity and confirming the behavior after the decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- authentication, authorization, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100