operator pod not authenticating correctly when processing address CR

In prior releases, if you used the AMQ Broker Operator to create a broker Pod that required login (that is, by setting `requireLogin` to `true` in the Custom Resource (CR) used for the deployment), any addresses you tried to create on the broker via a CR were not created. This issue is now resolved.

1. modify basic example deployment to requireLogin $ cat deploy/examples/artemis-basic-deployment.yaml apiVersion: broker.amq.io/v2alpha1 kind: ActiveMQArtemis metadata: name: ex-aao spec: deploymentPlan: size: 1 image: registry.redhat.io/amq7/amq-broker:7.5 requireLogin: true 2. create deployment $ oc create -f deploy/examples/artemis-basic-deployment.yaml 3. obtain auto generated credentials $ echo -n "User: " ; oc get secret/ex-aao-credentials-secret -o template --template '{{.data.AMQ_USER}}' | base64 -d ; echo "" $ echo -n "Password: " ; oc get secret/ex-aao-credentials-secret -o template --template '{{.data.AMQ_PASSWORD}}' | base64 -d ; echo "" 4. log in to web console using credentials 5. create address $ oc create -f deploy/crs/broker_v2alpha1_activemqartemisaddress_cr.yaml activemqartemisaddress.broker.amq.io/ex-aaoaddress created 6. Note that the address is not actually created (verify in the web console), logs indicate: WARN [io.hawt.system.Authenticator] Login failed due to: User does not exist: admin