search

openid / oid4vc-haip-sd-jwt-vc

High Assurance Profile of OID4VP and OID4VCI using SD-JWT VC and mdocs that is privacy preserving, secure, and meets regulatory requirements
29 stars 7 forks source link

add back client_metadata? #17

Open Sakurann opened 1 year ago

Sakurann commented 1 year ago

I left it out in the first pass. any protocol-related parameter that can be passed in the client_metadata like subject_syntax_types_supported is hard-coded in the profile. if there is a need to verifier related metadata like logo_url, client_name, etc. we should add it back

peppelinux commented 1 year ago

federation trust_chain bring the verifier metadata in the trust attestation, and the federation_entity metadata defines a standard scheme for every kind of participant, this is here

https://openid.net/specs/openid-connect-federation-1_0.html#section-4.7

Sakurann commented 1 week ago

now that client_metadata has been improved in oid4vp, we should add it back