Configuring the embedded ActiveMQ broker to use a different JAAS security realm than the enclosing Karaf container is being ignored.

Solution Verified - Updated -


When trying to configure JBoss Fuse to use a different JAAS configuration realm for the embedded ActiveMQ broker than the Karaf container, this configured security realm is ignored. The broker continues to use the security realm of the Karaf container called 'karaf'.

E.g. configuring etc/activemq.xml to

  <!-- changing realm name from default 'karaf' to 'mq' -->
  <jaasAuthenticationPlugin configuration="mq" />

the embedded ActiveMQ broker will still use the default 'karaf' authentication realm.

Trying to access the broker from a JMS client results in

User name admin or password is invalid.

although the right security credentials were submitted.


  • JBoss Fuse 6.0
  • JBoss Fuse 6.1
  • JBoss A-MQ 6.0
  • JBoss A-MQ 6.1

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