I ran in to an issue I'd like to throw out here to see if this is expected
behavior or a bug that needs reported.
When there is a context specified in the <ldapConnection><url> tag I've
noticed that DNs passed to the ScriptableJndiServices must use the exact
same case or the context gets added again when submitting the request to
the LDAP server. For example when using:
<ldapconnection>
<url>ldap://myserver.com/dc=DomainA,dc=com/</url>
</ldapconnection>
If you use the following:
srcLdap.attribute("cn=record1,dc=domaina,dc=com","cn")
The DN of the search base passed to the LDAP server looks like:
cn=record1,dc=domaina,dc=com,dc=DomainA,dc=com
Which results in an empty result set or object not found error. However,
if I use:
srcLdap.attribute("cn=record1,dc=DomainA,dc=com","cn")
I get a correct result set. I've noticed this behavior for the attribute,
exists, and search methods. Is this expected behavior or a bug?
-Jon C. Kidder
American Electric Power
Middleware Services
614-716-4970_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
