Solid OIDC Security Consideration Client IDs
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-ids:
An AS SHOULD assign a fixed set of low trust policies to any client identified as anonymous.
Elaborate a bit more on "anonymous".
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
Start with the security-client-ids section and read the surrounding guidance for clients identified as anonymous. Clarify what “anonymous” means in this context, then ensure the added explanation fits the specification’s existing terminology and intent.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100