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
Draft 15 intoruces the concept of "key attestation" as a way for the holder to provide evidence for the authenticity and security properties of a key and its storage component to the Credential Issuer.
Spec forsees that a key attestation jwt can be used as proof of possession of key material to be embedded in issued credentials (see here)
It also mentiones that
The Credential Issuer SHOULD issue a Credential for each cryptographic public key specified in the attested_keys claim within the key_attestation parameter.
For the above to be supported issuer must:
Introduce new proof type attestation in credential configuration's proof_types_supported
Validate the key attestation passed from wallet:
Validate that key attestation is required from the credential's policy (configuration includes it in proof_types_supported)
Draft 15 intoruces the concept of "key attestation" as a way for the holder to provide evidence for the authenticity and security properties of a key and its storage component to the Credential Issuer.
Spec forsees that a key attestation jwt can be used as proof of possession of key material to be embedded in issued credentials (see here)
It also mentiones that
For the above to be supported issuer must:
attestation
in credential configuration'sproof_types_supported
proof_types_supported
)attested_keys
claim a separate credential instance should be created for the same dataset and format.The text was updated successfully, but these errors were encountered: