AMQ console exposed even-though set useClientAuth: true

Solution Unverified - Updated -

Issue

  • We are deploying AMQ on OpenShift using the AMQ operator. We would like to secure access to the management console and disallow guest access. So in the deployment, we set:
  console:
    expose: true
    useClientAuth: true
    sslEnabled: false

However the resulting login.config is as follows:
activemq


{ org.apache.activemq.artemis.spi.core.security.jaas.PropertiesLoginModule sufficient debug=false reload=true org.apache.activemq.jaas.properties.user="artemis-users.properties" org.apache.activemq.jaas.properties.role="artemis-roles.properties"; org.apache.activemq.artemis.spi.core.security.jaas.GuestLoginModule sufficient debug=false org.apache.activemq.jaas.guest.user="amq" org.apache.activemq.jaas.guest.role="admin";

And anyone can access the console without a password. This is not the way we want it. We also can't set the AMQ_REQUIRE_LOGIN to true in the Stateful Set, since the operator sets it back to false

Environment

  • Red Hat AMQ
    • 7.8

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