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. Use response-derived ids:
the design id and version from the design journey, the list id 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, purpose (revocation or suspension)
and revokeAtExpiry. It applies to the JWS formats dc+sd-jwt and jwt_vc_json. Leave it empty for
mso_mdoc, which uses the standalone CWT profile. 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.