You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
there is a requirement to support various client_id_schemes in RFC002. This requirement mostly comes from RFC001 that references HAIP which includes client_id_schemes that are not part of OIDC4VP draft 18 that RFC002 is based on.
As a result RFC002 should in my opinion explicitly state the client id schemes EWC supports in the current pilot phase. As far as I know EWC wallet providers and Issuers/Verifiers rely on: redirect_uri, did and x509_sans_dns
The text was updated successfully, but these errors were encountered:
Similar to the reasoning behind #146
there is a requirement to support various client_id_schemes in RFC002. This requirement mostly comes from RFC001 that references HAIP which includes client_id_schemes that are not part of OIDC4VP draft 18 that RFC002 is based on.
As a result RFC002 should in my opinion explicitly state the client id schemes EWC supports in the current pilot phase. As far as I know EWC wallet providers and Issuers/Verifiers rely on: redirect_uri, did and x509_sans_dns
The text was updated successfully, but these errors were encountered: