Update verifier global configuration

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

Updates the global configuration of the OpenID4VP verifier. An organisation has one verifier 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 server answers HTTP 400.

Request

application/json

Body

required

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

supportCredentialEncryption boolean

Set to true when the verifier accepts an encrypted Authorization Response for the direct_post.jwt response mode. A presentation definition with direct_post.jwt needs this value. The dc_api.jwt response mode does not need it.

presentationRequestExpiresIn integer

Possible values: >= 3600

Lifetime of an Authorization Request in seconds. The server writes this value to the exp claim of the request. The smallest value is 3600.

Responses

200

The server updated the verifier global configuration.

Response Headers

application/json

Schema

Schema

globalConfiguration objectrequired

Global configuration of the OpenID4VP verifier. It holds the settings that every verification request of the organisation uses.

id stringrequired

Record identifier of the verifier global configuration. It has the same value as verifierGlobalConfigurationId.

verifierGlobalConfigurationId stringrequired

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

openIdOrganisationId stringrequired

Identifier of the digital wallet of the organisation that holds this configuration.

supportCredentialEncryption booleanrequired

When true, the verifier accepts an encrypted Authorization Response for the direct_post.jwt response mode. Set it to true before you create a presentation definition with direct_post.jwt. The dc_api.jwt response mode does not need it. The default is false.

presentationRequestExpiresIn numberrequired

Lifetime of an Authorization Request in seconds. The server writes this value to the exp claim of the request. The smallest value is 3600, and the default is 3600.

createdAt numberrequired

Unix timestamp in seconds when the server made this configuration.

updatedAt numberrequired

Unix timestamp in seconds when the server last changed this configuration.

Example (from schema)

{
  "globalConfiguration": {
    "id": "b7d1f4a2-8c3e-4a91-9f52-0d3c6e7a1b45",
    "verifierGlobalConfigurationId": "b7d1f4a2-8c3e-4a91-9f52-0d3c6e7a1b45",
    "openIdOrganisationId": "string",
    "supportCredentialEncryption": true,
    "presentationRequestExpiresIn": 3600,
    "createdAt": 1747011600,
    "updatedAt": 1747011600
  }
}

400

supportCredentialEncryption is null, presentationRequestExpiresIn is smaller than 3600, or the organisation has no deployed digital wallet.

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...