WSO2 Message Broker provides support to send/receive messages via secured connections using the SSL/TLS protocol. The following instructions describe how to configure the MB server and JMS clients to communicate via encrypted connections using SSL.
Enabling SSL in the broker
To enable SSL in the server side, change the following entries in the
<MB_HOME>/repository/conf/broker.xml file under the relevant transport:
The parameters in the above configuration are as follows.
|SSL Connection||This contains the basic configurations relating to the SSL connection. Setting the|
The location where the keystore used for securing SSL connections is stored. By default this is the default keystore (
Note that this should always be a keystore created for the super tenant. Find out more about setting up keystores for your MB server.
|Password||The password of the keystore.|
Configuring JMS Clients to use SSL
SSL parameters are configured and sent to the broker as broker options in the
TCPConnectionURL defined by the client. You need to set the 'ssl=true' property in the url and specify the keystore and client trust store paths and passwords. Use the connection url format shown below to pass the SSL parameters:
Setting the 'ssl_cert_alias' property is not mandatory and can be used as an optional way to specify which certificate the broker should use if the trust store contains multiple entries.
Example: Consider that you have WSO2 Enterprise Service Bus (WSO2 ESB) as the JMS client. Shown below is an example connection url using the default keystores and trust stores in WSO2 ESB:
When you configure WSO2 ESB to communicate with the broker (WSO2 MB) using SSL, the SSL url should be configured in the
jndi.properties file for WSO2 ESB (stored in the
<ESB_HOME>/repository/conf directory). Go to this link for detailed instructions on how WSO2 ESB integrates with WSO2 MB.
Configuring JMS Clients for Failover with SSL
For example, if you have configured a WSO2 Message Broker cluster, you might need to configure failover. If those broker nodes have different certs in place, when configuring a failover connection url at the client side, you can individually specify a client trust store and a keystore for each broker in the broker list. Or else, you can import the certs of all brokers in the cluster to a single trust store with different cert aliases and differentiate the cert to use when failing over by the alias.