Setting up the Key and Trust Stores
Also see Tomcat's SSL instructions for more info. The following was provided by Colin Kilburn. Thanks Colin!
ActiveMQ uses dummy credentials by default
ActiveMQ includes key and trust stores that reference a dummy self signed cert. When you create a broker certificate and stores for your installation, either overwrite the values in the conf directory or delete the existing dummy key and trust stores so they cannot interfere)
Starting the Broker
Using the javax.net.ssl.* System Properties
Before starting the broker's VM set the ACTIVEMQ_SSL_OPTS environment variable so that it knows to use the broker keystore. (note that in previous versions of ActiveMQ this property was called SSL_OPTS in some scripts. As of v5.12.0 all scripts use ACTIVEMQ_SSL_OPTS)
Using Spring to configure SSL for a Broker instance
Sometimes the use of javax.net.ssl.* system properties is not appropriate as they effect all SSL users in a JVM. ActiveMQ 5.2.x adds an <sslContext> element to the <amq:broker> that allows a broker specific set of SSL properties to be configured.
The SslContext test case validates starting an SSL transport listener using the configuration specified in the broker Xbean. The SslContext element is added to the broker as follows:
The SslContext is used to configure the SslTransportFactory for that broker. Full details of the configuration options available can be seen in the schema definition or in the accessors of org.apache.activemq.spring.SpringSslContext
Starting the Client
When starting the client's VM, specify the following system properties:
In Linux, do not use absolute path to keystore. By default, keytool uses ~/.keystore, but in some setups passing -Djavax.net.ssl.keyStore=/home/account/.keystore to Java VM does not work. This is not ActiveMQ specific but good to keep in mind anyway.
If you want to verify client certificates, you need to take a few extra steps:
Starting with version 5.12, you can define certificate revocation list (CRL) path on ssl context, so that invalid certificates can revoked
This list is static and loaded on broker startup.
Starting with version 5.14.0, you can also enable more advanced Online Certificate Status Protocol (OCSP) protocol. For that you need to configure a location for the
Then you need to configure OCSP responder properties in
A demo of the broker configuration working with OCSP responder can be found at https://github.com/dejanb/sslib
Working Around Java 7 SSL Bugs
As noted by issue AMQ-5970, it seems some versions of Java 7 have problems with SSL sessions that need to use the Diffie-Hellman cypher suite. If you run into this issue, just copy the Bouncy Castle bcprov-jdk15on-148.jar to ActiveMQ's lib directory and restart your broker.
These links might also help