-
Bug
-
Resolution: Done
-
Major
-
AMQ 7.3.0.GA, AMQ 7.4.0.CR2
-
None
-
2
-
AMQ Broker 2919, ignore
At the moment the way that the user and cluster user credentials are configured is to pass them to the artemis create command which gets logged in full as per this example:
Configuring Broker
Broker will be clustered
Creating Broker with args --silent --role admin --name amq-broker --http-host example-activemqartemis-ss-1 --java-options=-Djava.net.preferIPv4Stack=true --user admin --password admin --allow-anonymous --data /opt/example-activemqartemis/data --no-autotune --clustered --cluster-user=clusterpoduser --cluster-password=clusterpodpassword --host example-activemqartemis-ss-1
Here we can see the --password XXXXX and --cluster-password YYYYY passed in the clear.
- duplicates
-
ENTMQBR-2183 Hide password from default amq image logs when pod is created
- Closed
- is related to
-
ENTMQBR-2629 Ensure sensitive credentials are stored in kubernetes secrets
- Closed
-
ENTMQBR-2830 Documentation: Ensure sensitive credentials are stored in kubernetes secrets
- Closed