Standard way to add/change WebID at the Identity Provider
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 26
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Neither OAuth2.0, nor OpenID Connect (nor, currently, Solid-OIDC), specifies how to let a user/subject add or change claims — and, by extension, their identifying information (e.g. sub and webid claims). Making the jump from local to global information, however, Solid-OIDC would i.m.o. benefit from standardizing this, at least for those claims that are accepted identifiers within the Solid ecosystem (*).
Specific use-cases that come to mind are:
- users with accounts at multiple Identity Providers for different WebIDs, wishing to merge the information on both;
- users with a single WebID pointing to a single Identity Provider who, on creation of a second WebID, want to keep identifying using the same Identity Provider; and
- users with a self-minted WebID, wanting to add it as a claim to a (new or existing) Identity Provider.
While not necessarily about account registration, this seems closely linked to solid/solid-oidc#77 (proposing to incorporate the OpenID Connect Create Prompt draft).
Very interested to hear your thoughts on this, whether you think this is desirable, and how you think this could best be achieved.
(*) I'm writing this about WebIDs, but this holds more generally for all kinds of "solid claims", cf. https://github.com/solid/solid-oidc/issues/26.
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 use cases in this issue and the linked solid/solid-oidc#77 and #26 discussions. Determine whether the project wants a standardized mechanism for changing identity claims; done would require an agreed, concrete specification proposal rather than an implementation change.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100