You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Ken Geis (JIRA)" <ji...@apache.org> on 2017/03/23 20:10:41 UTC
[jira] [Commented] (CAMEL-11060) dn shouldn't be strictly required
for Spring LDAP component
[ https://issues.apache.org/jira/browse/CAMEL-11060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15939147#comment-15939147 ]
Ken Geis commented on CAMEL-11060:
----------------------------------
I've found that this forces me not to set the base property on my ContextSource. If I do, then the base is duplicated. For example, if I set the context source base to "ou=people" and the query DN to "ou=people", then Spring LDAP searches with a base "ou=people,ou=people" and it bombs because that does not exist.
> dn shouldn't be strictly required for Spring LDAP component
> -----------------------------------------------------------
>
> Key: CAMEL-11060
> URL: https://issues.apache.org/jira/browse/CAMEL-11060
> Project: Camel
> Issue Type: Bug
> Affects Versions: 2.18.3
> Reporter: Ken Geis
>
> I set a base DN in my LdapContextSource underlying the LdapTemplate. It's redundant to need to set it in my route, but if I don't, the SpringLdapProducer complains "DN must not be empty, but you provided an empty DN".
> In other code, I do this and regularly pass an empty string as the base to LdapTemplate.search(base, ...).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)