[jira] [Commented] (CAMEL-11060) dn shouldn't be strictly required for Spring LDAP component

["onder sezgin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-11060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955226#comment-15955226 ] 

onder sezgin commented on CAMEL-11060:
--------------------------------------

well, i think better approach would be able to check if baseDN was set on LdapTemplate and if none, grab the DN from the enpoint options. I am not an expert on ldap and spring-ldap API. However, i could not see a way to check if LdapTemplate was created with baseDN. spring-ldap has limitations i guess and so the component comes with it. How about an option on the endpoint, so that camel would give you the control over if you set the base dn or not? maybe we can work on such PR? what do you think?

> 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: Improvement
>    Affects Versions: 2.18.3
>            Reporter: Ken Geis
>            Priority: Minor
>
> 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)