Closed huber-and closed 1 year ago
How did you test? As described in Readme and also values.yaml the authentication.user & authentication.password are only for the initial admin user. If you change that in the Rabbit management UI the values are ignored on further upgrade deployments.
This is how I tested it
# Ingress
...
...
# Default user and erlang cookie
authentication:
## Initial user name
user: "iamadmin"
## Initial password
password: "secret"
## Erlang cookie (MANDATORY)
erlangCookie: "VGhpc0lzTXlFcmxhbmdDb29raWUK"
## Management UI plugin options
managementPlugin:
## Enable management UI plugin with default configuration
enabled: true
## Storage parameters
storage:
requestedSize: 256Mi
Afterwards you can login with "iamadmin"/"secret".
You are right, i found the issue. When the password contains a # like "test#01" only "test" is used as password.
This is described in section "Override Default User Credentials" of https://www.rabbitmq.com/access-control.html.
Summarized: The overall behavior is correct. For the default user the setting inside rabbitmq.conf can't contain a "#" character because it is interpreted as comment in the config file. Also putting quotes around it will not help.
A user or password like test@1
will work of course.
This only affects the initial default user, which should be changed after initial deployment anyway.
Thanks!
It looks like the RabbitMQ chart does ignore the authentication settings. When set env.RABBITMQ_DEFAULT_USER and env.RABBITMQ_DEFAULT_PASS it works as expected.