Page Comparison

The EI Message Broker runtime provides support to send/receive messages via secured connections using the SSL/TLS protocol. The following instructions describe how to configure the broker server and JMS clients to communicate via encrypted connections using SSL.

Table of Contents

maxLevel	3
minLevel	3

Enabling SSL in the broker

To enable SSL inthe server side, change the following entries in the <EI_HOME>/wso2/broker/conf/broker.xml file under the relevant transport:relevant transport (AMQP or MQTT). See Configuring Transports for WSO2 MB for more information on the available transports.

Code Block

<sslConnection enabled="true" port="8672">
    	<keyStore>
        	<location>repository/resources/security/wso2carbon.jks</location>
            <password>wso2carbon</password>
            <certType>SunX509</certType>
    	</keyStore>
        <trustStore>
            <location>repository/resources/security/client-truststore.jks</location>
            <password>wso2carbon</password>
            <certType>SunX509</certType>
        </trustStore>
</sslConnection>

The parameters in the above configuration are as follows.

Parameter Description

SSL Connection

This contains the basic configurations relating to the SSL connection. Setting the

enabled="true" attribute ensures that SSL is enabled by default when the broker is started. The

port="8672" attribute sets 8672 as the default SSL listener port for messages/command sent via the relevant transport.

Location

The location where the keystore used for securing SSL connections is stored. By default this is the default keystore(wso2carbon.jks) that is shipped with the broker.

Note
Note that this should always be a keystore created for the super tenant. Find out more about setting up keystores for your broker.

Password The password ofthe keystore.

Certification Type

The type of SSL certificate used for the keystore/truststore. SunX509 is the standard name of the algorithm used by the key managers. This value should be changed accordingly if the system is running on a different JVM. For example, IbmX509 for the IBM JVM.

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 connectionurl format shown below to pass the SSL parameters:

Code Block

String connectionURL = "amqp://<USERNAME>:<PASSWORD>@carbon/carbon?brokerlist='tcp://<IP>:<SSL_POR T>?ssl='true'&ssl_cert_alias='<CERTIFICATE_ALIAS_IN_TRUSTSTORE>'&trust_store=' <PATH_TO_TRUST_STORE>'&trust_store_password='<TRUSTSTORE_PASSWORD>'& key_store='<PATH_TO_KEY_STORE>'&key_store_password='<KEYSTORE_PASSWOR D>''";

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 the Integrator runtime of WSO2 EI as the JMS client. Shown below is an example connectionurl using the default keystores and trust stores in the Integrator:

Code Block

String connectionUrl = "amqp://admin:admin@carbon/carbon?brokerlist='tcp://localhost:8672?ssl='true'&ssl_cert_alias='RootCA'&trust_store='{ESB_HOME}/repository/resources/security/client-truststore.jks'&trust_store_password='wso2carbon'&key_store='{ESB_HOME}/repository/resources/security/wso2carbon.jks'&key_store_password='wso2carbon''";

...

Versions Compared

Old Version 3

New Version 4

Key

Enabling SSL in the broker

Configuring JMS Clients to use SSL