Configure credential configurations
A credential configuration is what the issuer advertises and a wallet requests, addressed by its credential_configuration_id. Writing its settings registers the id with the issuer and sets its signing key and status list. The credential design binds to the same id from the design side. This journey comes after designs and status lists because it uses the design's configuration id and the list's correlationId.
Complete first: Set up the credential issuer, Define credential designs and claims, Publish status lists.
Steps and why they come in this order
| Step | Why here |
|---|---|
| 1. Review configurations and effective values | Seeded or earlier configurations may already advertise the type. Read stored and effective values before writing. |
| 2. Write a configuration | Writing settings both stores them and registers the id in the issuer index, which is what makes the issuer advertise it. |
| 3. Import configurations from issuer metadata | When a configuration already exists in another issuer metadata document, import it instead of retyping it. |
| 4. Check the effective configuration | Inheritance is live. Confirm the resolved values, operator form and authorization server before creating offers. |
Design versus configuration
The credential design owns identity and presentation: per-locale display, claim policy and rendering. The configuration settings own everything else: OAuth scope, format identity, binding and signing algorithms, proof types, signing key, validity and status binding. Writing settings never touches design-authored display, and editing a design never overwrites settings.
These routes address the tenant's issuer. The credential-level authorization-server override in step 4
is addressed per issuer instance, under /oid4vci/issuers/{instanceId}/....
Deeper reference
Credential Issuer: Credentials explains every setting and the Postman folders 3. Tenant APIs > Credential issuer and Define your own credential. Issuer configuration shows a complete effective example.
Next journey
Continue with Issue credentials.