You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
You can do your own web configuration if required
Or
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.
(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 showIf 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.
The text was updated successfully, but these errors were encountered: