1.9 Appliance Keys and Source Credentials
Key Takeaways
VA-based connector credential encryption uses a 2048-bit RSA public key associated with the cloud cluster and a private key on the VA.
For standard setup, configure the same cluster key passphrase on each VA before it is paired.
The credential encryption pair, a virtual machine’s administrative login key, and a target’s TLS certificate serve different purposes.
When switching to a different VA cluster in a disaster recovery design, follow SailPoint’s procedure to reenter the source credentials.
Follow one secret through the design
For a direct connector that uses a virtual appliance, SailPoint documents a credential encryption design with a 2048-bit Rivest–Shamir–Adleman (RSA) asymmetric key pair. The cloud has the public key associated with the VA cluster and can use it to encrypt the credential. A VA keeps the private key used to decrypt it on the customer side when it communicates with the source. This protects the credential separately from the encrypted transport the VA uses to reach cloud services.
The key layout applies to the documented VA-based connector design. A SaaS connector has no customer VA and can use a cloud-managed key pair. Check the connector category before answering where decryption occurs. The fact that a source account is hosted externally does not settle the question. The connector architecture is what determines whether customer-managed appliance infrastructure participates.
| Item | Role in this deployment | Design consequence |
|---|---|---|
| Cluster credential encryption public key | Cloud-side encryption of a VA-backed source credential | The source association determines which VA cluster’s encryption design applies |
| Credential encryption private key | Decryption on the appliance | Keep the appliance in an appropriate private network and use documented appliance controls |
| Cluster key passphrase | Input to the standard VA’s key setup | Each member of the same cluster uses the same value |
| Pairing code | Registers the running VA with its tenant entry | Submit the newly generated code within the documented window |
| Platform login credential or key | Administers the VM through a supported platform or shell path | Follow the hosting platform’s access procedure |
| Target certificate and trust configuration | Establishes the target’s identity in a TLS-protected connection | Follow the connector’s trust and port requirements |
Check the setup sequence
In standard VA setup, the engineer uses va-bootstrap set-passphrase before calling va-bootstrap pair. SailPoint explains that each VA contains the private RSA key generated from the selected key passphrase. Use the identical passphrase when configuring another member of the same cluster. Keep the original cluster value according to the organization’s approved secret handling process since future additions need it.
Pairing associates the VA with the intended cluster and tenant. It is a different action from setting the passphrase. A distinct platform key pair selected when launching an Amazon Web Services instance belongs to the hosting environment. Likewise, a source certificate used for Transport Layer Security (TLS) on the connector-to-target leg does not provide the source credential decryption key. If a connection test fails because the directory certificate has expired, remedy the certificate problem with the documented configuration. A new tenant pairing is unrelated to that symptom.
SailPoint’s standard setup automatically encrypts the configured passphrase, and its documentation identifies the protected representation by its leading colons. The protected representation and the original input supplied during setup serve different operational purposes. Avoid passing a value from another cluster into a new member’s setup by choosing the correct secret record first. If a setup question gives three strings, identify which one is a local login credential, which value belongs to the cluster, and which code expires once its pairing window has passed.
Worked recovery decision
An organization plans to add a third appliance to the active production cluster for extra capacity. Configure it using the existing cluster passphrase before pairing it with that cluster. Verify the intended environment, bootstrap and pair the addition, and then test the relevant source route. The procedure for ordinary capacity expansion is to give the new member the same cluster context.
Now consider a planned switch to a separately deployed disaster recovery cluster. The source configuration needs to point to the recovery cluster, and SailPoint specifies reentering the source credentials when switching clusters. Keep those credentials available through the organization’s approved access process and verify the target connection afterward. An existing pairing code or cloud public key is insufficient to recover the original plaintext credential. The design relies on the VA holding the corresponding private key. Plan the operator’s access to the service credential as part of the recovery, and verify the destination independently.
See SailPoint’s connectivity encryption model, passphrase setup and VA placement and connector-side TLS setup.
An engineer traces a direct VA-based connector’s saved credential. Which locations match SailPoint’s documented RSA design?
Both keys are stored only in the connected target’s trust store
The cloud decrypts with its private key and the VA stores only a public key
The cloud has the cluster’s public key for encryption and the VA has the private key for decryption
The cloud and VA use the pairing code as the RSA private key
Which input should an engineer reuse when adding a VA to an existing standard cluster?
The cluster’s current key passphrase before generating a pairing code for the new VA
The previous member’s expired pairing code as the new appliance password
The source’s client certificate as the appliance login key
The cloud’s public encryption key as the target’s password
Sections you finish are checked off in the contents.