Update holder global configuration

PUT 
/v2/config/digital-wallet/openid/holder/global-configuration

Updates the holder global configuration for OID4VCI and OpenID4VP flows. An organisation has one holder global configuration, so the path has no identifier.

Send only the fields that you want to change. A field that you leave out keeps its stored value. Do not send null for supportCredentialEncryption: the wallet answers HTTP 400.

Request

application/json

Body

required

The settings to change. A field that you leave out keeps its stored value.

supportCredentialEncryption boolean

When true, the wallet accepts encrypted OID4VCI Credential Responses. Send a JSON boolean; null gives HTTP 400.

refreshCredentialStatusInterval integer

Interval in seconds between two credential revocation status checks. Use 0 to stop the automatic checks.

redirectUrl string

Redirect URL that the wallet sends in the OAuth 2.0 Authorization Request during OID4VCI credential issuance. Give an absolute URL, or an empty string to use the callback URL of the wallet.

requirePushedAuthorizationRequests boolean

When true, the wallet uses a Pushed Authorization Request (PAR) for the OID4VCI Authorization Code flow.

Responses

200

The wallet updated the holder global configuration.

Response Headers

application/json

Schema

Schema

globalConfiguration object

Global configuration of the holder wallet. It holds the settings that every OID4VCI and OpenID4VP flow of the organisation uses.

id stringrequired

Record identifier of the holder global configuration. The service makes this value when it saves the record. It has the same value as holderGlobalConfigurationId.

holderGlobalConfigurationId stringrequired

Unique identifier of the holder global configuration. An organisation has one holder global configuration, so the read and update operations do not use this value.

openIdOrganisationId stringrequired

Identifier of the digital wallet deployment that holds this configuration.

supportCredentialEncryption booleanrequired

When true, the wallet accepts encrypted OID4VCI Credential Responses. The default is false.

refreshCredentialStatusInterval integerrequired

Interval in seconds between two credential revocation status checks. 0 stops the automatic checks. The default configuration uses 86400 (one check each day).

redirectUrl stringrequired

Redirect URL that the wallet sends in the OAuth 2.0 Authorization Request during OID4VCI credential issuance. When no URL is set, the wallet uses its own callback URL, and this field shows that URL.

requirePushedAuthorizationRequests booleanrequired

When true, the wallet uses a Pushed Authorization Request (PAR, RFC 9126) for the OID4VCI Authorization Code flow. The default is false.

createdAt numberrequired

Unix timestamp (in seconds) when this configuration was created.

updatedAt numberrequired

Unix timestamp (in seconds) when this configuration was last modified.

Example (from schema)

{
  "globalConfiguration": {
    "id": "b7d1f4a2-8c3e-4a91-9f52-0d3c6e7a1b45",
    "holderGlobalConfigurationId": "b7d1f4a2-8c3e-4a91-9f52-0d3c6e7a1b45",
    "openIdOrganisationId": "string",
    "supportCredentialEncryption": false,
    "refreshCredentialStatusInterval": 86400,
    "redirectUrl": "https://wallet.example.com/callback",
    "requirePushedAuthorizationRequests": false,
    "createdAt": 1747011600,
    "updatedAt": 1747011600
  }
}

400

supportCredentialEncryption is null, a field is unknown or has the wrong JSON type, refreshCredentialStatusInterval is negative, or redirectUrl is not an absolute URL.

Response Headers

application/json

Schema

Schema

errorCode integerrequired
errorDescription stringrequired

Example (from schema)

{
  "errorCode": 400,
  "errorDescription": "Bad input parameter"
}

401

Unauthorized

Response Headers

application/json

Schema

Schema

errorCode integerrequired
errorDescription stringrequired

Example (from schema)

{
  "errorCode": 400,
  "errorDescription": "Bad input parameter"
}

404

Global configuration not found. The wallet makes the configuration when it deploys the organisation wallet, so this error comes only when that step failed. There is no create operation: contact support.

Response Headers

application/json

Schema

Schema

errorCode integerrequired
errorDescription stringrequired

Example (from schema)

{
  "errorCode": 400,
  "errorDescription": "Bad input parameter"
}

500

Internal server error

Response Headers

application/json

Schema

Schema

errorCode integerrequired
errorDescription stringrequired

Example (from schema)

{
  "errorCode": 400,
  "errorDescription": "Bad input parameter"
}

Loading...