Maximo Open Forum

 View Only

 CWWIM4513E The password match failed for the 'wasadmin' principal name

  • Everything Maximo
Amar Msaid's profile image
Amar Msaid posted 08-10-2023 07:52

Hi everyone,

i have cloned our staging maximo environment and followed a procedure to make all the changes and actions needed in the cloned environment (all the reference to the original environment have been changed). When i restarted the cloned VM, all things seem correct and the DMGR, Application server and maximo application are running. I am able to connect to the Websphere administration console with the user maxadmin, but the maximo login page is not displayed.

Notice: The original and the cloned environment don't use LDAP for the autentification but use maxuser maximo table to authenticate the users. 

Here message that i see in the application server log :

[23-08-09 17:14:48:848 EDT] 0000006c LTPAServerObj E   SECJ0369E: L'authentification a échoué lors de l'utilisation de LTPA. L'exception est com.ibm.websphere.wim.exception.PasswordCheckFailedException: CWWIM4513E  Echec de correspondance du mot de passe pour le nom de principal 'wasadmin'..

[23-08-09 17:14:48:903 EDT] 0000006c SystemOut     O 09 août 2023 17:14:48:889 [INFO ] [maximo] BMXAA6709I - Impression de StackTrace : CWWIM4513E  Echec de correspondance du mot de passe pour le nom de principal 'wasadmin'.

com.ibm.websphere.security.auth.WSLoginFailedException: CWWIM4513E  Echec de correspondance du mot de passe pour le nom de principal 'wasadmin'.

          at com.ibm.ws.security.ltpa.LTPAServerObject.authenticate(LTPAServerObject.java:1024) ~[com.ibm.ws.runtime.jar:?]

          at com.ibm.ws.security.server.lm.ltpaLoginModule.login(ltpaLoginModule.java:661) ~[com.ibm.ws.runtime.jar:?]

          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0]

          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90) ~[?:1.8.0]

          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) ~[?:1.8.0]

          at java.lang.reflect.Method.invoke(Method.java:508) ~[?:1.8.0]

          at javax.security.auth.login.LoginContext.invoke(LoginContext.java:788) ~[?:1.8.0]

          at javax.security.auth.login.LoginContext.access$000(LoginContext.java:196) ~[?:1.8.0]

          at javax.security.auth.login.LoginContext$4.run(LoginContext.java:698) ~[?:1.8.0]

          at javax.security.auth.login.LoginContext$4.run(LoginContext.java:696) ~[?:1.8.0]

          at java.security.AccessController.doPrivileged(AccessController.java:738) ~[?:1.8.0]

 

 

 

 

mark robbins's profile image
mark robbins

I would look at earlier entries in the logs for additional clues as to what is happening.

This is likely to be a symptom of a bigger problem and that should be listed in the earlier log entries