...
Master keyrotation required in case of it compromising is required if it has beencompromisedor at the end of the crypto period (key validity period).
Design assumes that , an administrator will provide an ability to get a new master key by EncryptionSPI
from underlying storage.
...
New master key should must be available to EncryptionSPI
for each server node. The cluster should must be active.
Users can control the master key rotation process key via some kind of user interface(CLI, JMX, Java API).
...
Each phase is a distributed process.
The goal is to verify that all server nodes have the same master key. A The server node starts begins prepare phase with the MasterKeyChangeRequest
that contains:
...
Each server node executes the following actions:
It obtains Obtains a digest of a new master key. If the digest is unavailable then , the process completes with the an error.
The coordinator starts the perform phase when the prepare phase is completed without errors.
...
The coordinator node starts the prepare phase with the MasterKeyChangeRequest
that contains:
...
Each server node executes the following actions:
ChangeMasterKeyRecord
) that consist of:MetaStore
.Distributed process is a cluster-wide process that accumulates single nodes results to finish itself.
...
InitMessage
sent via discovery.SingleNodeMessage
sent via communication.FullMessage
sent via discovery.Several processes of one the same type can be started at the same time.
...
The process completes when the perform phase completed (all nodes was have been re-encrypts encrypted their keys).
...
If some node was unavailable during master key rotation process it will unable to join to the cluster because it has old master key.
To update this node user should run ignite Ignite with system property (IGNITE_MASTER_KEY_NAME_TO_CHANGE_BEFORE_STARTUP=newMasterKeyName
)
The node will re-encrypt cache keys with new MK and try to join to the cluster.
A node should not try to join to the cluster before the process of ChangeMasterKeyRecord
. Regardless of whether the key rotation was finished successfully or not, the recovery will will be from the record.
ChangeMasterKeyRecord
in the process node recovery it was passed to EncryptionManager
.EncryptionManager
writes new cache group keys to it....
Reject node join. It may lead to inconsistent master keys in cluster.
...
Cache keys must not be created during the master key rotation process. So, a node will throw an exception if a user users will start cache during the key rotation process. Moreover, if group keys were generated before the master key was change, starting the cache start will be rejected (case of client node starts the cache).
...
...
The node Node will process the critical failure error failure. Failure handler must stop the node to prevent inconsistent keys in the cluster.
...
setMasterKeyName(String masterKeyName)
// Sets "current" master key nameString getMasterKeyName()
// Gets "current" master key nameFollow The following methods will work with master key that setted was set by previous method:
byte[] masterKeyDigest()
byte[] encryptKey(Serializable key)
Serializable decryptKey(byte[] key)
This is necessary so that ignite Ignite can decrypt cache keys with the old master key and encrypt with the new one.
...
Meta storage will store name of master key name. Key name from meta storage has a higher priority to key name from EncryptionSpi
.
Currently, the joining node send sends hash MK for validation in attributes. Attributes can't be modified at runtime. So the joining node will send hash MK in JoiningNodeDiscoveryData
.
...