nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Enable Customer signed certificates for Rabbitt MQ inbound communication port from APE's to the Primary polling engine

spodil91

Rabbitt MQ service using Solarwinds issued self-signed certificate applied to the secure comminucation port 5671 (RabbitMQ inbound communication port from APE's to the Primary polling engine). But, customer want to enable they own signed certificate which is not possible in Solarwinds. We have worked with Solarwinds vendor on this issue(case # -00133855).

Solarwinds have advised that the product does not support using a customer issued certificate . This is being raised as a feature request, to be considered for future releases.

Thanks,

Sateesh Podili

Find more posts tagged with

Status: None

Comments

dwclark5

Need to change the self-signed cert to DOD Certificate due to vulnerabilities being found

charlesjsmith

Were you able to change out the certificate for rabbitmq? I'm having similar problem.