No mention or reference to client_assertion
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
The non normative example in the token request (c.f. https://openid.github.io/OpenID4VCI/openid-4-verifiable-credential-issuance-1_1-wg-draft.html#section-7.1-10 same for https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#section-6.1-10) contains client_assertion, but as far as I can see it is never mentioned or referenced from this specification directly.
In fact, the recommended way (https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#section-13.2-3.1) is to use https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#name-wallet-attestations-in-jwt- that follows https://datatracker.ietf.org/doc/html/draft-ietf-oauth-attestation-based-client-auth-07 which in the changelog contains
remove usage of RFC7521 and the usage of client_assertion
So it might be a reasonable editorial change, to remove the client_assertion from the example.
Contributor guide
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 the non-normative token request example in section 7.1 of the working draft and section 6.1 of the 1.0 specification. Compare its use of client_assertion with section 13.2 and the cited OAuth attestation changelog. Done means the example and surrounding specification consistently reflect the supported client authentication guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100