Unlocking AMQ Permissions in Openshift for Non-Admin Users

AMQ Permissions: The Problem

This scenario may sound very familiar to you. You successfully install the AMQ Broker in your development environment, configure the queues, and develop components that publish/subscribe messages in the broker. Everything works flawlessly according to your plan until you encounter a major challenge: attempting to replicate the setup in a non-development environment such as production. But now, at this point, you encounter your first roadblock – you lack the privileges to install the broker.

For security reasons, it is typically entrusted to someone with administrative rights instead of yourself, which is understandable. However, the real problem arises when you realize that you are unable to create addresses or queues without depending on the administrator for each task. Relying on the administrator can become a significant bottleneck. While one possible solution is to become an administrator yourself, it is often not a viable option. Alternatively, a better approach would be to obtain the necessary permissions to manage the AMQ broker independently. In this blog entry, I will explain precisely how to achieve this.