01-28-2014 02:28 PM
I am running into an issue where the LDAP integration seems to be not working properly.
I have deployed the proper war files into the Tomcat directories.
I deleted the el-api.jar file from the web services.
The adblog message I see when trying to log in is:
2014/01/28 14:18:44.761 0 256 [Thrd#:1548]Error loggued 331989648 - -52 Unable to load LDAP-specific dynamic library ('old
2014/01/28 14:18:44.761 0 1 [Thrd#:1548](-52) Unable to load LDAP-specific dynamic library ('oldap.dll').
2014/01/28 14:18:44.761 0 256 [Thrd#:1548]Error loggued 331989648 - -52 Unable to load LDAP-specific dynamic library ('nsl
2014/01/28 14:18:44.761 0 1 [Thrd#:1548](-52) Unable to load LDAP-specific dynamic library ('nsldap32v50.dll').
Logging in as the Admin works perfectly fine.
Users are able to log into AM with their LDAP credentials fine when using the Windows client.
Any advice is appreciated.
01-28-2014 06:04 PM
I have configured LDAP for AM 9.30 and 9.32 and have never run into those error messages in the adblog.
It seems to be complaining about an ldap dll so you may want to make sure you have all of the necesarry LDAP files (dll's) and they are not corrupt. When you installed Asset Manager, did you do a full install? If so, my understanding is that all necesarry LDAP files are included, however if you choose custom installation you must ensure the LDAP component is to be installed. What is interesting is that you say LDAP works fine with the Windows client. It seems like that type of error would prevent LDAP from working at all.
The only cases I've had where Windows client worked and Web client failed were issues with my LDAP certificate and trust store. Make sure there is no issue with these things as well.
01-29-2014 04:25 PM - edited 01-29-2014 04:27 PM
I also found this Support Tip that looks like a workaround to this issue: