Allow OAuth 2.0 Attestation-Based Client Authentication
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Originally submitted by josephheenan (Joseph Heenan) on 2025-05-27
FAPI2 currently only allows private_key_jwt and mtls client authentication, both of which are kind of awkward for mobile clients to do.
This makes it difficult for OID4VCI to adopt FAPI (see https://github.com/openid/OpenID4VCI/issues/291#issuecomment-2862965297).
I wonder if we can allow the new IETF draft in the future (in addition to private_key_jwt / MTLS client auth) - I think it would be a non-breaking extension:
https://datatracker.ietf.org/doc/draft-ietf-oauth-attestation-based-client-auth/
Bitbucket status: open
Bitbucket origin: issue 744
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
No files, tests, or entry points are named. Start by reading the FAPI2 client-authentication requirements and the linked IETF attestation-based client-authentication draft, then review the OID4VCI discussion for compatibility context. Done means defining and implementing support for the new authentication method alongside private_key_jwt and MTLS without breaking existing methods.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100