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
I was wondering if it would make sense to state optionally that credential issuer may advertise OAuth 2.0 Protected Resource Metadata, in addition to credential issuer metadata.
In VCI scope is an optional attribute of a credential_configuration. If not provided, the wallet has a single - implied -option to use authorization_details, in authorization code grant. Resource metadata would allow the issuer to explicitly define this.
In VCI there is no option for the credential issuer to express DPoP requirements (required or not, supporter algorithms, DPoP Nonce etc).
The text was updated successfully, but these errors were encountered:
I was wondering if it would make sense to state optionally that credential issuer may advertise OAuth 2.0 Protected Resource Metadata, in addition to credential issuer metadata.
scope
is an optional attribute of acredential_configuration
. If not provided, the wallet has a single - implied -option to useauthorization_details
, in authorization code grant. Resource metadata would allow the issuer to explicitly define this.DPoP
requirements (required or not, supporter algorithms, DPoP Nonce etc).The text was updated successfully, but these errors were encountered: