Skip to main content

Configuration for Issuing Credentials

This page provides a map of the most relevant configurations for credential issuers. For the complete list of all available configurations, see the Core Configuration Reference.

Basics​

KeyAt a glanceDocumentation
formatWhich credential formats you can issue, plus per-format defaults such as credential lifetime and revocation method.Reference
issuanceProtocolHow credentials are offered and delivered to wallets via OpenID4VCI, including token and code lifetimes, DPoP, redirect URIs and the offer URL scheme.
revocationMethods for revoking or suspending issued credentials, and status list sizing.Reference
transportChannels available for exchanging credentials. Issuance runs over HTTP.Reference
datatypeValidation rules for claim values in your credential schemas, such as patterns, numeric and date ranges, and allowed file types.
globalSettings.credentialSchema.maxExpirationSecondsUpper limit on the expiration a credential schema can set. Defaults to 10 years.Reference
globalSettings.credentialSchema.maxBatchSizeUpper limit on the batch size a credential schema can set. Defaults to 20.Reference

Identifiers and keys​

KeyAt a glanceDocumentation
identifiersWhich identifier types (X.509 certificate, CA, key, DID) you can use as an issuer.Reference
keyAlgorithmSigning algorithms available for issuer key.Reference
keyStorageWhere issuer keys are kept, such as the encrypted internal database or Azure Key Vault.Reference
didDID methods available for DID-based issuer identifiers, and limits on the keys each DID can hold.Reference
signerSigners that issue X.509 certificates from a CA identifier, including the settings needed for mdoc issuer CAs.Reference

Ecosystems​

KeyAt a glanceDocumentation
ecosystemConstraints for regulatory ecosystems such as which schema IDs the ecosystem recognizes and which ones count as PID.Reference
trustListSubscriberTrust list types your instance can subscribe to, for checking whether other parties are trusted.Reference

System​

KeyAt a glanceDocumentation
app.coreBaseUrlBase URL of your Core instance. Wallets and verifiers use this domain to reach Core.
globalSettings.defaultLanguageFallback language (BCP 47, default en) used where none is specified, such as during credential schema creation.