Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
3.14.7, 3.18.4
-
None
-
linux, jdk11, camel-main, camel-ldap, ActiveDirectory
-
Unknown
-
Regression
Description
We updated to camel 3.18.4 and this broke camel-ldap, running against ActiveDirectory.
Filter string is "(CN=USERID)". In 3.18.4, this gets escaped to "\28CN=USERID\29" (changed by CAMEL-18696), which does not return a result, but instead throws this exception:
javax.naming.directory.InvalidSearchFilterException: invalid attribute description; remaining name 'OU=Std,OU=User,OU=ORG,DC=ad,DC=example,DC=com'
at java.naming/com.sun.jndi.ldap.Filter.encodeSimpleFilter(Unknown Source)
at java.naming/com.sun.jndi.ldap.Filter.encodeFilter(Unknown Source)
at java.naming/com.sun.jndi.ldap.Filter.encodeFilterString(Unknown Source)
at java.naming/com.sun.jndi.ldap.LdapClient.search(Unknown Source)
at java.naming/com.sun.jndi.ldap.LdapCtx.doSearch(Unknown Source)
at java.naming/com.sun.jndi.ldap.LdapCtx.searchAux(Unknown Source)
at java.naming/com.sun.jndi.ldap.LdapCtx.c_search(Unknown Source)
at java.naming/com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(Unknown Source)
at java.naming/com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(Unknown Source)
at java.naming/com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(Unknown Source)
at java.naming/javax.naming.directory.InitialDirContext.search(Unknown Source)
at org.apache.camel.component.ldap.LdapProducer.simpleSearch(LdapProducer.java:129)
at org.apache.camel.component.ldap.LdapProducer.process(LdapProducer.java:83)
The same filter string used to work fine in 3.18.1
Attachments
Issue Links
- is caused by
-
CAMEL-18696 camel-ldap - Make filter a bit easier to use
- Resolved