The self-signed certificates delivered with your MySQL Enterprise Monitor installation are set to expire after 365 days. Every upgrade is delivered with new certificates set to expire 365 days after the day the upgrade package was built. In the unlikely event you are running a version of MySQL Enterprise Service Manager using the default certificates for more than a year, you must generate new certificates. If you do not generate new certificates, the SSL connection between MySQL Enterprise Service Manager and the repository fails. This section describes how to generate those certificates.
These instructions guide you through the process of installing SSL
certificates for your MySQL Enterprise Monitor installation. The
$INSTALL_ROOT represents the root path of your
installation, which defaults to:
Table 6.1 Default Root Path (
|Operating System||Default Path|
|Linux / Solaris||
|Mac OS X||
To use SSL, you must generate a certificate and private key.
These can be verified and signed through a third-party
authority, such as Thawte or Entrust, or generated locally and
self-signed. The recommended tool for locally-generated SSL key
and certificates is the OpenSSL Toolkit. The OpenSSL libraries
are delivered by default with UNIX, Linux and Mac OS X
platforms, but must be obtained separately for Microsoft Windows
The Windows installation also requires the
2008 Redistributables libraries.
For security reasons, we recommend you install the latest, compatible version of the OpenSSL Toolkit.
If you intend to use a Certificate Authority to verify your organisation's identity and sign your certificate, you must generate a private key, which is used to create a Certificate Signing Request (CSR), and send the CSR file to the Certificate Authority.
To generate the RSA private key, run the following command:
openssl genrsa -out insertName.key 2048
This generates a 2048-bit, RSA private key.
To generate the Certificate Signing Request (CSR), run the following command:
openssl req -new -nodes -key insertName.key -out insertName.csr
This command prompts for input. Complete the fields as required.
CN field must correspond to the
hostname. It is recommended that you use the fully-qualified
server name, rather than
If you intend to use a self-signed certificate, you can generate the key and certificate with a single command:
openssl req -x509 -newkey rsa:2048 -keyout key.pem -out cert.pem -days 365
This command generates a 2048-bit RSA key,
key.pem, and a certificate,
cert.pem, which is valid for 365 days.
To install an SSL certificate for the MySQL Enterprise Service Manager:
Save the certificate and private key, both in PEM format, in the following location:
If you are using a chained certificate implementation, you must
add the following attribute to the
element of Tomcat's
For information on SSL and MySQL Server, see Creating SSL and RSA Certificates and Keys.
To configure SSL-related options for the Agent, the following
values may be placed in
Table 6.2 SSL Configuration Options For The Agent's
||Verify that the hostname of the service manager that the Agent is connected to matches what is in the SSL certificate, Default is false, as we are only using SSL for confidentiality|
||If set to
||Default false, but to support self-signed certificates, a commercial certificate, or if the CA certificate has been imported into a keystore, then set to true||3.0.20|
||String||Path to keystore with CA cert(s), if
||String||Password for the CA keystore, if
ssl-verify-hostname=false ssl-verify-host-certs=true ssl-ca-keystore-path=/path/to/keystore ssl-ca-keystore-password=password123
To import a CA certificate in PEM format to a new keystore on the Agent, execute the following:
$INSTALL_ROOT/java/bin/keytool -import -file /path/to/ca/ca.pem -alias CA_ALIAS -keystore $INSTALL_ROOT/etc/cacerts
The tool responds with the certificate details. For example:
Enter keystore password: (the keystore will require at least a 6 character password) Re-enter new password: Owner: CN=serverName.com, O=MySQL AB, ST=Uppsala, C=SE Issuer: O=MySQL AB, L=Uppsala, ST=Uppsala, C=SE Serial number: 100002 Valid from: Fri Jan 29 12:56:49 CET 2010 until: Wed Jan 28 12:56:49 CET 2015 Certificate fingerprints: MD5: E5:FB:56:76:78:B1:0C:D7:B0:80:9F:65:06:3E:48:3E SHA1: 87:59:80:28:CE:15:EF:7E:F1:75:4B:76:77:5E:64:EA:B7:1D:D1:18 SHA256: F4:0B:79:52:CF:F3:A1:A4:7F:B2:D7:C1:65:60:F0:80:93:87:D2:68:9A:A1: 84:F4:06:6E:8E:CF:C1:F6:1B:52 Signature algorithm name: MD5withRSA Version: 1 Trust this certificate? [no]: (type yes + enter) Certificate was added to keystore
You must edit the
to use the path to the keystore and password.
SSL configuration for LDAP is configured at the MySQL Enterprise Service Manager Java VM level. That is, it is configured in the keystore of the Java VM bundled with your MySQL Enterprise Monitor installation.
The JVM shipped with MySQL Enterprise Service Manager does not support the AES256 cipher. This can prevent you using LDAP servers which implement that cipher.
To connect to LDAP servers which implement the AES256 cipher, you must download and install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 8 package. This package is available from: Java Cryptography Extension.
The steps described in this section assume your LDAP server is correctly configured and you have a root CA certificate which was used to generate the LDAP server's certificate.
To enable SSL for LDAP and MySQL Enterprise Service Manager, you must do the following:
Convert the LDAP server's root CA certificate from PEM to DER format, if necessary. If the CA certificate is already in DER format, continue to the next step.
openssl x509 -in cacert.pem -inform PEM -out ~/cacert.der -outform DER
Import the CA certificate, in DER format, into the MySQL Enterprise Service Manager Java keystore. Run the following command from the
bindirectory of your MySQL Enterprise Service Manager's Java installation:
keytool -import -trustcacerts -alias ldapssl -file ~/cacert.der -keystore lib/security/cacerts
Restart MySQL Enterprise Service Manager with the following command: