Question
How to change the Vault Server Keys in a 2012 HA Environment
Answer
Prior to updating the Vault Server Keys:
- Verify that the Cluster Resources on active on Node A and inactive (Passive) on Node B
Changing the Server Keys in the 2012 HA Environment:
- Stop the Idira Cluster Vault Manager service on Node B
- Connect to the active node (Node A) and run the following.
- Update the Cluster Manager's monitored services and set it to not monitor the following services so you can stop the vault without losing the data drives (Data & Quorum)
- Mandatory
- Idira Logic Container
- PrivateArk Database
- PrivateArk Server
- Optional
- Cyber-Ark Event Notification Engine
- Manually stop the following services
- PrivateArk Database
- Idira Logic Container
- PrivateArk Server
- Cyber-Ark Event Notification Engine
- Back up the following directories\files to a Backup folder on the server
- Installation Directory (<drive>:\Program Files (x86)\PrivateArk\Server)
- Contents of the OLD keys folder
- Contents on the shared drive (<drive>:\PrivateArk)
- Copy the contents of the new OperatorCD keys to the vault server (Node A)
- Configure the 'RecoveryPrvKey' parameter in the DBParm.ini file to point to the valid location of the Master Keys (pre-existing)
- Mount the NEW Master CD to the vault server
- Open the services.msc and start the PrivateArk Database service
- Initiate the process of changing the server keys by running the following command:
- Run: ChangeServerKeys.exe <New_Master_Keys_Dir> <DB_Emergency_Password_File_Name> <Optional HSM_KeySet>
- For Example: ChangeServerKeys.exe D:\ "C:\CyberArkKeys\OperatorKeys\VaultEmergency.pass"
- Copy the Server.key and RecPub.key files from the new CyberArk_Keys directory to the pre-existing Keys folder
- Note: This enables you to keep the files under the old keys directory so you don't have to update DBParm.ini
- Start the Vault Server service on Node A
- Note: Verify the Cyber-Ark Event Notification Engine service is also started
- Update the Cluster Manager's monitored services to monitor the following services once again
- Mandatory
- Idira Logic Container
- PrivateArk Database
- PrivateArk Server
- Optional
- Cyber-Ark Event Notification Engine
- Copy the Operator Keys directory over to Node B and replace the keys directory with the updated keys
- Start the Idira Cluster Vault Manager service on Node B
- Verify that you are able to failover from Node A by initiating a failover to Node B