Citrix Secure Developer Spaces™

Use HashiCorp Vault as a Secret Manager

October 9, 2025

Contributed by:

You can use HashiCorp Vault to store all platform secrets instead of encrypting them in MongoDB.

Citrix Secure Developer Spaces™ (SDS) Platform connects to HashiCorp Vault using the JWT authentication mechanism provided by Kubernetes.

For more information, see Use Kubernetes for OIDC authentication

Prerequisites

The configuration depends on whether your Vault instance is deployed in the same Kubernetes cluster as the SDS Platform:

If Vault is deployed in the same cluster:
The OpenID Connect (OIDC) issuer endpoint is automatically reachable.
If Vault is deployed in a different cluster:
Ensure that the OIDC issuer endpoint of the SDS cluster is reachable by Vault.
If it isn’t, you must manually add the signing public key(s) of the SDS cluster.
For details, see Use Kubernetes for OIDC authentication

Configuration

You can configure Vault in the SDS Platform using the following four Helm chart values:

# hashicorpVault:
#   If set, secrets are stored in Vault instead of the database.
#   vaultAddress: "https://example.com:8200"
#   vaultRoleName: "sds-role"
#   customMountPath: "" # Default is "secret"
#   vaultCertB64: ""    # Base64-encoded PEM CA certificate (optional)
<!--NeedCopy-->

Parameter descriptions

Parameter	Description
vaultAddress	Specifies the Vault address. The Vault instance must be accessible from the SDS cluster. All platform services use this address to store and retrieve secrets.
vaultRoleName	Specifies the name of the Vault role configured for SDS. If different Kubernetes services use different service accounts, the `bound_subject` field may vary. You can omit this field when creating the role.
customMountPath	Specifies the Vault path where secrets are stored. Optional. Defaults to `secret`.
vaultCertB64	Specifies the Base64-encoded TLS certificate for Vault. Use this setting if Vault uses a self-signed certificate. Optional.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Use HashiCorp Vault as a Secret Manager

October 9, 2025

Contributed by:

October 9, 2025

Contributed by:

Use HashiCorp Vault as a Secret Manager

Prerequisites

Configuration

Parameter descriptions

In this article