RabbitMQ deployment with third-party certificate

[imGannicus]

Can rabbitmq be deployed on server with wildcard third-party certificate (e.g. godaddy) having name different from server name. Server name is like rabbitserver.qa.local and wild card certificate name is like *.qa.test.rabbit.com

[lukebakken]

Server name is like rabbitserver.qa.local and wild card certificate name is like *.qa.test.rabbit.com

No, that's not how wildcard certs work, in any case.

[imGannicus]

wildcard certificate works for websites/web services when we get DNS entry created like rabbitserver.qa.test.rabbit.com and bind to website/web service but its not working in case of rabbitmq

[lukebakken]

its not working in case of rabbitmq

That statement tells me absolutely nothing useful.

[imGannicus]

how can we make rabbitmq work with third-party cert?

[michaelklishin]

@imGannicus all certificates are "third party" ones for RabbitMQ. We will not troubleshoot TLS for non-paying users.

There are two extensive guides related to TLS:

• On how TLS is used with RabbitMQ
• On how to troubleshoot TLS-related issues, namely how to narrow them down efficiently
• An example tool that generates self-signed certificate chains which is used extensively by the RabbitMQ team for integration tests

The docs even mention some specific log messages for very common failure scenarios, and explains how TLS peer verification works.

The only thing I can add to the doc guides above: it might be that your certificate does not have the appropriate Subject Alternative Name fields. You haven't provided any details, so that's just a guess with an OpenSSL config example.

We will not guess as to what you are trying and what exactly does "its not working" mean. Such problem definitions in a domain as nuanced as TLS do nothing but waste everyone's time.