[
https://issues.apache.org/jira/browse/CAMEL-11060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955596#comment-15955596
]
ASF GitHub Bot commented on CAMEL-11060:
----------------------------------------
GitHub user kgeis opened a pull request:
https://github.com/apache/camel/pull/1592
CAMEL-11060: fall back to context source base DN
This patch makes the Spring LDAP component so that if no "dn" parameter is
specified, it uses the base defined on the Spring LDAP ContextSource. An error
will only occur if the base is defined in neither place.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kgeis/camel CAMEL-11060
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1592.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1592
----
commit 018be2d8dbae53fd262eebeaeee7f7be3c825a33
Author: Ken Geis <[email protected]>
Date: 2017-04-04T18:34:22Z
CAMEL-11060: fall back on base DN specified on Spring LDAP context source
if none is defined in the URI
----
> 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)