IETF I-D for Client Identifiers as URIs
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 26
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
I just wanted to let the Solid-OIDC team know that I'm currently working with Aaron Parecki to define an OAuth IETF I-D for client identifier metadata documents, or as they exist in Solid-OIDC Client ID Documents. I believe we're currently compatible with the prior-work done by Solid-OIDC, and we've also acknowledged the prior work you've done.
https://www.ietf.org/id/draft-parecki-oauth-client-id-metadata-document-01.html
This allows them to be used in the wider OAuth community, outside of that of just Solid; for instance, in federated social media, where they are also quite useful, where OIDC Federation wouldn't necessarily work (due to lack of trust roots)
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
The issue names no repository file, test, or entry point to inspect. Read the linked IETF draft and compare it with the Solid-OIDC specification; completion is not defined because the issue does not request a concrete repository change.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100