I am new to ad lds and ldap. I created an instance of ad lds using port 50000 (for non-ssl) and created a user with adsi edit as follows:
DN is CN=UserInsideOU,OU=OUNumber1,O=Microsoft,C=US
I can get on a second server and use ldp.exe 3.0 to do a simple bind successfully. I can also see this in wireshark, although oddly the bindrequest has a blank after C=US.
Then it does a searchrequest on <ROOT> baseObject which is successful. I do not know what the searchRequest is doing or what ROOT is.
Now I am debugging a java service that is supposed to authenticate in the same way as ldp.
the wireshark capture on this java service attempt has the following differences:
1. there is no blank after c=us in the bind request, but the bind is successful
2. the search request is "OU=OUNumber1,O=Microsoft,C=US"without the blank followed by wholeSubTree, but the working (LDP) traffic says searchRequest "<ROOT>" baseObject
3. the search above for wholeSubTree fails...nosuchObject DSID-031522c9, Problem 2001 best match of 'o=Microsoft,C=US'
4. Is the information in the search request case sensitive?
5. Why is there a search immediately after the simple bind?
6. Is it possible that I need specific properties set on the user of ou objects that I created by hand in AdsiEdit that must be populated with certain values?
Any answers or explanation as to why there is a search after the bind or the other steps would be greatly appreciated.
Thanks.
leo