Authorise null to access your pod

Open
#1,607 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, nodejs
Domain
authentication, authorization, backend

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.

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!

Dominant language
JavaScript
Stars
1.8k
Forks
308
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodeSolidServer/node-solid-server

All issues in nodeSolidServer/node-solid-server

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.