UMA Claims Pushing with DPoP-bound Solid OIDC tokens
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 26
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
In the Solid OIDC specification we are currently not defining the UMA claims pushing flow in a normative sense. See Section 9.2
The claim_token_format http://openid.net/specs/openid-connect-core-1_0.html#IDToken is used, which should thus indicates a Solid-OIDC DPoP-bound identity token. However from the perspective of the UMA specification DPoP is not considered in the claims pushing flow, so it would be good to write this out in a normative fashion. Especially given the fact that this IRI already identifies OIDC ID Tokens that aren't DPoP-bound.
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 with Section 9.2 of the Solid OIDC specification and review the UMA claims-pushing flow alongside the DPoP requirements described in the issue. The work is complete when the specification normatively defines how the DPoP-bound Solid OIDC identity token is handled and distinguishes it from a non-DPoP-bound ID token.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100