Fabric Master Key Management defines how the platform generates, protects, and controls the master encryption key used to secure data encryption keys in Fabric, either through Fabric’s internal key management or through integration with an external enterprise KMS.
Using the Fabric-Managed Master Key model, the Fabric platform manages the master encryption key internally. Fabric generates the master key and securely stores it within the platform environment, where it is used to protect the encryption keys that secure sensitive data stored by Fabric.
This approach is appropriate for deployments where an external enterprise Key Management Service (KMS) is not required. It provides strong encryption with minimal operational complexity, as Fabric handles the lifecycle of the master key within the platform while maintaining the encryption hierarchy used to protect data at rest.
For more information about Fabric master key management, please review this topic.
Set the MASTERKEY_KEY_STORE_ENABLED parameter of the config.ini file to false (default) to generate a master key without a KeyStore.
Set the MASTERKEY_KEY_STORE_ENABLED parameter of the config.ini file to true.
After adding the encryption module to the fabric-server-start.sh module, create the Keystore folder under the k2view home directory for all nodes:
cd $K2_HOME
mkdir .keystore
Run the keytool command on the coordinator node:
keytool -genseckey -alias masterkey_key_name -keyalg aes -keysize 256 -storepass <password> -keystore $K2_HOME/.keystore/fabric.keystore -storetype PKCS12
scp $K2_HOME/.keystore/fabric.keystore fabric@10.10.10.10:/$K2_HOME/.keystore/
sed -i "s@#KEY_STORE_LOCATION=.*@KEY_STORE_LOCATION=$K2_HOME/.keystore/fabric.keystore@" $K2_HOME/config/config.ini
sed -i 's@#KEY_STORE_PASSWORD=.*@KEY_STORE_PASSWORD= <password>@' $K2_HOME/config/config.ini
Fabric Master Key Management defines how the platform generates, protects, and controls the master encryption key used to secure data encryption keys in Fabric, either through Fabric’s internal key management or through integration with an external enterprise KMS.
Using the Fabric-Managed Master Key model, the Fabric platform manages the master encryption key internally. Fabric generates the master key and securely stores it within the platform environment, where it is used to protect the encryption keys that secure sensitive data stored by Fabric.
This approach is appropriate for deployments where an external enterprise Key Management Service (KMS) is not required. It provides strong encryption with minimal operational complexity, as Fabric handles the lifecycle of the master key within the platform while maintaining the encryption hierarchy used to protect data at rest.
For more information about Fabric master key management, please review this topic.
Set the MASTERKEY_KEY_STORE_ENABLED parameter of the config.ini file to false (default) to generate a master key without a KeyStore.
Set the MASTERKEY_KEY_STORE_ENABLED parameter of the config.ini file to true.
After adding the encryption module to the fabric-server-start.sh module, create the Keystore folder under the k2view home directory for all nodes:
cd $K2_HOME
mkdir .keystore
Run the keytool command on the coordinator node:
keytool -genseckey -alias masterkey_key_name -keyalg aes -keysize 256 -storepass <password> -keystore $K2_HOME/.keystore/fabric.keystore -storetype PKCS12
scp $K2_HOME/.keystore/fabric.keystore fabric@10.10.10.10:/$K2_HOME/.keystore/
sed -i "s@#KEY_STORE_LOCATION=.*@KEY_STORE_LOCATION=$K2_HOME/.keystore/fabric.keystore@" $K2_HOME/config/config.ini
sed -i 's@#KEY_STORE_PASSWORD=.*@KEY_STORE_PASSWORD= <password>@' $K2_HOME/config/config.ini