Chapter 5. Connecting to AMQ Management Console for an Operator-based broker deployment

Procedure

1. In the OpenShift Container Platform web console, click Networking Routes.

   On the Routes page, identify the wconsj Route for the given broker Pod. For example, my-broker-deployment-wconsj-0-svc-rte.

2. Under Location, click the link that corresponds to the Route.

   A new tab opens in your web browser.

3. Click the Management Console link.

   The AMQ Management Console login page opens.

4. To log in to the console, enter the values specified for the adminUser and adminPassword properties in the Custom Resource (CR) instance used to create your broker deployment.

   If there are no values explicitly specified for adminUser and adminPassword in the CR, follow the instructions in Section 5.2, “Accessing AMQ Management Console login credentials” to retrieve the credentials required to log in to the console.

   Note

   Values for adminUser and adminPassword are required to log in to the console only if the requireLogin property of the CR is set to true. This property specifies whether login credentials are required to log in to the broker and the console. If requireLogin is set to false, you can log in to the console without supplying a valid username password by entering any text when prompted for username and password.

Procedure

1. See the complete list of secrets in your OpenShift project.

   1. From the OpenShift Container Platform web console, click Workload Secrets.

   2. From the command line:

      $ oc get secrets

2. Open the appropriate secret to reveal the Base64-encoded console login credentials.

   1. From the OpenShift Container Platform web console, click the secret that includes your broker Custom Resource instance in its name. Click the YAML tab.

   2. From the command line:

      $ oc edit secret <my-broker-deployment-credentials-secret>

3. To decode a value in the secret, use a command such as the following:

   $ echo 'dXNlcl9uYW1l' | base64 --decode
   console_admin