Set up an OpenID4VP wallet provider
To allow customers to sign in using an OpenID4VP-based wallet, configure a wallet provider in Enterprise login.
The provider configuration defines how Strivacity communicates with the wallet, verifies the presented credentials, and maps wallet claims to Strivacity native claims.
OpenID4VP wallet providers are available for customer authentication only. They cannot be configured as admin login providers.
Create the login provider
- In the Admin Console, go to Identities → Enterprise login.
- Select Create.
- Under OpenID4VP-based wallets, select Wallet.
- Complete the settings in the General tab.
- Complete the settings in the Configuration tab.
- Select Save.
General
The General tab defines how the provider is identified and presented to customers.
| Field name | Description |
|---|---|
| Name | Enter a display name for the provider. |
| Description | Optional. Add notes to help other administrators identify the configuration. |
| Policy tag | Select an optional tag to apply to this provider. |
| Login button text | Customize the text displayed on the login button for this provider. |
| Login button logo URL | Enter a URL for the logo shown on the login button. |
Configuration
The Configuration tab defines how Strivacity communicates with the wallet and verifies the credentials it presents.
Wallet request settings
| Field name | Description |
|---|---|
| Client ID scheme | Defines how the client ID is presented to the wallet. The supported value is x509_hash. |
| Request URI method | Select the HTTP method the wallet uses to retrieve the authorization request. Select GET or POST according to the wallet provider requirements. |
| Authorization endpoint | Enter the authorization endpoint used to initiate the wallet request. The default value is openid4vp://. The required value depends on the wallet provider. |
Issuer trust
Trusted list URL specifies the trust list Strivacity uses to verify the issuer of credentials returned by the wallet.
Enter the trusted list URL provided for the integration.
Identifier mapping
Use Identifier mapping to define how Strivacity identifies the account represented by the wallet credentials.
Select one of the following:
- Get from a claim: Use a claim returned by the wallet as the identifier.
- Use custom identifier: Generate an identifier when the wallet does not provide a suitable unique claim.
When using a claim, you can select the claim to use as the identifier after the provider has been created.
Access certificate
The access certificate and private key are used to sign authorization requests sent to the wallet.
Upload the certificate and corresponding private key provided for the integration. Certificates and private keys are accepted in PEM format.
After the provider is created, the current certificate details are displayed under Current certificate.
Registration certificate
Upload the registration certificate provided for the integration. The registration certificate is a JWT file and determines which claims are available for the wallet provider.
After the provider is created, details from the certificate are displayed under Current registration certificate.
Claims
After you save the provider, Strivacity determines the available claims from the registration certificate.
Open the Claims tab to configure the claims returned by the wallet.
For each claim:
- Use the Enabled toggle to include or exclude the claim.
- Under Native claim, select the Strivacity native claim to which the value should be mapped.
- If Identifier mapping is set to Get from a claim, enable Use as identifier for the claim that uniquely identifies the account.
Only one claim can be selected as the identifier.
Select Save after configuring the claims.
Custom identifier
If the wallet does not provide a suitable unique identifier claim, set Identifier mapping to Use custom identifier and save the configuration.
Open the Custom identifier tab to define how the identifier is calculated. The editor provides the following inputs:
| Input | Description |
|---|---|
request_body | The request body of the token request. |
claims | The claims passed to the function. |
account | The subject user. |
The function must return an Identifier object containing the calculated identifier. You can calculate the identifier from one or more claims returned by the wallet.
Select Save after configuring the custom identifier.
Custom identifier logs
When Identifier mapping is set to Use custom identifier, use the Customer identifier logs tab to review logs generated by the custom identifier code.
The log list shows the date and log level counts for each entry. Select Refresh to update the list.
Updated about 2 hours ago

