Hurrah!! Problem solved!
Well, at least I think so!!
This is the configuration I am using:
I had to create a user in LDS called admin and allocated it to the reader role in LDS (if you dont have this, import it from the ldf files provided for LDS).Code:<authentication-manager alias="ldapAuthenicationManager">
<ldap-authentication-provider
user-search-filter="(uid={0})"
group-search-filter="(member=userGroup)"
>
</ldap-authentication-provider>
</authentication-manager>
<ldap-server url="ldap://server:50006/$CN=Users,CN=Domain,CN=local" manager-dn="Cn=Admin,CN=Domain,CN=local" manager-password="Pssword101" />
After this I created a user and then a group, I added my user to the group I create ad
At this point I was getting Ldap error 32. After a serious amount of debugging through the spring security code and looking at the event logs of the server I guessed that the problem was with how AD LDS was set up. After a lot of fiddling and guess work I stumbled upon the problem.
To resolve this I ended up having to add the user I wanted to log in with (not the manager-dn) to the reader group also to allow a successful bind. Doing that resolved the problem for me
Hopefully this is of use?
