Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't log into web console unless MQ_DEV=true #557

Open
sichapman opened this issue Apr 15, 2024 · 1 comment
Open

Can't log into web console unless MQ_DEV=true #557

sichapman opened this issue Apr 15, 2024 · 1 comment

Comments

@sichapman
Copy link

sichapman commented Apr 15, 2024

(As of 9.3.5.0-r2)

I don't want the default objects created as they clash with what we add ourselves so usually set MQ_DEV=false.

However with the latest image, trying to log in to the web console using the password I set in the environment variables gives a Login failed. Enter a valid user ID and password. error. The logs show

2024-04-15T08:21:32.363Z CWWKS3005E: A configuration exception has occurred. No UserRegistry implementation service is available.  Ensure that you have a user registry configured.

2024-04-15T08:21:32.385Z FFDC1015I: An FFDC Incident has been created: "com.ibm.ws.security.registry.RegistryException: CWWKS3005E: A configuration exception has occurred. No UserRegistry implementation service is available.  Ensure that you have a user registry configured. com.ibm.ws.security.authentication.jaas.modules.UsernameAndPasswordLoginModule 116" at ffdc_24.04.15_08.21.32.0.log

If I set MQ_DEV=true it works fine (the web console anyway), but it doesn't feel right that this should be necessary, and it didn't used to be.

@vgavinash
Copy link
Contributor

vgavinash commented Apr 22, 2024

@sichapman, please note that this dependency was deliberately introduced since the dev users (both app & admin) apply to both the qmgr and the web server, and so for entirity, both need configurations available in the default objects. The related check happens at line - https://github.com/ibm-messaging/mq-container/blob/master/cmd/runmqserver/main.go#L176

However I can suggest you a way out,

  1. You can do your own web configuration if required
    Or
  2. You can comment out the check for MQ_DEV in the above said line and re-build the container. This will let you login to MQ console using the admin user and MQ_APP_PASSWORD.

Tagging @arthurbarr for any further comments.

Thanks,
Avinash

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants