dsconfig set-crypto-manager-prop — Modifies Crypto Manager properties
dsconfig set-crypto-manager-prop
{options}
The dsconfig set-crypto-manager-prop command takes the following options:
--set {PROP:VALUE}
Assigns a value to a property where PROP is the name of the property and VALUE is the single value to be assigned. Specify the same property multiple times in order to assign more than one value to it.
Crypto Manager properties depend on the Crypto Manager type, which depends on the null option.
--reset {property}
Resets a property back to its default values where PROP is the name of the property to be reset.
Crypto Manager properties depend on the Crypto Manager type, which depends on the null option.
--add {PROP:VALUE}
Adds a single value to a property where PROP is the name of the property and VALUE is the single value to be added.
Crypto Manager properties depend on the Crypto Manager type, which depends on the null option.
--remove {PROP:VALUE}
Removes a single value from a property where PROP is the name of the property and VALUE is the single value to be removed.
Crypto Manager properties depend on the Crypto Manager type, which depends on the null option.
Crypto Managers of type crypto-manager have the following properties:
Specifies the key length in bits for the preferred cipher.
128
An integer value. Lower value is 0.
No
No
None
Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
Yes (Use --advanced in interactive mode.)
No
Specifies the cipher for the directory server using the syntax algorithm/mode/padding. The full transformation is required: specifying only an algorithm and allowing the cipher provider to supply the default mode and padding is not supported, because there is no guarantee these default values are the same among different implementations. Some cipher algorithms, including RC4 and ARCFOUR, do not have a mode or padding, and hence must be specified using NONE for the mode field and NoPadding for the padding field. For example, RC4/NONE/NoPadding.
AES/CBC/PKCS5Padding
A String
No
No
None
Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
Yes (Use --advanced in interactive mode.)
No
Specifies the preferred message digest algorithm for the directory server.
SHA-256
A String
No
No
None
Changes to this property take effect immediately and only affect cryptographic operations performed after the change.
Yes (Use --advanced in interactive mode.)
No
The preferred key wrapping transformation for the directory server. This value must be the same for all server instances in a replication topology.
RSA/ECB/OAEPWITHSHA-1ANDMGF1PADDING
A String
No
No
None
Changes to this property will take effect immediately but will only affect cryptographic operations performed after the change.
No
No
Specifies the preferred MAC algorithm for the directory server.
HmacSHA256
A String
No
No
None
Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
Yes (Use --advanced in interactive mode.)
No
Specifies the key length in bits for the preferred MAC algorithm.
128
An integer value. Lower value is 0.
No
No
None
Changes to this property take effect immediately but only affect cryptographic operations performed after the change.
Yes (Use --advanced in interactive mode.)
No
Specifies the nicknames (also called the aliases) of the keys or key pairs that the Crypto Manager should use when performing SSL communication. The property can be used multiple times (referencing different nicknames) when server certificates with different public key algorithms are used in parallel (for example, RSA, DSA, and ECC-based algorithms). When a nickname refers to an asymmetric (public/private) key pair, the nickname for the public key certificate and associated private key entry must match exactly. A single nickname is used to retrieve both the public key and the private key. This is only applicable when the Crypto Manager is configured to use SSL.
Let the server decide.
A String
Yes
No
The Crypto Manager must be disabled and re-enabled for changes to this setting to take effect
No
No
Specifies the names of the SSL cipher suites that are allowed for use in SSL or TLS communication.
Uses the default set of SSL cipher suites provided by the server's JVM.
A String
Yes
No
None
Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
No
No
Specifies whether SSL/TLS is used to provide encrypted communication between two OpenDJ server components.
false
true
false
No
No
None
Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
No
No
Specifies the names of the SSL protocols that are allowed for use in SSL or TLS communication.
Uses the default set of SSL protocols provided by the server's JVM.
A String
Yes
No
None
Changes to this property take effect immediately but only impact new SSL/TLS-based sessions created after the change.
No
No