-
Notifications
You must be signed in to change notification settings - Fork 13
Open
Description
This is a proposal to change the webid claim to solid in access tokens and ID tokens.
The background for this is severalfold:
- The current
webidclaim is very WebID specific, and WebIDs are (according to the draft WebID specification) limited to HTTPS URLs. If other types of identifiers are to be supported (e.g. DIDs, VCs), placing those in thewebidclaim is questionable. Asolidclaim would therefore be more flexible and, arguably, forward looking. - The names used by Solid-OIDC have generally been moving toward "Solid" and away from "WebID". The specification name is
Solid-OIDC(it was formerlyWebID-OIDC). The audience claim for access tokens uses a value ofsolidto indicate that the token should be used with the Solid ecosystem. - WebIDs will continue to be supported with a
solidclaim and will likely continue to be the main identifier format for agents in the near term - There is a discussion to use a scope value with Solid-OIDC, and there is an indication that this scope could be
solid. If the name of that scope is, in fact,solid, then using asolidclaim in the resulting tokens would make for a simple, consistent naming structure.
If the name of this claim is changed to solid, we should constrain the value(s) to be IRIs.
This change would place no new requirements on Solid components to support DIDs, but it does make support of DIDs more possible for the future.
This change would require adjustments on client apps (RP), Pod servers (RS) and identity providers (OP).
matthieubosquet, NSeydoux and balessan
Metadata
Metadata
Assignees
Labels
No labels