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

Detect modern TLS listeners in the management plugin #6

Open
michaelklishin opened this issue Feb 15, 2019 · 0 comments
Open

Detect modern TLS listeners in the management plugin #6

michaelklishin opened this issue Feb 15, 2019 · 0 comments

Comments

@michaelklishin
Copy link
Member

michaelklishin commented Feb 15, 2019

As of rabbitmq/rabbitmq-management#618 there is one more way of configuring listeners, in particular for TLS. This plugin hasn't been updated to support them,
so a node that uses e.g. the following configuration

management.ssl.port       = 15671
management.ssl.cacertfile = /path/to/ca_certificate.pem
management.ssl.certfile   = /path/to/server_certificate.pem
management.ssl.keyfile    = /path/to/server_key.pem

would incorrectly assume that it should use HTTP and not HTTPS for URI schema because the application environment key structure would be different from before rabbitmq/rabbitmq-management#618 days.

[168224342]

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

1 participant