Create a Vault Entry

Manage an Organization Coveo Relevance Cloud System Administrator Product Documentation

In this article

Example

Vault entries are sensitive and restricted key-value pairs stored in the Vault API of the Coveo Migration Service. The service uses these entries to migrate sensitive information leveraged by your resources, such as credentials used to index content. You can also use vault entries in indexing pipeline extensions (IPEs).

Note

When using the Migration Service to apply a snapshot to an organization, you can typically use a purpose-built Import vault parameters button to automatically import vault parameters from the origin organization.

If there remain missing vault entries after the import, you need to create them manually.

This article provides an example that shows you how to create vault entries using the POST /vaultentries endpoint.

Example

You want to apply a snapshot to an organization, but you receive an error message when checking the prerequisites, because a vault entry with the following key is missing: originorganizationid_iyn07x-configuration.parameters.secretKey.value. It’s used as a credential by one of your sources. You try pressing the Import vault entries button, but it has no effect because you have deleted the vault entry from the origin organization.

You therefore use the POST /vaultentries endpoint to create the target vault entry in your destination organization.

POST https://platform.cloud.coveo.com/rest/organizations/destinationorganizationid/vaultentries HTTP/1.1
Accept: application/json
Content-Type: application/json

Request payload:

{
  "attributeReferences": [
    {
      "jsonPath": "configuration.parameters.secretKey.value", 
      "resourceName": "originorganizationid_iynO7X", 
      "resourceType": "SOURCE"
    }
  ],
  "key": "originorganizationid_iyn07x-configuration.parameters.secretKey.value", 
  "value": "s8h#kj%43s", 
  "organizationId": "destinationorganizationid", 
  "valueType": "STRING",
  "vaultVisibilityType": "OBFUSCATED"
}

	To determine the `jsonPath` value, you open the snapshot JSON content to find out the path to the target key from its parent resource model. In this case, it’s `configuration.parameters.secretKey.value`. `// ... "SOURCE": [ { "model": { // ... "configuration": { // ... "parameters": { // ... "secretKey": { "sensitive": true, "value": "{{ VAULT.originorganizationid_iynO7X-configuration.parameters.secretKey.value }}" } }, // ... } // ... } // ... "resourceName": "originorganizationid_iynO7X" } ] // ...`
	The `resourceName` of the migrated resource, which you can find in the snapshot JSON content as well.
	The `key` of the missing vault entry you are creating, namely `originorganizationid-configuration.parameters.secretKey.value`.
	Then, you set the vault entry `value` to `s8h#kj%43s`, which is the credential needed to access the content your source indexes.
	You set the unique identifier of the destination organization as the value of the `organizationId` parameter.

After sending this request, you go back to the Administration Console and check that your snapshot prerequisites are now satisfied.

Successful migration check after adding vault entry

Was this article useful?

What's next for me?