We were unable login to the OAM console after changing the identity store used by the LDAP authenication scheme. In our case it was IdentityStore1 and got changed to ADStore. So we had to revert the values in oam-config.xml to login to the console again.
Weblogic server maintains multiple back ups of the file in the below location.
We found there was a backup file existing before the change happened. So by restoring the file and restarting the servers we were able to login to the console.
If you cannot find the any backup of the file in the folder just edit the oam-config.xml and setting the correct ldap id. For example,
Weblogic server maintains multiple back ups of the file in the below location.
DOMAIN_HOME/config/fmwconfig/oam-config.xml
We found there was a backup file existing before the change happened. So by restoring the file and restarting the servers we were able to login to the console.
If you cannot find the any backup of the file in the folder just edit the oam-config.xml and setting the correct ldap id. For example,
<Setting Name="ldapid" Type="xsd:string">UserIdentityStore</Setting>
