com.ibm.websphere.wim.exception.WIMSystemException: CWWIM4520E The ‘javax.naming.AuthenticationException: [LDAP: error code 49 – 80090308: LdapErr: DSID-0C090417, comment: AcceptSecurityContext error, data 52e, v1db1\u0000]; resolved object com.sun.jndi.ldap.LdapCtx@34982018’ naming exception occurred during processing.
To reset the password , it depends on which registry in use. If user exists in LDAP then you need to reset from LDAP side.
If user is in file registry then you should follow the below steps.
stop dmgr (kill java process if stop failed)
dmgr/bin/wsadmin.sh -conntype NONE -lang jacl
$AdminTask changeFileRegistryAccountPassword {-userId your_userID -password new_password}
$AdminConfig save
Then Start DMGR and try to login to console.
If still having issue then please run collector tool and send us the jar file.
To run the collector tool, please take these steps:
1. Open a terminal window and change your working directory to any temp location that is not located under the WebSphere install directory tree. ie.
# cd /tmp
2. Run the profile specific collector script by specifying the full file path spec to the collector.sh script.
e.g.
#DMGRProfile_name\bin\collector.sh|bat
3. The collector script will create the jar file in your current directory location.
1: Disable security
How do I disable security in WAS when I cannot access the administrative console?
How do I manually disable WAS security if I am locked out of the IBM Integrated Solutions Console?
2: Then Kill DMGR Process and start the DMGR. Login to console.
3: Verify that LDAP test connection successful and also mention the Bind user ID.
4:Then Use LDAP Test Query Option to find the User wssysad. This is to cross verify if wssysad exists in LDAP or not.
5:Also Go to Global Security. Then under User Account repository click on Configure . Then Select the option Allow operations if some of the repositories are down .
6: Enable Core Security trace by following the below link
https://www.ibm.com/support/pages/node/708633
Then Enable security and restart DMGR . Then try to login.