Azure Key Vault Secret Path Expressions

For information on how to configure the Azure Key Vault credential provider, refer to Azure Key Vault.

Username and Password

Note

The reference examples provided on this page are for Secrets; similarly, follow the same approach for Keys and Certificates.

Before Encoding

Using Secret ARN:

secrets://azure-key-vault/https://jubileecpkeyvault.vault.azure.net/keys/HarshalFirstKey/value

Note

It is recommended to omit the version ID from secret, key, or certificate identifiers to always fetch the latest value.

Example: The secret identifier below includes a version ID:

https://jubileecpkeyvault.vault.azure.net/secrets/HarshalFirstKey/e5a9dd5cc1284a4caa5bef8cd733feab

The recommended approach is to omit the version ID from the identifier, ensuring that the latest value is always retrieved:

https://jubileecpkeyvault.vault.azure.net/secrets/HarshalFirstKey

Important

The URL path should always start with the prefix, secrets://. Each attribute in the URL path must be URL-encoded. Each URL attribute in the path is case-sensitive.

After Encoding

After you encode the URL path, it should appear as follows:

Using Secret ARN:

secrets://azure-key-vault/https%3A%2F%2Fjubileecpkeyvault.vault.azure.net%2Fkeys%2FHarshalFirstKey/value

The following is an explanation of the attributes of this URL:

azure-key-vault - Configured Credential Provider on SailPoint.
https%3A%2F%2Fjubileecpkeyvault.vault.azure.net%2Fkeys%2FHarshalFirstKey - Secret Identifier of the secret.
value - The name of the secret which needs to be fetched from the JSON response.

Tip

Use urlencoder.org to encode your URL attributes.

Prefixes and Suffixes

If any secret paths have a prefix or a suffix, you must append a query parameter to the secret path as follows:

To add a prefix - ?prefix=<prefix>. For example, if the secret value returned after evaluation is LocalAdmin, but the complete value required by the secret field is DomainOne\LocalAdmin then the secret path expression will be as follows to add the required prefix:
```
secrets://azure-key-vault/https%3A%2F%2Fjubileecpkeyvault.vault.azure.net%2Fkeys%2FHarshalFirstKey/value?prefix=DomainOne%5C
```
To add a suffix - ?suffix=<suffix>. For example, if the secret value returned after evaluation is localadministrator, but the complete value required by the secret field is localadminstrator@sp.com then the secret path expression will be as follows to add the required suffix:
```
secrets://azure-key-vault/https%3A%2F%2Fjubileecpkeyvault.vault.azure.net%2Fkeys%2FHarshalFirstKey/value?suffix=%40sp.com
```
To add a prefix and suffix - ?prefix=<prefix>&suffix=<suffix>. For example, if the secret value returned after evaluation is LocalAdmin, but the complete value required by the secret field is DomainOne\LocalAdmin@sp.com then the secret path expression will be as follows to add the required prefix and suffix:
```
secrets://azure-key-vault/https%3A%2F%2Fjubileecpkeyvault.vault.azure.net%2Fkeys%2FHarshalFirstKey/value?prefix=DomainOne%5C&suffix=%40sp.com
```

Important

All input parameters must be encoded.

Standard format for credential path:

secrets://{credential-provider-source}/{secret-identifier}/{secret-key}?prefix=someValue&suffix=someValue2

Important

Prefix and suffix are optional.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.