KB 246 (CLOUD): PowerConnect Cloud - Rotating the Keystore Password
|
Category: Information |
Priority: Normal |
|---|---|
|
Platform: Cloud |
Version: 1 from 05.08.2026 |
Overview
POWERCONNECT_SECRET environment variable is the password for PowerConnect's keystore, which holds stored credentials and certificates. From 9.2.1 it also helps identify the cluster, so every node in a cluster must use the same value.
Changing the environment variable on its own is not enough. The keystore must be re-protected with the new value first, otherwise PowerConnect cannot read its stored credentials.
You need to follow these steps when you:
-
change the secret, for example as part of a password rotation policy
-
upgrade a cluster to 9.2.1 whose nodes currently use different secrets
Before you start
-
Plan a short outage. All nodes in a cluster must be stopped while the secret is changed.
-
Use the keytool from the Java installation PowerConnect runs on. It must be Java 11 or later.
-
Have the current secret and the new secret ready.
Steps
-
Stop PowerConnect on all nodes.
-
On each node, back up the keystore:
<POWERCONNECT_HOME>/secrets/powerconnect.keystore -
On each node, change the keystore password:
keytool -storepasswd -storetype PKCS12 -keystore <POWERCONNECT_HOME>/secrets/powerconnect.keystorekeytool prompts for the current secret, then the new secret twice. Entering them at the prompts keeps them out of your shell history.
If the nodes currently use different secrets, enter each node's own current secret here and the same new secret on every node.
-
Set POWERCONNECT_SECRET to the new value on every node (this may need to be done in the systemd configuration if you are using systemd to manage PowerConnect).
-
Start the nodes one at a time, waiting for each to finish starting before starting the next.
Blobstore datastore
If PowerConnect uses the blobstore datastore, the keystore is the powerconnect.keystore object under your DATASTORE_PREFIX. Download it, run step 3 against the downloaded file, and upload it back before starting PowerConnect.
Checking the change
On each node, check the startup log:
-
There is no Failed to load keystore message.
-
Every node logs the same Hazelcast cluster name.
Then open the PowerConnect UI and test an input and an output that use stored credentials.
Restoring
If a node cannot read its keystore after the change, stop it, restore the keystore backup from step 2, set POWERCONNECT_SECRET back to the previous value and start it again. In a cluster, revert every node so they all use the same secret.