Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add clarification about client_id for wallet attestation #441

Merged
merged 9 commits into from
Feb 13, 2025
6 changes: 4 additions & 2 deletions openid-4-verifiable-credential-issuance-1_0.md
Original file line number Diff line number Diff line change
@@ -2532,7 +2532,7 @@ The following is a non-normative example of a Wallet Attestation:

```
{
"typ": "oauth-client-attestation+jwt"
"typ": "oauth-client-attestation+jwt",
"alg": "ES256",
"kid": "11"
}
@@ -2558,6 +2558,8 @@ The following is a non-normative example of a Wallet Attestation:

To use the Wallet Attestation towards the Authorization Server, the Wallet MUST generate a proof of possession according to Section 5.2 "Client Attestation PoP JWT" of Attestation-Based Client Authentication.

The `sub` claim of the Wallet Attestation JWT is picked by the Wallet Provider and represents the `client_id` of the Wallet. This value should be shared by all Wallet Instances from that Wallet Provider for privacy reasons.

# IANA Considerations

## OAuth URI Registry
@@ -2756,7 +2758,7 @@ The technology described in this specification was made available from contribut

-16

*
* clarify client_id of wallet with wallet attestation

-15