Solid OIDC Issuer Discovery via Link Headers
Open
Nobody has claimed this yet.
doc: solid-oidc
editorial
- Dominant language
- Bikeshed
- Stars
- 26
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
In #oidc-issuer-discovery-link-headers:
Mention why/how this may be useful, e.g., when resource is not publicly readable (401/403)?
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
Open the #oidc-issuer-discovery-link-headers section in the specification and review the existing explanation. Add a concise rationale describing when Link Header discovery is useful, including cases where the resource is not publicly readable and returns 401 or 403; done means the section explains both the purpose and the relevant access scenario.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100