Solid OIDC Primer Retrieves OP Configuration
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 26
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
In #authorization-code-pkce-flow-step-3:
The thing we care about here
Note that we only support the code response type.
Paraphrase.
However, implicit flows should not be used for security reasons. Therefore, we don’t recommend enabling them. For the same reason, we do not support the implicit grant type.
It is unclear whether these recommendations are expanding on the spec or suggesting best practices. If the latter, consider moving them to a separate; "Solid OIDC Best Practices and Guidelines".
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 #authorization-code-pkce-flow-step-3 section and read the quoted text about the code response type and implicit grant type. Clarify whether those passages explain the specification or state best practices; done means the distinction is explicit, with best-practice guidance moved to a separate “Solid OIDC Best Practices and Guidelines” document if appropriate.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100