Solid OIDC Security Consideration Client Trust
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 #security-client-trust:
Unclear how to use this information as a security consideration. Perhaps elaborate. Alternatively, reuse some of this information in #concepts or somewhere else early on.
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
Review the material referenced by #security-client-trust and compare it with the earlier #concepts content. Clarify how client trust should be used as a security consideration, or determine whether the information belongs in #concepts or another early section; done means the placement and security guidance are actionable.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100