Read verifier global configuration
GET/v2/config/digital-wallet/openid/verifier/global-configuration/:globalConfigurationId
Reads the global configuration of the OpenID4VP verifier by its identifier.
The organisation must have a deployed digital wallet. If it has none, the server answers with HTTP 400.
Request
Path Parameters
Unique identifier of the global configuration. Give globalConfigurationId for the issuer operations, holderGlobalConfigurationId for the holder operations, and verifierGlobalConfigurationId for the verifier operations. Do not give the id field of the record.
Header Parameters
Optional. Unique identifier of the sandbox organisation to use for this request. When you send this header, the service runs the operation in the context of the named sandbox organisation, that is, against the wallet of that sandbox organisation and not against the main wallet of the organisation. Leave the header out to use the main wallet.
The service reads this header only when you authenticate with a bearer access token. When you authenticate with an API key, the service takes the sandbox organisation from the API key and ignores this header. To run an API-key call in a sandbox organisation, bind the key to the sandbox organisation with PUT /v2/config/admin/apikey/{apiKeyId}/sandbox-org instead.
X-SubwalletId is the deprecated name of this header. The service continues to accept it, but X-SandboxOrgId wins if you send both headers.
The sandbox organisation must exist, must belong to your organisation and must be deployed. An unknown identifier, an identifier of a sandbox organisation that is not deployed, and an identifier that belongs to a different organisation all make the call fail with HTTP 400.
Responses
- 200
- 400
- 401
- 500
The server found the verifier global configuration.
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
verifierGlobalConfiguration objectrequired
Global configuration of the OpenID4VP verifier. It holds the settings that every verification request of the organisation uses.
Record identifier of the verifier global configuration. The server makes this value when it saves the record. It is not the same value as verifierGlobalConfigurationId.
Unique identifier of the verifier global configuration. Use this identifier to read, update or delete the record.
Identifier of the digital wallet deployment that holds this configuration.
When true, the verifier accepts an encrypted OpenID4VP Authorization Response, that is a response mode of direct_post.jwt or dc_api.jwt.
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.
Unix timestamp in seconds when the server made this configuration.
Unix timestamp in seconds when the server last changed this configuration.
{
"verifierGlobalConfiguration": {
"id": "665f2b8c9a1d4e0012ab34cd",
"verifierGlobalConfigurationId": "b7d1f4a2-8c3e-4a91-9f52-0d3c6e7a1b45",
"openIdOrganisationId": "string",
"supportCredentialEncryption": true,
"presentationRequestExpiresIn": 3600,
"createdAt": 1747011600,
"updatedAt": 1747011600
}
}
The organisation is unknown, the organisation has no deployed digital wallet, the digital wallet deployment is not resolved, or no configuration has the supplied globalConfigurationId.
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
{
"errorCode": 400,
"errorDescription": "Bad input parameter"
}
Unauthorized
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
{
"errorCode": 400,
"errorDescription": "Bad input parameter"
}
Internal server error
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
{
"errorCode": 400,
"errorDescription": "Bad input parameter"
}