[jira] [Resolved] (CAMEL-18809) camel-core-model: RouteDefinitionHelper should resolve the intercepted from URI which is configured with property placeholder
[ https://issues.apache.org/jira/browse/CAMEL-18809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Babak Vahdat resolved CAMEL-18809. -- Resolution: Fixed > camel-core-model: RouteDefinitionHelper should resolve the intercepted from > URI which is configured with property placeholder > - > > Key: CAMEL-18809 > URL: https://issues.apache.org/jira/browse/CAMEL-18809 > Project: Camel > Issue Type: Bug > Components: camel-core-model >Affects Versions: 3.18.4 >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Minor > Fix For: 3.18.5, 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18811) camel-ldap - InvalidSearchFilterException: invalid attribute description
[
https://issues.apache.org/jira/browse/CAMEL-18811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646826#comment-17646826
]
Christian Schubert-Huff commented on CAMEL-18811:
-
We updated to 3.18.4 with the intention to fix
[CVE-2022-45046|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-45046],
which is a blocker to our release. I have not looked into camel-spring-ldap,
yet, and may not be able to do so before January.
> camel-ldap - InvalidSearchFilterException: invalid attribute description
>
>
> Key: CAMEL-18811
> URL: https://issues.apache.org/jira/browse/CAMEL-18811
> Project: Camel
> Issue Type: Bug
> Components: camel-ldap
>Affects Versions: 3.18.4
> Environment: linux, jdk11, camel-main, camel-ldap, ActiveDirectory
>Reporter: Christian Schubert-Huff
>Priority: Minor
>
> 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:
> {code:java}
> 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)
> {code}
> The same filter string used to work fine in 3.18.1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-17946) camel-as2 - Add https support
[ https://issues.apache.org/jira/browse/CAMEL-17946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646785#comment-17646785 ] Shikhar commented on CAMEL-17946: - Draft PR: [https://github.com/apache/camel/pull/8896] > camel-as2 - Add https support > - > > Key: CAMEL-17946 > URL: https://issues.apache.org/jira/browse/CAMEL-17946 > Project: Camel > Issue Type: New Feature > Components: camel-as2 >Affects Versions: 3.16.0 >Reporter: Ted Lundqvist >Priority: Minor > Fix For: 3.x > > > The AS2 component should have support for TLS for both server and client > connections. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18661) Camel OpenTelemtery instrumentation does not make spans current
[
https://issues.apache.org/jira/browse/CAMEL-18661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18661:
Fix Version/s: 3.20.0
(was: 3.21.0)
> Camel OpenTelemtery instrumentation does not make spans current
>
>
> Key: CAMEL-18661
> URL: https://issues.apache.org/jira/browse/CAMEL-18661
> Project: Camel
> Issue Type: Bug
> Components: camel-opentelemetry
>Affects Versions: 3.19.0
> Environment: any, functional issue
>Reporter: Liudmila
>Priority: Minor
> Fix For: 3.20.0
>
> Attachments: camel_and_service_bus.png
>
>
> I have the following application:
>
> {code:java}
> @Component
> public class SourceRoute extends EndpointRouteBuilder {
> private static final String cs = "...";
> @Override
> public void configure() {
>from(timer("tick").period(1000).repeatCount(1))
> .log("Timer triggered")
> .setBody(simple("hello"))
> .to(azureServicebus("testme").
> serviceBusType("topic").
> connectionString(cs));
> }
> } {code}
>
> And I run it with [OpenTelemtery Java
> agent|https://github.com/open-telemetry/opentelemetry-java-instrumentation/].
> Camel creates "tick" and "testme" spans.
> ServiceBus SDK is instrumented too and it creates it's own spans.
> h2. Actual behavior:
> Spans created by ServiceBus SDK are unrelated to Camel spans. I.e. ServiceBus
> spans and Camel spans are in different traces (check out the attached
> screenshot).
> h2. Expected behavior:
> Camel "testme" span is a parent of ServiceBus spans:
> * tick
> ** testme
> *** ServiceBus.message
> *** ServiceBus.send
> h2. Investigation
> If I look into the OTel instrumentation code (and debug my application). I
> can see that OTel span starts here
> https://github.com/apache/camel/blob/1175c2666821457dcb6cf0921f4076508459341a/components/camel-opentelemetry/src/main/java/org/apache/camel/opentelemetry/OpenTelemetryTracer.java#L92
> and then is 'activated' here
> https://github.com/apache/camel/blob/main/components/camel-tracing/src/main/java/org/apache/camel/tracing/Tracer.java#L248
> But the activation code only puts trace_id and span_id on MDC.
> The proposal for Camel is to make OpenTelemtery span active (using
> Span.makeCurrent()).
> This is the only way underlying traces can be correlated to Camel spans.
> {code:java}
> try (Scope s = span.makeCurrent()) {
>// wrap processing, but always clean up the scope to avoid leaks
> } {code}
> OTel instrumentation will take care of propagating this context anywhere else.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18811) camel-ldap - InvalidSearchFilterException: invalid attribute description
[
https://issues.apache.org/jira/browse/CAMEL-18811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646766#comment-17646766
]
Claus Ibsen commented on CAMEL-18811:
-
Try with camel-spring-ldap.
Otherwise try to see if you can alter the code or try something and test on
your end.
> camel-ldap - InvalidSearchFilterException: invalid attribute description
>
>
> Key: CAMEL-18811
> URL: https://issues.apache.org/jira/browse/CAMEL-18811
> Project: Camel
> Issue Type: Bug
> Components: camel-ldap
>Affects Versions: 3.18.4
> Environment: linux, jdk11, camel-main, camel-ldap, ActiveDirectory
>Reporter: Christian Schubert-Huff
>Priority: Minor
>
> 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:
> {code:java}
> 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)
> {code}
> The same filter string used to work fine in 3.18.1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18811) camel-ldap - InvalidSearchFilterException: invalid attribute description
[
https://issues.apache.org/jira/browse/CAMEL-18811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18811:
Priority: Minor (was: Major)
> camel-ldap - InvalidSearchFilterException: invalid attribute description
>
>
> Key: CAMEL-18811
> URL: https://issues.apache.org/jira/browse/CAMEL-18811
> Project: Camel
> Issue Type: Bug
> Components: camel-ldap
>Affects Versions: 3.18.4
> Environment: linux, jdk11, camel-main, camel-ldap, ActiveDirectory
>Reporter: Christian Schubert-Huff
>Priority: Minor
>
> 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:
> {code:java}
> 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)
> {code}
> The same filter string used to work fine in 3.18.1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18811) camel-ldap - InvalidSearchFilterException: invalid attribute description
[
https://issues.apache.org/jira/browse/CAMEL-18811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schubert-Huff updated CAMEL-18811:
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:
{code:java}
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)
{code}
The same filter string used to work fine in 3.18.1
was:
We upgraded 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:
{code:java}
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)
{code}
The same filter string used to work fine in 3.18.1
> camel-ldap - InvalidSearchFilterException: invalid attribute description
>
>
> Key: CAMEL-18811
> URL: https://issues.apache.org/jira/browse/CAMEL-18811
> Project: Camel
> Issue Type: Bug
> Components: camel-ldap
>Affects Versions: 3.18.4
> Environment: linux, jdk11, camel-main, camel-ldap, ActiveDirectory
>Reporter: Christian Schubert-Huff
>Priority: Major
>
> 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:
> {code:java}
> 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
>
[jira] [Updated] (CAMEL-18811) camel-ldap - InvalidSearchFilterException: invalid attribute description
[
https://issues.apache.org/jira/browse/CAMEL-18811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schubert-Huff updated CAMEL-18811:
Description:
We upgraded 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:
{code:java}
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)
{code}
The same filter string used to work fine in 3.18.1
was:
We upgraded 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:
{code:java}
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)
{code}
The same filter string used to work fine in 3.18.1
> camel-ldap - InvalidSearchFilterException: invalid attribute description
>
>
> Key: CAMEL-18811
> URL: https://issues.apache.org/jira/browse/CAMEL-18811
> Project: Camel
> Issue Type: Bug
> Components: camel-ldap
>Affects Versions: 3.18.4
> Environment: linux, jdk11, camel-main, camel-ldap, ActiveDirectory
>Reporter: Christian Schubert-Huff
>Priority: Major
>
> We upgraded 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:
> {code:java}
> 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
>
[jira] [Created] (CAMEL-18811) camel-ldap - InvalidSearchFilterException: invalid attribute description
Christian Schubert-Huff created CAMEL-18811:
---
Summary: camel-ldap - InvalidSearchFilterException: invalid
attribute description
Key: CAMEL-18811
URL: https://issues.apache.org/jira/browse/CAMEL-18811
Project: Camel
Issue Type: Bug
Components: camel-ldap
Affects Versions: 3.18.4
Environment: linux, jdk11, camel-main, camel-ldap, ActiveDirectory
Reporter: Christian Schubert-Huff
We upgraded 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:
{code:java}
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)
{code}
The same filter string used to work fine in 3.18.1
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18809) camel-core-model: RouteDefinitionHelper should resolve the intercepted from URI which is configured with property placeholder
[ https://issues.apache.org/jira/browse/CAMEL-18809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18809: Fix Version/s: 3.20.0 (was: 3.21.0) > camel-core-model: RouteDefinitionHelper should resolve the intercepted from > URI which is configured with property placeholder > - > > Key: CAMEL-18809 > URL: https://issues.apache.org/jira/browse/CAMEL-18809 > Project: Camel > Issue Type: Bug > Components: camel-core-model >Affects Versions: 3.18.4 >Reporter: Babak Vahdat >Assignee: Babak Vahdat >Priority: Minor > Fix For: 3.18.5, 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18667) camel-telegram - Update models according to the current API documentation
[ https://issues.apache.org/jira/browse/CAMEL-18667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646599#comment-17646599 ] Sergei Portnov commented on CAMEL-18667: Sorry, I was sick. I'm still working on this > camel-telegram - Update models according to the current API documentation > - > > Key: CAMEL-18667 > URL: https://issues.apache.org/jira/browse/CAMEL-18667 > Project: Camel > Issue Type: Improvement > Components: camel-telegram >Reporter: Sergei Portnov >Priority: Minor > Fix For: 3.x > > > Current Telegram models are outdated. Need to update this to match the > current [API > documentation|https://core.telegram.org/bots/api#available-types]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18748) camel-catalog - Missing properties for ErrorHandler in catalog for yaml DSL
[ https://issues.apache.org/jira/browse/CAMEL-18748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18748. - Resolution: Fixed > camel-catalog - Missing properties for ErrorHandler in catalog for yaml DSL > --- > > Key: CAMEL-18748 > URL: https://issues.apache.org/jira/browse/CAMEL-18748 > Project: Camel > Issue Type: Improvement > Components: camel-catalog >Reporter: Marat Gubaidullin >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.20.0 > > > Different properties for the ErrorHandler model in catalog and > camelYamlDsl.json > [https://github.com/apache/camel/blob/main/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/errorHandler.json] > and > [https://github.com/apache/camel/blob/30029a9f3f02befd111e57a301025d94fe565c73/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L760] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18748) camel-catalog - Missing properties for ErrorHandler in catalog for yaml DSL
[ https://issues.apache.org/jira/browse/CAMEL-18748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18748: Issue Type: Improvement (was: Bug) > camel-catalog - Missing properties for ErrorHandler in catalog for yaml DSL > --- > > Key: CAMEL-18748 > URL: https://issues.apache.org/jira/browse/CAMEL-18748 > Project: Camel > Issue Type: Improvement > Components: camel-catalog >Reporter: Marat Gubaidullin >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.20.0 > > > Different properties for the ErrorHandler model in catalog and > camelYamlDsl.json > [https://github.com/apache/camel/blob/main/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/errorHandler.json] > and > [https://github.com/apache/camel/blob/30029a9f3f02befd111e57a301025d94fe565c73/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L760] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18177) camel-slack - Honour Retry-After when requests are rate-limited
[
https://issues.apache.org/jira/browse/CAMEL-18177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17646562#comment-17646562
]
Luca Burgazzoli commented on CAMEL-18177:
-
/cc [~acosentino]
> camel-slack - Honour Retry-After when requests are rate-limited
> ---
>
> Key: CAMEL-18177
> URL: https://issues.apache.org/jira/browse/CAMEL-18177
> Project: Camel
> Issue Type: Improvement
> Components: camel-slack
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: 3.x
>
>
> According to slack's doc:
> {code}
> If you exceed a rate limit when using any of our HTTP-based APIs (including
> Incoming Webhooks), Slack will return a HTTP 429 Too Many Requests error, and
> a Retry-After HTTP header containing the number of seconds until you can
> retry.
> {code}
> We should explore if we can honor the Retry-After seconds to perform the
> next poll.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18796) camel-kafka: kafka consumer stops in case of an authentication issue
[
https://issues.apache.org/jira/browse/CAMEL-18796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18796.
-
Resolution: Fixed
> camel-kafka: kafka consumer stops in case of an authentication issue
>
>
> Key: CAMEL-18796
> URL: https://issues.apache.org/jira/browse/CAMEL-18796
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka
>Affects Versions: 3.18.0, 3.19.0
>Reporter: Luca Burgazzoli
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 3.18.5, 3.20.0
>
>
> I'm running in a strange behavior of the camle-kafka component in case of a
> glitch/temporary authentication issue. Assuming we have the following code:
> {code:java}
> //usr/bin/env jbang "$0" "$@" ; exit $?
> //
> //DEPS io.quarkus.platform:quarkus-camel-bom:2.14.2.Final@pom
> //DEPS org.apache.camel.quarkus:camel-quarkus-kafka
> //DEPS org.apache.camel.quarkus:camel-quarkus-log
> //DEPS org.apache.camel.quarkus:camel-quarkus-direct
> //
> //JAVAC_OPTIONS -parameters
> //JAVA_OPTIONS -Djava.util.logging.manager=org.jboss.logmanager.LogManager
> //
> import org.apache.camel.ExtendedCamelContext;
> import org.apache.camel.builder.endpoint.EndpointRouteBuilder;
> public class ck extends EndpointRouteBuilder {
> @Override
> public void configure() throws Exception {
> getCamelContext().adapt(ExtendedCamelContext.class)
> .setErrorHandlerFactory(
> deadLetterChannel("direct:dlq")
> );
> var kafka = kafka("demo")
> .brokers("{{test.kafka.broker}}")
> .autoOffsetReset("earliest")
> .securityProtocol("SASL_SSL")
> .saslMechanism("PLAIN")
>
> .saslJaasConfig("org.apache.kafka.common.security.plain.PlainLoginModule
> required username='{{test.kafka.username}}'
> password='{{test.kafka.password}}';");
> from("direct:dlq")
> .to("log:dlq?showAll=true=true");
> from(kafka)
> .to("log:kafka?showAll=true=true");
> }
> }
> {code}
> What this route is doing is:
> 1. set-up a global error handler (send to a DLQ)
> 2. poll data from a kafka topic
> If for some reason there is a glitch in the authentication machinery, then
> the KafkaConsumer thread is terminated and no more poll/reconnection attempt
> are made.
> {code}
> 2022-12-05 21:52:48,728 DEBUG
> [org.apa.cam.com.kaf.con.sup.KafkaRecordProcessorFacade] (Camel (camel-1)
> thread #1 - KafkaConsumer[demo]) Last poll on thread demo-Thread 0 resulted
> on 0 records to process
> 2022-12-05 21:52:53,729 DEBUG
> [org.apa.cam.com.kaf.con.sup.KafkaRecordProcessorFacade] (Camel (camel-1)
> thread #1 - KafkaConsumer[demo]) Last poll on thread demo-Thread 0 resulted
> on 0 records to process
> 2022-12-05 21:52:58,730 DEBUG
> [org.apa.cam.com.kaf.con.sup.KafkaRecordProcessorFacade] (Camel (camel-1)
> thread #1 - KafkaConsumer[demo]) Last poll on thread demo-Thread 0 resulted
> on 0 records to process
> 2022-12-05 21:53:03,731 DEBUG
> [org.apa.cam.com.kaf.con.sup.KafkaRecordProcessorFacade] (Camel (camel-1)
> thread #1 - KafkaConsumer[demo]) Last poll on thread demo-Thread 0 resulted
> on 0 records to process
> 2022-12-05 21:53:08,732 DEBUG
> [org.apa.cam.com.kaf.con.sup.KafkaRecordProcessorFacade] (Camel (camel-1)
> thread #1 - KafkaConsumer[demo]) Last poll on thread demo-Thread 0 resulted
> on 0 records to process
> 2022-12-05 21:53:09,598 INFO [org.apa.kaf.com.net.Selector] (Camel (camel-1)
> thread #1 - KafkaConsumer[demo]) [Consumer
> clientId=consumer-9fc21222-980b-4dd7-8e2b-0a228a4f3fe5-1,
> groupId=9fc21222-980b-4dd7-8e2b-0a228a4f3fe5] Failed re-authentication with
> broker-0-lb-cos-ce---l--votu-gig.bf2.kafka.rhcloud.com/34.247.249.77
> (channelId=2147483647) (Authentication failed: credentials for user could not
> be verified)
> 2022-12-05 21:53:09,602 ERROR [org.apa.kaf.cli.NetworkClient] (Camel
> (camel-1) thread #1 - KafkaConsumer[demo]) [Consumer
> clientId=consumer-9fc21222-980b-4dd7-8e2b-0a228a4f3fe5-1,
> groupId=9fc21222-980b-4dd7-8e2b-0a228a4f3fe5] Connection to node 2147483647
> (broker-0-lb-cos-ce---l--votu-gig.bf2.kafka.rhcloud.com/34.247.249.77:443)
> failed authentication due to: Authentication failed: credentials for user
> could not be verified
> 2022-12-05 21:53:09,605 WARN [org.apa.cam.com.kaf.KafkaFetchRecords] (Camel
> (camel-1) thread #1 - KafkaConsumer[demo]) Exception
> org.apache.kafka.common.errors.SaslAuthenticationException caught by thread
> demo-Thread 0 while polling topic demo from kafka: Authentication failed:
> credentials for user could not be verified:
> org.apache.kafka.common.errors.SaslAuthenticationException: Authentication
> failed: credentials for user could not be
[jira] [Updated] (CAMEL-18748) camel-catalog - Missing properties for ErrorHandler in catalog for yaml DSL
[ https://issues.apache.org/jira/browse/CAMEL-18748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18748: Fix Version/s: 3.20.0 (was: 3.21.0) > camel-catalog - Missing properties for ErrorHandler in catalog for yaml DSL > --- > > Key: CAMEL-18748 > URL: https://issues.apache.org/jira/browse/CAMEL-18748 > Project: Camel > Issue Type: Bug > Components: camel-catalog >Reporter: Marat Gubaidullin >Priority: Major > Fix For: 3.20.0 > > > Different properties for the ErrorHandler model in catalog and > camelYamlDsl.json > [https://github.com/apache/camel/blob/main/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/errorHandler.json] > and > [https://github.com/apache/camel/blob/30029a9f3f02befd111e57a301025d94fe565c73/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L760] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18748) camel-catalog - Missing properties for ErrorHandler in catalog for yaml DSL
[ https://issues.apache.org/jira/browse/CAMEL-18748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-18748: --- Assignee: Claus Ibsen > camel-catalog - Missing properties for ErrorHandler in catalog for yaml DSL > --- > > Key: CAMEL-18748 > URL: https://issues.apache.org/jira/browse/CAMEL-18748 > Project: Camel > Issue Type: Bug > Components: camel-catalog >Reporter: Marat Gubaidullin >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.20.0 > > > Different properties for the ErrorHandler model in catalog and > camelYamlDsl.json > [https://github.com/apache/camel/blob/main/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/models/errorHandler.json] > and > [https://github.com/apache/camel/blob/30029a9f3f02befd111e57a301025d94fe565c73/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camelYamlDsl.json#L760] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
