Create a credential path
Use this task to define where inside a vault the file server credentials live. A credential path belongs to one vault and holds the lookup keys DCT uses to retrieve the username and password at runtime.
Steps
-
Go to Compliance > Delphix Infrastructure > Password Vaults and open the vault.
-
Select the Credential Paths tab.
-
Click + Credential Path.
-
Enter a Name and, optionally, a Description.
-
(Optional) Add tags: enter a Tag Key and Tag Value, then click + Tag.
-
In the Parameters field, enter the lookup parameters as JSON. See Credential parameter reference for the required keys. Click Format JSON to format the entry.
-
Click Create.
Credential parameter reference
The Parameters field accepts a JSON object. The required keys vary by vault type. These values are lookup keys and are not masked in the UI or API.
HashiCorp
{
"engineType": "KEY_VALUE_V2",
"engine": "secret",
"path": "sftp/credentials",
"usernameKey": "username",
"passwordKey": "password"
}
CyberArk
{
"queryString": "Safe=SftpSafe;Folder=Root;Object=sftp-creds"
}
Azure Key Vault
{
"vaultName": "your-keyvault-name",
"usernameKey": "sftp-username",
"passwordKey": "sftp-password"
}
vaultName is the name of the Azure Key Vault as shown in the Azure portal. usernameKey and passwordKey are the names of the secrets in that vault that hold the username and password.
GCP Secret Manager
{
"projectId": "999999999999",
"versionId": "latest",
"usernameKey": "sftp-username",
"passwordKey": "sftp-password"
}
projectId is the numeric project ID. Find it in the secret's path in the GCP console — for example, projects/999999999999/secrets/sftp-username. Use "latest" for versionId to always fetch the newest version, or enter an integer version number as a string to pin to a specific version.