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.
Table of Contents | ||||
---|---|---|---|---|
|
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:
Code Block | ||
---|---|---|
| ||
<sslConnection enabled="true" port="8672"> <keyStore> <location>repository/resources/security/wso2carbon.jks</location> <password>wso2carbon</password> |
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
|
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 WSO2 MB. 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:
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 truststore contains multiple entries. Shown below is an example connection url using default keystores and trust stores in WSO2 carbon products:
...