Reconsider Client Identifiers in light of OpenID Federation Entities
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 26
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
This issue brings in several related issues, including #199, #95, #202 and #201, reframing the issue as the following:
The Solid-OIDC specification currently makes use of globally unique client_id values, formatted as URLs that dereference to a Client Identifier Document (as defined by Solid-OIDC). A very similar mechanism is defined by the (draft) OpenID Connect Federation specification.
This issue is here to discuss the proposal (edited to incorporate https://github.com/solid/solid-oidc/issues/207#issuecomment-1301065781):
The Solid-OIDC specification should drop the current definition of Client Identifiers and associated JSON-LD appendix in favor of adopting the OpenID Connect Federation definition of an Entity Identifier and Automatic Registration
/cc @Sakurann
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 by reading the Solid-OIDC Client Identifiers section and its JSON-LD appendix, then compare them with the linked OpenID Connect Federation Entity Identifier and Automatic Registration sections. Review related issues #199, #95, #202 and #201 and the discussion before determining the specification changes needed; done requires a decided proposal and corresponding specification update.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100