Aman T

Neil, Tried your approach. No luck :-( I have attached logs from both calls ( searchRequest for eDir and AD). //eDirectory Call - getLDAPGroups filter: (appId=807) - getLDAPGroups searchRequest: SearchRequest(baseDN='ou=groups,o=sales', scope=SUB, deref=ALWAYS, sizeLimit=0, timeLimit=0, filter='(appId=807)', attrs={*}, controls={ManageDsaITRequestControl(isCritical=false)}) === Testing UnboundId Call ===== === Connection Status ===== true //Active Directory Call - getLDAPGroups filter: (appId=867)...

Wow.. Thanks for all this. I will report back with my findings using this piece of code.

Neil, thanks for the info. Unfortunately debugger is refusing to connect to the directory: Enter the password for the user: Unable to authenticate to the directory server using the provided settings: result code='81 (server down)' These machines are pretty locked down, so I can't really install wireshark. We ran a similar test on another eDirectory instance and got the same result.

Neil, Do I need to run my code from the same folder where I initiated the debugger? My current code runs on a Tomcat and I am not sure if this debugger can listen in communications initiate on Tomcat.

Neil, Thans for getting back. I'll get you this info. Please keep an eye on this thread. Thanks

Hi Jim, I have tried with SearchControls.SUBTREE_SCOPEas well and it works fine. I can provide whatever other information you folks need. searchOU/ouEX values are the same(just different variable names). One of my colleague ran into the same issue couple of months back but he simply ignored and moved to JNDI based calls. This could possibly be a bug.

Hi Jim, I have tried with SearchControls.SUBTREE_SCOPEas well and it works fine. I can provide whatever other information you folks need. searchOU/ouEX values are the same(just different variable names). One of my colleague ran into the same issue couple of months back but he simply ignore and moved to JNDI based calls. This could possibly be a bug.

Neil, Thanks for the reply. Here's an interesting find... when I tried to execute the same logic using JNDI using the same bind credentials, everything worked fine. Issue seems to be with the client here. Code below works fine for the same credentials and same eDirectory. LdapContext conn = getJNDIConnection("eDir-Name"); SearchControls searchControls = new SearchControls(); searchControls.setSearchScope(SearchControls.ONELEVEL_SCOPE); NamingEnumeration results = null; results = conn.search(searchOU,...