IBM Security RabbitMQ Support

This topic only applies to Verify Privilege Vault On-Premises.
This topic is the customer-facing version of IBM Security Support knowledge base article RabbitMQ Support (KB 1764686073610). The KB remains the canonical reference for IBM Security Support agents; this topic mirrors it for customers who need to understand the support boundary before opening a case.

RabbitMQ is an asynchronous messaging system that is used as a foundational technology for Verify Privilege Vault On-Premises and is used with the Distributed Engine component. It is the recommended messaging system that functions as a queue of work for Distributed Engine to receive and publish messages to and from, but RabbitMQ is a 3rd-party product and is not owned, operated, or managed by IBM Security.

The purpose of this topic is to clarify how IBM Security supports RabbitMQ.

IBM Security Technical Support Responsibilities

  • Assist customers by supplying general information about RabbitMQ.

  • Help deploy RabbitMQ as a single node.

  • Supply links to publicly available RabbitMQ documentation.

Customer Responsibilities

  • Customers are responsible for creating, deploying, and troubleshooting certificates or certificate errors with RabbitMQ.

  • As each customer environment is unique and can include products from many different vendors, customers are responsible for troubleshooting and solving network or 3rd-party product issues in their environments.

  • Upgrade RabbitMQ or apply any hotfixes, patches, or security updates for RabbitMQ.

  • Customers are responsible for clustering or re-clustering RabbitMQ if a cluster has failed. If necessary, IBM Security Technical Support can provide links to non-IBM Security resources which describe how to cluster or re-cluster RabbitMQ.

  • Determine root causes for RabbitMQ issues that do not include a Verify Privilege Vault component.

In all cases IBM Security Technical Support will act to ensure Verify Privilege Vault is functional, but this may not always result in the same architecture if RabbitMQ clusters are not fully operational.

IBM Security Technical Support will assist customers who use RabbitMQ in a clustered configuration to determine whether a defect exists in the software. If there is a defect in a IBM Security application which only appears when RabbitMQ is in a cluster or only occurs when a customer has RabbitMQ with SSL, then it will be addressed and fixed according to its severity, since the product does support (is compatible with) clustering and RabbitMQ with SSL.

If a customer reports an issue to IBM Security Technical Support and it is found to be an issue with a customer's RabbitMQ, either the customer can remediate the cluster issue or IBM Security Technical Support can restore functionality by changing Verify Privilege Vault to point to an individual node.

For Clustered Environments

IBM Security will not reconfigure RabbitMQ clustering, since this is part of hosting and maintaining a RabbitMQ on-premises environment.

RabbitMQ Federation is not supported by Verify Privilege Vault or IBM Security. RabbitMQ Federation is incompatible with any functionality which requires quick responses in order for logins and the UI to work correctly (blocking calls), and as such we do not support it at the current time. While it is possible for the application to function with Federation enabled, time-sensitive operations will be unreliable and may time out.