2013/9/25 Alexander Amaral <[email protected]> > Apache DS doesn't like it either. In Apache DS, it works as long as 1) > the # sign is the first character in the string, or 2) if the two > characters immediately after the # sign don't form a valid hex value. I'm > assuming LSC works by the same principle. > > The following work: > > #10user > user#5 > this#1user > > The following don't: > > user#99 > this#10user > user#F1 > > I believe all of the combinations above are valid. There was a spring > framework bug related to this that was closed earlier this year. See > below: > https://jira.springsource.org/**browse/LDAP-229<https://jira.springsource.org/browse/LDAP-229> > >
We use the Apache DS API, as you can see in the error message: org.apache.directory.shared.ldap.exception.LdapInvalidDnException If the DN is really valid againts LDAP RFC, a bug should be open on Apache DS API side. Clément.
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
