I have successfully setup AD LDS to extensively extend the schema to add numerous new attributes for several applications. I have also setup SSL and have been successful in doing all the Bind scenarios via ADSIedit and Ldp. I also can Bind and pull back any information I wish via PowerShell. Everything appears to be working correctly.
Now when I had customers attempt to point to AD LDS with their apps, they can't Bind. For example, GADS (Google Apps Directory Sync) is one of them. We would like to point to AD LDS to pull several attributes. I can't get GADS to connect to AD LDS. If I point to an AD DS (Domain Controller) it connects great, but not if I point to AD LDS. I can use ADSIedit on the server that GADS would be running on and with that tool, I am successfully connecting, just not through the GADS connection. The same hold true for other applications (JAMF is another example).
I can't believe that AD LDS would be deployed if it only works with some things and not others. I have spent a lot of time searching the web and trying many different suggestions. Nothing seems to be working.
Has anyone had issues using non-Windows applications authenticating users through AD LDS (userProxyFull)? If yes, what should I try?
I had my customer call support on four different apps and they all state that they don't support AD LDS. I don't know if they really don't or just don't understand what AD LDS is supposed to be. In reading over all the Microsoft info on AD LDS, it appears to be exactly what I want, but if it doesn't work (or I just can't make it work) then I will have to pursue other solutions.
Thanks in advance
