Issue #582 has been updated by Raphaël Ouazana. Status changed from Feedback to Closed % Done changed from 50 to 100
The right way is to use the search without the naming context. ---------------------------------------- Bug #582: case sensitive DN comparisons in ScriptableJndiServices http://tools.lsc-project.org/issues/582 Author: Jon Kidder Status: Closed Priority: Normal Assigned to: Category: Core Target version: 2.1 Problem in version: 2.0.1 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. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
