This topic describes how to configure the Encrypted Content Store.
The Encrypted Content Store is configured using the properties in the SkyVault-global.properties file and can be administered using JMX.
Set up encryption properties using SkyVault-global.properties file
To configure the Encrypted Content Store, set the configuration properties in the
SkyVault-global.properties file. For example, here is a set of properties
which configure the default Java JCE provider implementation with two master keys (override the
cryptodoc.jce.providerName property to configure a specific
provider).
filecontentstore.subsystem.name=encryptedContentStore cryptodoc.jce.keystore.path=<path_to_the_keystore> cryptodoc.jce.keystore.password=<master_password_for_the_keystore> cryptodoc.jce.key.aliases=<alias_for_the_key> cryptodoc.jce.key.passwords=<password_for_the_key_itself> cryptodoc.jce.keygen.defaultSymmetricKeySize=128For detailed information on these properties, see Encrypted Content Store properties.
Note: On Enterprise, properties edited using JMX are
persisted and will override any settings in the SkyVault-global.properties
file. Use the JMX client to change the configuration properties on Enterprise.
Set up encryption properties using JMX client
You can configure the Encrypted Content Store using the JMX client, such as JConsole on the JMX MBeans > SkyVault > Configuration > ContentStore > managed > encrypted > Attributes tab.
