How to define broker's security settings separately from the ActiveMQArtemis CR's implementation

Solution Verified - Updated -

Issue

  • The way to define security settings on the queues is defined as follows, on the ActiveMQArtemis custom resource implementation:
spec:
  ...
  brokerProperties:
  - securityRoles.#.group2.send=true
  - securityRoles.#.group1.consume=true
  - securityRoles.#.group1.createAddress=true
  - securityRoles.#.group1.createNonDurableQueue=true
  - securityRoles.#.group1.browse=true
  ...

as stated in the official documentation here

But this way of defining the addresses' security is hard to maintain, especially when there are defined a lot of addresses for the broker

Environment

  • OCP 4.x
  • AMQ Broker operator 7.11.x
  • AMQ 7.11.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content