Appendix B. Encryption Key Manager Configuration Properties Files; Encryption Key Manager Server Configuration Properties File - Dell PowerVault ML6000 User Manual

Dell powervault ml6000 encryption key manager user's guide
Hide thumbs Also See for PowerVault ML6000:
Table of Contents

Advertisement

Appendix B. Encryption Key Manager Configuration
Properties Files

Encryption Key Manager Server Configuration Properties File

The Encryption Key Manager requires two configuration property files: one for the
Encryption Key Manager server, and one for the CLI client. Each of these files is
treated and parsed as a Java.util.Properties load file, which imposes certain
restrictions on the format and specification of properties:
v Configuration properties are recorded one-per-line. The value(s) for a given
property extend to the end of the line.
v Property values, such as passwords, that contain spaces need not be enclosed in
quotation marks.
v Keystore passwords must not be greater than 127 characters in length.
v Accidental whitespace at the end of a line may be interpreted as part of a
property value.
Sample configuration properties files are available for download at
http://support.dell.com in the EKMServicesandSamples file.
The following comprises the complete set of properties in the Encryption Key
Manager server configuration file (KeyManagerConfig.properties). The order of
property settings in the file does not matter. Comments may appear in the file. To
add a comment, use a "#" in the first column of a line.
Note: Changes made to the KeyManagerConfig.properties file may be lost at
shutdown. Therefore, be sure the Encryption Key Manager server is not
running before editing configuration properties. To stop the Encryption Key
Manager server issue the stopekm command from the CLI client. Your
changes are activated when the Encryption Key Manager server is restarted.
Admin.ssl.ciphersuites = value
Specifies the cipher suites to be used for communication between
Encryption Key Manager servers. A cipher suite describes the
cryptographic algorithms and handshake protocols Transport Layer
Security (TLS) and Secure Sockets Layer (SSL) use for data transfer.
Required
Values
Default
Admin.ssl.keystore.name = value
This is the name of the database of key pairs and certificates used for
Secure Socket Layer client operations such as sync commands between
Encryption Key Manager Servers. In a sync operation, the certificate that
the Secure Sockets client presents to the Secure Sockets server comes from
this keystore.
Required
Optional.
Possible values are any cipher suites supported by
IBMJSSE2.
JSSE_ALL
Optional. Used only with sync command. Defaults to value
of config.keystore.file property.
B-1

Advertisement

Table of Contents
loading

Table of Contents