Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve enabling SSL section in configure with RabbitMQ page #1223

Merged
merged 2 commits into from
Jan 6, 2025
Merged

Improve enabling SSL section in configure with RabbitMQ page #1223

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
285a76e
Improve enabling SSL section in configure with RabbitMQ page
ShammiL Jan 3, 2025
f97bbad
Apply suggestions from code review
DinithiDiaz Jan 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 18 additions & 15 deletions en/docs/install-and-setup/setup/brokers/configure-with-rabbitmq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,11 +35,15 @@ sender_enable = true

Add the following parameters to enable SSL for the RabbitMQ listener.

!!! Tip
Note that keystore information is not required for an SSL connection if the <code>fail_if_no_peer_cert</code> parameter is set to 'false' in the RabbitMQ broker. You only need to enable SSL in the Micro Integrator (using the `parameter.ssl_enable` parameter shown below).

However, if the <code>fail_if_no_peer_cert</code> parameter is set to 'true' in RabbitMQ, the keystore configurations (given below) are also required for the Micro Integrator.
```toml
[[transport.rabbitmq.listener]]
parameter.ssl_enable = true
parameter.ssl_version = "SSL"
```

!!! Tip
Note that keystore information is not required for an SSL connection if the <code>fail_if_no_peer_cert</code> parameter is set to 'false' in the RabbitMQ broker. You only need to enable SSL in the Micro Integrator (using the `parameter.ssl_enable` parameter shown above). You can check the <code>fail_if_no_peer_cert</code> parameter in the <code>rabbitmq.conf</code> file in its <a target="_blank" href="https://www.rabbitmq.com/docs/configure#config-location">OS-specific location</a>.
DinithiDiaz marked this conversation as resolved.
Show resolved Hide resolved

Shown below is an example of the config file where `fail_if_no_peer_cert` is set to `false`:
DinithiDiaz marked this conversation as resolved.
Show resolved Hide resolved
```
ssl_options.cacertfile = /path/to/ca_certificate.pem
Expand All @@ -49,17 +53,16 @@ Add the following parameters to enable SSL for the RabbitMQ listener.
ssl_options.fail_if_no_peer_cert = false
```

```toml
[[transport.rabbitmq.listener]]
parameter.ssl_enable = true
parameter.ssl_version = "SSL"
parameter.keystore_location ="repository/resources/security/wso2carbon.jks"
parameter.keystore_type = "JKS"
parameter.keystore_password = "wso2carbon"
parameter.truststore_location ="repository/resources/security/client-truststore.jks"
parameter.truststore_type = "JKS"
parameter.truststore_password = "wso2carbon"
```
However, if the <code>fail_if_no_peer_cert</code> parameter is set to 'true' in RabbitMQ, the keystore configurations (given below) are also required for the Micro Integrator.
DinithiDiaz marked this conversation as resolved.
Show resolved Hide resolved

```
parameter.keystore_location ="repository/resources/security/wso2carbon.jks"
parameter.keystore_type = "JKS"
parameter.keystore_password = "wso2carbon"
parameter.truststore_location ="repository/resources/security/client-truststore.jks"
parameter.truststore_type = "JKS"
parameter.truststore_password = "wso2carbon"
```

## Configuring connection recovery

Expand Down