Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-8119

Corrections in documentation "Configuring JAAS login modules in a secret"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • AMQ 7.11.0.OPR.3.GA
    • security
    • None
    • Important

      I noticed there is an error and one omission in the following documentation:

      https://access.redhat.com/documentation/en-us/red_hat_amq_broker/7.11/html/deploying_amq_broker_on_openshift/assembly-br-configuring-operator-based-deployments_broker-ocp#proc-br-configuring-jaas-login-modules-for-authentication_broker-ocp

       

      Error:

      The login.config given in the example, has a syntax error. The file contents should be:

      activemq {
          org.apache.activemq.artemis.spi.core.security.jaas.PropertiesLoginModule sufficient
              reload=false
              org.apache.activemq.jaas.properties.user="artemis-users.properties"
              org.apache.activemq.jaas.properties.role="artemis-roles.properties"
              baseDir="/home/jboss/amq-broker/etc";    
      
          org.apache.activemq.artemis.spi.core.security.jaas.PropertiesLoginModule sufficient
              reload=true
              org.apache.activemq.jaas.properties.user="new-users.properties"
              org.apache.activemq.jaas.properties.role="new-roles.properties";
      }; 

      Omission:

      The status of the CR may appear in OutOfSync, until the new file is loaded into memory. This happens when you try loggin on the AMQ Management Console after the changes. For the examples presented, you could login with user: "ruben", password: "ruben01!", for the changes to be loaded.   

       

       

            jcliffor@redhat.com John Clifford
            rhn-support-anarvaez Alfredo Narvaez
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: