502->601 Tomcat->WAS LDAP issues.
![]()
All,
I did a successful upgrade in the test environment, which included the migration of tomcat->WAS Liberty. After the migration, I need to finish the last few steps, but I cannot login. It seems that there may be an issue with the "copied" bindPassword, as it's failing authentication. (so, before it even tried to look up the user that logged in, it fails to bind to ldap with the "bind" user)
I know the password of the "binding" user and it works. I can't reset everything, because production is using it. What are my next steps to resolve the ldapUserRegistry.xml file? I there a way to produce another "generated" password to copy and paste in here?
If not how do I "reset" so I can login and connect to LDAP without "corrupting" the 601 upgrade?
thanks
|
Accepted answer
2 other answers
![]()
I only have a vague recollection of running into this myself....
I remember fiddling about with this: <JazzInstallRoot>/server/liberty/wlp/bin/securityUtility If you type ./securityUtility help encode it should help you. I think that this is how I got it working. I then ran into trouble with the Filters which are dependant on which ldap implementation you are using ... HTH, Robin |