Authenticate to Veeva Vault
After you add the connector, you need to set the required properties. URL: Enter the URL for your Veeva Vault host (for example, https://MyVault.veevavault.com). supports authenticating to Veeva Vault in several ways. Select your authentication method below to proceed to the relevant section that contains the authentication details.Basic
Azure Active Directory
To connect with your Azure Active Directory credentials, specify the following properties:- Auth Scheme: Select AzureAD.
- Azure Tenant: Enter the Veeva Vault tenant that is used to access data, either by name (for example, contoso.omnicrosoft.com) or by identifier (Id).
- OAuth Client Id: Enter the client Id that you were assigned when you registered your application with an OAuth authorization server.
- OAuth Client Secret: Enter the client secret that you were assigned when you registered your application with an OAuth authorization server.
- (Optional) Open ID Connect Profile ID: Enter the Id of your OAuth2.0 / Open ID Connect profile.
Azure Active Directory with OpenID Connect
To connect via OpenID Connect with Azure Active Directory, specify the following properties:- Auth Scheme: Select AzureADOpenID.
- OAuth JWT Cert: Enter your Java web tokens (JWT) certificate store.
- OAuth JWT Cert Type: Enter the type of key store that contains your JWT Certificate. The default type is PEMKEY_BLOB.
- (Optional) OAuth JWT Cert Password: Enter the password for your OAuth JWT certificate.
- (Optional) OAuth JWT Cert Subject: Enter the subject of your OAuth JWT certificate.
Okta
- SSO Exchange Url: Enter the URL that is used for consuming the SAML response and exchanging it for service specific credentials.
Veeva Vault as a Reverse ETL Destination
In the application, you can configure Veeva Vault as a reverse ETL destination so that it can receive processed data from the source warehouse. As a reverse ETL destination, Veeva Vault supports all three transfer modes (Insert, Upsert, and Update). In Veeva Vault, updates are matched by using either the object’s primary key (or a system-generated identifier) or unique columns. For Upsert mode, only unique columns are used for matching. Note: Bulk operations for Insert, Upsert, and Update are supported only for the current Veeva Vault API. Transfer-Modes Summary| Mode | Supported | Key Used for Matching | Bulk Support | Notes |
|---|---|---|---|---|
| Insert | Yes | N/A (always creates new records) | Yes (with current API) | Creates new records in Veeva Vault. |
| Update | Yes | Primary key (or system-generated Id) or unique columns | Yes (with current API) | Updates existing records. |
| Upsert | Yes | Unique columns | Yes (with current API) | Updates existing records if a matching key or unique column exists. If no match exists, a new record is inserted. |
Complete Your Connection
To complete your connection:- Define advanced connection settings on the Advanced tab. (In most cases, though, you should not need these settings.)
- If you authenticate with AzureAD or AzureADOpenID, click Connect to Veeva Vault to connect to your Veeva Vault account.
- Click Create & Test to create your connection.