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.

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

[Improvement]: Steps for enabling SSL when configuring Rabbitmq can be more precise #389

Closed
ShammiL opened this issue Jul 8, 2024 · 0 comments

Comments

@ShammiL
Copy link
Contributor

ShammiL commented Jul 8, 2024

Description

The documentation for configuring RabbitMQ has a section explaining how to enable SSL. It instructs to check the fail_if_no_peer_cert config in RabbitMQ before adding the configs to enable SSL. But this explanation can be a little confusing to a beginner in RabbitMQ. Mentioning that fail_if_no_peer_cert can be found inside the rabbitmq.conf file in the OS specific location can make it more understandable.

Also having the above explanation as a Tip and having the relevant config values to add separately can also be a little confusing.

Describe the problem(s)

A detailed description of the purpose of this improvement.

Describe your solution(s)

A detailed description of how this improvement will solve the problem described above.

Related issue(s) (optional)

Any related issues such as sub tasks and issues reported in other repositories (e.g., component repositories), similar problems, etc.

Suggested label(s) (optional)

Optional comma-separated list of suggested labels. Non committers can’t assign labels to issues, and thereby, this will help issue creators who are not a committer to suggest possible labels.

Suggested assignee(s) (optional)

Optional comma-separated list of suggested team members who should attend the issue. Non committers can’t assign issues to assignees, and thereby, this will help issue creators who are not a committer to suggest possible assignees.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants