1.1.1

Table Of Contents
Default ValueCommentArgument
communication outside of the SQLFire
distributed system.
any
Space-separated list of the valid SSL
protocols for this connection. You can specify
agent-ssl-protocols
any protocol that is enabled by default in the
congured Java Secure Sockets Extension
(JSSE) provider.
any
Space-separated list of the valid SSL ciphers
for this connection. You can specify any
agent-ssl-ciphers
ciphers that are enabled by default in the
congured JSSE provider.
trueIf true, require client authentication for
RMI and other non-HTTP
connectors/adaptors.
agent-ssl-require-authentication
falseIf true, require client authentication for
HTTP adaptors.
http-ssl-require-authentication
In addition to conguring these properties, you must generate a keystore with the JMX Agent's certicate, and
export the Agent's certicate into all client keystores that will need to access the Agent for monitoring. The
example that follows how to generate and use these keystores using the Java keytool utility.
Note: You can also congure a SQLFire system to use SSL protocol for communication between system
members. See Conguring Authentication and Authorization on page 241 for details.
Example of Configuring SSL for JMX Agents
Follow these steps to congure and start the JMX Agent with SSL enabled:
1. Congure the agent properties listed described in the preceding table.
2. Generate a keystore for the JMX Agent. This example store uses the alias "jmxagent" and creates a new
keystore named admin.keystore:
$ keytool -genkey -alias jmxagent -dname "CN=trusted" -validity 3650
-keypass password -keystore admin.keystore -storepass password -storetype
JKS
3. Verify the new keystore le:
$ keytool -list -keystore admin.keystore
Enter keystore password: password
Keystore type: JKS
Keystore provider: SUN
Your keystore contains 1 entry
jmxagent, Mar 15, 2013, PrivateKeyEntry,
Certificate fingerprint (MD5):
83:71:0D:E4:53:AF:5C:31:E4:43:3D:01:C7:2C:BC:05
vFabric SQLFire User's Guide306
Managing and Monitoring vFabric SQLFire