[OpenID4VC High Assurance Interoperability Profile with SD-JWT VC] Issues

[peppelinux]

See https://github.com/openid/oid4vc-haip-sd-jwt-vc

• [x] vp_format must include vc+sd-jwt see
• [x] HAIP doesn't support Wallet capabilities discovery . This is in conflict with the proposed Advanced Flow
• [x] [Issuance] The client_id value in the PAR request MUST be a string that the Wallet has used as the sub value in the client attestation JWT
• [ ] [Issuance] Refresh tokens MUST be supported for credential refresh.
• [ ] [Issuance] Wallets MUST support deferred authorization by being able to process the Token error response parameters authorization_pending and slow_down, and the credential offer parameter interval
• [x] #177
• [ ] [Presentation] client_id_scheme value MUST be either x509_san_dns or verifier_attestation. The Wallet MUST support both. The Verifier MUST support at least one. (we use OpenID Federation, then client_id_scheme set to entity_id)
• [x] Presentation Definition JSON object MUST be sent using a presentation_definition parameter -> (we want to use scopes!)
• [x] Issuers, holders and verifiers MUST support P-256 (secp256r1) as a key type with ES256 JWT algorithm for signing and signature validation

[peppelinux]

The presentation definition example MUST use this schema https://vcstuff.github.io/oid4vc-haip-sd-jwt-vc/draft-oid4vc-haip-sd-jwt-vc.html#appendix-B

[peppelinux]

during the call of 28 aug 2024 we agreed to close this issue and use separate issues within the milestone 0.8.1