solid / solid/solid-oidc

Presenting multiple WebIDs in an ID Token

Open
#47 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Bikeshed
Stars
26
Forks
14
PR merge metrics
No merged PRs in 30d

Description

Section 6.2 of the Solid-OIDC spec reads:

The user’s [singular] WebID MUST be present in the ID Token as the webid claim.

While this sentence implies that the token can only include a single WebID, it is perfectly possible for a user to have multiple WebIDs (cf. #46). In the use cases where an Identity Provider knows about more than one WebID, I believe it would be preferable to have the spec accept a list of them in the claim.

This would of course impact how Resource Servers (or their respective Authorization Server) have to deal with ID Tokens, but i.m.o. only for the better: users who indeed identify with multiple WebIDs would then be able to access all resources that they would otherwise be able to access with each of the WebIDs separately in multiple tokens.

Is something like this already proposed (I could not find it)? Do you think this is a good idea?

(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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with Section 6.2 of the Solid-OIDC specification and compare this proposal with issues #46 and #26. Determine whether multiple WebIDs should be permitted in the claim and what Resource Servers or Authorization Servers would need to do; the work is done when the specification decision and resulting wording are agreed.

Written by the indexing model from the issue text.

Assessment

Domain
authentication, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.