Write a configuration
Step 2 of 4 in Configure credential configurations.
Creating a configuration and configuring one are the same operation: write settings for a new
credential_configuration_id.
PUT replaces wholesale (omitted fields are cleared); PATCH merges. The design is linked from the
design side through its bindings[].credentialConfigurationId, so no design id goes in these settings.
Use response-derived values: the list's correlationId from the status-list journey, and the KMS
resource handle and alias from the KMS journey. validityPeriod is an ISO-8601 duration such as
P365D.
The status binding is the status object: statusListId (the list's correlationId), purpose
(revocation or suspension) and revokeAtExpiry. It applies to every format. Bind a JWT Token
Status List for dc+sd-jwt, a CWT list with mdocProfile: status_list for mso_mdoc, and a
Bitstring list for jwt_vc_json and jwt_vc_json-ld. A list whose specification, proof format or
mdoc profile does not fit the format fails issuance. A configuration bound to a list never issues
without its status claim: issuance fails rather than producing an unrevocable credential.
Delete removes the id from the index and clears its settings; the design stays.
Next
Continue with step 3, Import configurations from issuer metadata.