3.6. Disabling Broker Security

download PDF


Prior to Fuse MQ Enterprise version 7.0.2, the Apache ActiveMQ broker was insecure (JAAS authentication not enabled). This section explains how to revert the Apache ActiveMQ broker to an insecure mode of operation, so that it is unnecessary to provide credentials when connecting to the broker.
After performing the steps outlined in this section, the broker has no protection against hostile clients. This type of configuration is suitable only for use on internal, trusted networks.

Standalone server

These instructions assume that you are running Red Hat AMQ in standalone mode (that is, running in an OSGi container, but not using Fuse Fabric). In your installation of Red Hat AMQ, open the InstallDir/etc/activemq.xml file using a text editor and look for the following lines:
 <jaasAuthenticationPlugin configuration="karaf" />
To disable JAAS authentication, delete (or comment out) the jaasAuthenticationPlugin element. The next time you start up the AMQ container using the start script the broker will run with unsecured ports.
Red Hat logoGithubRedditYoutubeTwitter


Try, buy, & sell


About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.