VerifiableCredentialSdJwt
SD-JWT representation of a VerifiableCredential. According to SD-JWT-based Verifiable Credentials (SD-JWT VC), Draft 10 and Selective Disclosure for JWTs (SD-JWT), Draft 13
Constructors
Properties
OPTIONAL unless cryptographic Key Binding is to be supported, in which case it is REQUIRED. Contains the confirmation method identifying the proof of possession key as defined in RFC7800. It is RECOMMENDED that this contains a JWK as defined in Section 3.2 of RFC7800. For proof of cryptographic Key Binding, the KB-JWT in the presentation of the SD-JWT MUST be secured by the key identified in this claim.
OPTIONAL. The information on how to read the status of the Verifiable Credential. By including a status
claim in a Referenced Token, the Issuer is referencing a mechanism to retrieve status information about this Referenced Token. This specification defines one possible member of the status
object, called status_list
. Other members of the status
object may be defined by other specifications. This is analogous to cnf
claim in Section 3.1 of RFC7800 in which different authenticity confirmation methods can be included.
OPTIONAL. The expiry time of the Verifiable Credential after which the Verifiable Credential is no longer valid. See RFC7519 for more information.
The claim _sd_alg
indicates the hash algorithm used by the Issuer to generate the digests as described in Section 4.2. When used, this claim MUST appear at the top level of the SD-JWT payload. It MUST NOT be used in any object nested within the payload. If the _sd_alg
claim is not present at the top level, a default value of sha-256
MUST be used.
OPTIONAL. The information on how to read the status of the Verifiable Credential. By including a status
claim in a Referenced Token, the Issuer is referencing a mechanism to retrieve status information about this Referenced Token. This specification defines one possible member of the status
object, called status_list
. Other members of the status
object may be defined by other specifications. This is analogous to cnf
claim in Section 3.1 of RFC7800 in which different authenticity confirmation methods can be included.
REQUIRED. The type of the Verifiable Credential, e.g., https://credentials.example.com/identity_credential
. This specification defines the JWT claim vct
(for verifiable credential type). The vct
value MUST be a case-sensitive StringOrURI (see RFC7519) value serving as an identifier for the type of the SD-JWT VC. The vct
value MUST be a Collision-Resistant Name as defined in Section 2 of RFC7515.