[jira] [Moved] (CAMEL-20041) Move CxfMessageHeadersRelayTest to camel-cxf-soap
[ https://issues.apache.org/jira/browse/CAMEL-20041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh moved CXF-8949 to CAMEL-20041: -- Key: CAMEL-20041 (was: CXF-8949) Workflow: classic default workflow (was: Default workflow, editable Closed status) Project: Camel (was: CXF) > Move CxfMessageHeadersRelayTest to camel-cxf-soap > - > > Key: CAMEL-20041 > URL: https://issues.apache.org/jira/browse/CAMEL-20041 > Project: Camel > Issue Type: Bug >Reporter: Peter Palaga >Priority: Major > > The named test currently lives under > [camel-cxf-spring-soap|https://github.com/apache/camel/blob/0e26ffa824b7529fb916a53c327d7daeb78205ed/components/camel-cxf/camel-cxf-spring-soap/src/test/java/org/apache/camel/component/cxf/soap/headers/CxfMessageHeadersRelayTest.java#L731CxfMessageHeadersRelayTest] > but there does not seem to be anything Spring specific in the test. Moreover > it is cited on the CXF component page > https://camel.apache.org/components/4.0.x/cxf-component.html#_how_to_get_and_set_soap_headers_in_pojo_mode. > > We should attempt to move the test to > [camel-cxf-soap|https://github.com/apache/camel/tree/main/components/camel-cxf/camel-cxf-soap] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18951) Introducing SBOM generation
[ https://issues.apache.org/jira/browse/CAMEL-18951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762605#comment-17762605 ] Colm O hEigeartaigh commented on CAMEL-18951: - Alright thanks! > Introducing SBOM generation > > > Key: CAMEL-18951 > URL: https://issues.apache.org/jira/browse/CAMEL-18951 > Project: Camel > Issue Type: Improvement > Components: build system >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.0-M1, 4.0.0 > > > We could use some of the maven plugin out there: > https://github.com/CycloneDX/cyclonedx-maven-plugin > To me this one is really complete. > For the beginning I will use a profile without adding the generated SBOM to > the assembly (I don't know how big will it be), but I do believe it would be > really helpful and I would like to add it as standard information with each > release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18951) Introducing SBOM generation
[ https://issues.apache.org/jira/browse/CAMEL-18951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762602#comment-17762602 ] Colm O hEigeartaigh commented on CAMEL-18951: - [~acosentino] Is this generated SBOM available somewhere in Maven Central? For example I added it for Santuario recently [https://repo1.maven.org/maven2/org/apache/santuario/xmlsec/4.0.0-M1/] > Introducing SBOM generation > > > Key: CAMEL-18951 > URL: https://issues.apache.org/jira/browse/CAMEL-18951 > Project: Camel > Issue Type: Improvement > Components: build system >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.0-M1, 4.0.0 > > > We could use some of the maven plugin out there: > https://github.com/CycloneDX/cyclonedx-maven-plugin > To me this one is really complete. > For the beginning I will use a profile without adding the generated SBOM to > the assembly (I don't know how big will it be), but I do believe it would be > really helpful and I would like to add it as standard information with each > release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-15403) camel-xmlsecurity - Some unit tests fails with Oracle JDK8 261
[
https://issues.apache.org/jira/browse/CAMEL-15403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418668#comment-17418668
]
Colm O hEigeartaigh commented on CAMEL-15403:
-
Thanks [~ffang] ! Could you merge to 3.7.x as well?
> camel-xmlsecurity - Some unit tests fails with Oracle JDK8 261
> --
>
> Key: CAMEL-15403
> URL: https://issues.apache.org/jira/browse/CAMEL-15403
> Project: Camel
> Issue Type: Test
> Components: camel-xmlsecurity
>Affects Versions: 3.4.2
>Reporter: Freeman Yue Fang
>Assignee: Freeman Yue Fang
>Priority: Major
> Fix For: 3.5.0, 3.4.4
>
>
> It's caused by a newline "\n" isn't expected in the test payload for JDK
> 1.8_261.
> I noticed that we've already had code like
> {code}
> if (TestSupport.getJavaMajorVersion() >= 9) {
> includeNewLine = false;
> }
> {code}
> to determine need this newline or not. And I believe the lastest JDK8(Oracle
> JDK8 261) surely take the same logic as JDK9+ now.
> We need also check the 1.8 minor version
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15403) camel-xmlsecurity - Some unit tests fails with Oracle JDK8 261
[
https://issues.apache.org/jira/browse/CAMEL-15403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418487#comment-17418487
]
Colm O hEigeartaigh commented on CAMEL-15403:
-
[~ffang] Looks like this fix causes other JDK vendors to fail. Right now the
tests fail for me with:
openjdk version "1.8.0_265"
OpenJDK Runtime Environment (Zulu 8.48.0.53-CA-linux64) (build 1.8.0_265-b11)
> camel-xmlsecurity - Some unit tests fails with Oracle JDK8 261
> --
>
> Key: CAMEL-15403
> URL: https://issues.apache.org/jira/browse/CAMEL-15403
> Project: Camel
> Issue Type: Test
> Components: camel-xmlsecurity
>Affects Versions: 3.4.2
>Reporter: Freeman Yue Fang
>Assignee: Freeman Yue Fang
>Priority: Major
> Fix For: 3.5.0, 3.4.4
>
>
> It's caused by a newline "\n" isn't expected in the test payload for JDK
> 1.8_261.
> I noticed that we've already had code like
> {code}
> if (TestSupport.getJavaMajorVersion() >= 9) {
> includeNewLine = false;
> }
> {code}
> to determine need this newline or not. And I believe the lastest JDK8(Oracle
> JDK8 261) surely take the same logic as JDK9+ now.
> We need also check the 1.8 minor version
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (CAMEL-16910) Update Commons Compress to 1.21
[ https://issues.apache.org/jira/browse/CAMEL-16910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned CAMEL-16910: --- Assignee: Andrea Cosentino > Update Commons Compress to 1.21 > --- > > Key: CAMEL-16910 > URL: https://issues.apache.org/jira/browse/CAMEL-16910 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.7.6, 3.11.2 > > > The main branch update Commons Compress to 1.21: > ommit 0d26c3124ceb66c508e3d0cfbb4fb0400e5417b2 > Author: Andrea Cosentino > Date: Wed Jul 14 08:01:21 2021 +0200 > > Upgrade Commons-compress to version 1.21 > We should backport it for 3.11.x + 3.7.x as it fixes several high CVEs, e.g. > https://nvd.nist.gov/vuln/detail/CVE-2021-35517 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16910) Update Commons Compress to 1.21
Colm O hEigeartaigh created CAMEL-16910: --- Summary: Update Commons Compress to 1.21 Key: CAMEL-16910 URL: https://issues.apache.org/jira/browse/CAMEL-16910 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Fix For: 3.7.6, 3.11.2 The main branch update Commons Compress to 1.21: ommit 0d26c3124ceb66c508e3d0cfbb4fb0400e5417b2 Author: Andrea Cosentino Date: Wed Jul 14 08:01:21 2021 +0200 Upgrade Commons-compress to version 1.21 We should backport it for 3.11.x + 3.7.x as it fixes several high CVEs, e.g. https://nvd.nist.gov/vuln/detail/CVE-2021-35517 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-16389) Remove json-smart
[ https://issues.apache.org/jira/browse/CAMEL-16389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17307054#comment-17307054 ] Colm O hEigeartaigh commented on CAMEL-16389: - Oops, sorry about that. > Remove json-smart > - > > Key: CAMEL-16389 > URL: https://issues.apache.org/jira/browse/CAMEL-16389 > Project: Camel > Issue Type: Task >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.10.0 > > > There is a issue in json-smart, and the project appears not to be updated any > longer: [https://github.com/json-path/JsonPath/issues/676] > It's used in two components: > * camel-chunk - Appears to be no longer needed > * camel-jsonpath - I propose to swap it out to use Jackson instead via > [https://github.com/json-path/JsonPath/blob/master/README.md#jsonprovider-spi] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-16389) Remove json-smart
[ https://issues.apache.org/jira/browse/CAMEL-16389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-16389 started by Colm O hEigeartaigh. --- > Remove json-smart > - > > Key: CAMEL-16389 > URL: https://issues.apache.org/jira/browse/CAMEL-16389 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.9.0 > > > There is a security issue in json-smart, and the project appears not to be > updated any longer: [https://github.com/json-path/JsonPath/issues/676] > It's used in two components: > * camel-chunk - Appears to be no longer needed > * camel-jsonpath - I propose to swap it out to use Jackson instead via > [https://github.com/json-path/JsonPath/blob/master/README.md#jsonprovider-spi] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-16389) Remove json-smart
Colm O hEigeartaigh created CAMEL-16389: --- Summary: Remove json-smart Key: CAMEL-16389 URL: https://issues.apache.org/jira/browse/CAMEL-16389 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.9.0 There is a security issue in json-smart, and the project appears not to be updated any longer: [https://github.com/json-path/JsonPath/issues/676] It's used in two components: * camel-chunk - Appears to be no longer needed * camel-jsonpath - I propose to swap it out to use Jackson instead via [https://github.com/json-path/JsonPath/blob/master/README.md#jsonprovider-spi] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-15705) camel 2.x - camel-chronicle feature install failed due to xstream-java8 version
[
https://issues.apache.org/jira/browse/CAMEL-15705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved CAMEL-15705.
-
Resolution: Fixed
> camel 2.x - camel-chronicle feature install failed due to xstream-java8
> version
>
>
> Key: CAMEL-15705
> URL: https://issues.apache.org/jira/browse/CAMEL-15705
> Project: Camel
> Issue Type: Bug
> Components: osgi
>Affects Versions: 2.25.2
> Environment: Java 8
>Reporter: Xilai Dai
>Priority: Minor
> Fix For: 2.25.3
>
>
> Start karaf 4.2.9 OSGi container, execute:
> karaf@root()> feature:repo-add camel 2.25.2
> karaf@root()> feature:install camel-chronicle
> {code}
> Caused by: java.io.IOException: Error resolving artifact
> org.apache.servicemix.bundles:org.apache.servicemix.bundles.xstream-java8:jar:1.4.11.1_1:
> [Could not find artifact
> org.apache.servicemix.bundles:org.apache.servicemix.bundles.xstream-java8:jar:1.4.11.1_1
> in central (https://repo1.maven.org/maven2/)]
> {code}
> The bundle "xstream-java8" has to be corrected to "xstream".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CAMEL-15591) Put a configurable limit on the size of unzipped data using camel-zipfile + camel-tarfile
[ https://issues.apache.org/jira/browse/CAMEL-15591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-15591. - Resolution: Fixed > Put a configurable limit on the size of unzipped data using camel-zipfile + > camel-tarfile > - > > Key: CAMEL-15591 > URL: https://issues.apache.org/jira/browse/CAMEL-15591 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.6.0, 3.4.5 > > > For camel-zipfile + camel-tarfile, there is no limit on the size of > uncompressed data, potentially leading to an OOM Error. Instead we should > have a configurable limit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (CAMEL-15591) Put a configurable limit on the size of unzipped data using camel-zipfile + camel-tarfile
[ https://issues.apache.org/jira/browse/CAMEL-15591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-15591 started by Colm O hEigeartaigh. --- > Put a configurable limit on the size of unzipped data using camel-zipfile + > camel-tarfile > - > > Key: CAMEL-15591 > URL: https://issues.apache.org/jira/browse/CAMEL-15591 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.6.0, 3.4.5 > > > For camel-zipfile + camel-tarfile, there is no limit on the size of > uncompressed data, potentially leading to an OOM Error. Instead we should > have a configurable limit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15591) Put a configurable limit on the size of unzipped data using camel-zipfile + camel-tarfile
Colm O hEigeartaigh created CAMEL-15591: --- Summary: Put a configurable limit on the size of unzipped data using camel-zipfile + camel-tarfile Key: CAMEL-15591 URL: https://issues.apache.org/jira/browse/CAMEL-15591 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.6.0, 3.4.5 For camel-zipfile + camel-tarfile, there is no limit on the size of uncompressed data, potentially leading to an OOM Error. Instead we should have a configurable limit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14811) Remove JMX Connector configuration
[ https://issues.apache.org/jira/browse/CAMEL-14811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17199845#comment-17199845 ] Colm O hEigeartaigh commented on CAMEL-14811: - I agree with [~bedla] . Also, it is not a "fix" but the removal of a feature. To be secure just don't use the JMX Connector in earlier releases. > Remove JMX Connector configuration > -- > > Key: CAMEL-14811 > URL: https://issues.apache.org/jira/browse/CAMEL-14811 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > For 3.2.0, we should remove the JMX Connector configuration in > camel-management. Creating our own registry is not properly secure and > doesn't buy us anything extra over just using the default JVM JMX Settings. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14742) Prevent JMX rebinding
[ https://issues.apache.org/jira/browse/CAMEL-14742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-14742. - Resolution: Fixed > Prevent JMX rebinding > - > > Key: CAMEL-14742 > URL: https://issues.apache.org/jira/browse/CAMEL-14742 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to prevent JMX rebinding. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14742) Prevent JMX rebinding
[ https://issues.apache.org/jira/browse/CAMEL-14742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-14742: Fix Version/s: (was: 2.25.1) > Prevent JMX rebinding > - > > Key: CAMEL-14742 > URL: https://issues.apache.org/jira/browse/CAMEL-14742 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to prevent JMX rebinding. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14742) Prevent JMX rebinding
[ https://issues.apache.org/jira/browse/CAMEL-14742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071612#comment-17071612 ] Colm O hEigeartaigh commented on CAMEL-14742: - OK will do, thanks. > Prevent JMX rebinding > - > > Key: CAMEL-14742 > URL: https://issues.apache.org/jira/browse/CAMEL-14742 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.25.1, 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to prevent JMX rebinding. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14742) Prevent JMX rebinding
[ https://issues.apache.org/jira/browse/CAMEL-14742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071570#comment-17071570 ] Colm O hEigeartaigh commented on CAMEL-14742: - I could merge this fix for 2.25.x? https://github.com/apache/camel/pull/3651 > Prevent JMX rebinding > - > > Key: CAMEL-14742 > URL: https://issues.apache.org/jira/browse/CAMEL-14742 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.25.1, 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to prevent JMX rebinding. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14811) Remove JMX Connector configuration
[ https://issues.apache.org/jira/browse/CAMEL-14811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-14811. - Resolution: Fixed > Remove JMX Connector configuration > -- > > Key: CAMEL-14811 > URL: https://issues.apache.org/jira/browse/CAMEL-14811 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > For 3.2.0, we should remove the JMX Connector configuration in > camel-management. Creating our own registry is not properly secure and > doesn't buy us anything extra over just using the default JVM JMX Settings. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14811) Remove JMX Connector configuration
Colm O hEigeartaigh created CAMEL-14811: --- Summary: Remove JMX Connector configuration Key: CAMEL-14811 URL: https://issues.apache.org/jira/browse/CAMEL-14811 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.2.0 For 3.2.0, we should remove the JMX Connector configuration in camel-management. Creating our own registry is not properly secure and doesn't buy us anything extra over just using the default JVM JMX Settings. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14742) Prevent JMX rebinding
Colm O hEigeartaigh created CAMEL-14742: --- Summary: Prevent JMX rebinding Key: CAMEL-14742 URL: https://issues.apache.org/jira/browse/CAMEL-14742 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.0.2, 2.25.1, 3.2.0, 3.1.1 This task is to prevent JMX rebinding. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14711) Disable RabbitMQ Java serialization by default
[ https://issues.apache.org/jira/browse/CAMEL-14711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-14711: Description: This task is to disable the Rabbit MQ Java serialization functionality by default due to security reasons. It can be re-enabled using an "allowMessageBodySerialization" parameter. (was: This task is to remove the Rabbit MQ Java serialization functionality (from master only) due to security reasons.) > Disable RabbitMQ Java serialization by default > -- > > Key: CAMEL-14711 > URL: https://issues.apache.org/jira/browse/CAMEL-14711 > Project: Camel > Issue Type: Improvement > Components: camel-rabbitmq >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.2, 2.25.1, 3.2.0, 3.1.1 > > > This task is to disable the Rabbit MQ Java serialization functionality by > default due to security reasons. It can be re-enabled using an > "allowMessageBodySerialization" parameter. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14711) Disable RabbitMQ Java serialization by default
[ https://issues.apache.org/jira/browse/CAMEL-14711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-14711: Fix Version/s: 3.1.1 2.25.1 3.0.2 > Disable RabbitMQ Java serialization by default > -- > > Key: CAMEL-14711 > URL: https://issues.apache.org/jira/browse/CAMEL-14711 > Project: Camel > Issue Type: Improvement > Components: camel-rabbitmq >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.2, 2.25.1, 3.2.0, 3.1.1 > > > This task is to remove the Rabbit MQ Java serialization functionality (from > master only) due to security reasons. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14711) Disable RabbitMQ Java serialization by default
[ https://issues.apache.org/jira/browse/CAMEL-14711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-14711: Summary: Disable RabbitMQ Java serialization by default (was: Remove RabbitMQ Java serialization) > Disable RabbitMQ Java serialization by default > -- > > Key: CAMEL-14711 > URL: https://issues.apache.org/jira/browse/CAMEL-14711 > Project: Camel > Issue Type: Improvement > Components: camel-rabbitmq >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.2.0 > > > This task is to remove the Rabbit MQ Java serialization functionality (from > master only) due to security reasons. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14711) Remove RabbitMQ Java serialization
[ https://issues.apache.org/jira/browse/CAMEL-14711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-14711: Summary: Remove RabbitMQ Java serialization (was: Remove rabbit mq Java serialization) > Remove RabbitMQ Java serialization > -- > > Key: CAMEL-14711 > URL: https://issues.apache.org/jira/browse/CAMEL-14711 > Project: Camel > Issue Type: Improvement > Components: camel-rabbitmq >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.2.0 > > > This task is to remove the Rabbit MQ Java serialization functionality (from > master only) due to security reasons. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14711) Remove rabbit mq Java serialization
Colm O hEigeartaigh created CAMEL-14711: --- Summary: Remove rabbit mq Java serialization Key: CAMEL-14711 URL: https://issues.apache.org/jira/browse/CAMEL-14711 Project: Camel Issue Type: Improvement Components: camel-rabbitmq Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.2.0 This task is to remove the Rabbit MQ Java serialization functionality (from master only) due to security reasons. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-14532. - Resolution: Fixed > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039069#comment-17039069 ] Colm O hEigeartaigh commented on CAMEL-14532: - I see there are some sourcecheck errors - I'll fix them. > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039067#comment-17039067 ] Colm O hEigeartaigh commented on CAMEL-14532: - Are you sure it's related to my merges? I don't see anything obvious that could have caused it > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039056#comment-17039056 ] Colm O hEigeartaigh commented on CAMEL-14532: - [~davsclaus] Thanks, that's done. > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039042#comment-17039042 ] Colm O hEigeartaigh commented on CAMEL-14532: - [~acosentino] - It's merged to master now. Just a question though - I added two configuration options to [https://github.com/apache/camel/blob/ffda93ae1dd43d18a88b498c4c073f8f0f58b1be/components/camel-snakeyaml/src/main/java/org/apache/camel/component/snakeyaml/SnakeYAMLDataFormat.java] However I don't see them added to the adoc after I run mvn clean install. What am I missing here? > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038995#comment-17038995 ] Colm O hEigeartaigh commented on CAMEL-14532: - I am literally about to merge it - is there still time? > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-14532: Fix Version/s: 3.1.0 > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-14532: Description: There is an issue with this library that can cause endless recursion. A PR has been submitted upstream, however we can work around it in Camel until (if) it is applied. (was: There is an issue with this library that can cause endless recursion. The snakeyaml project will not fix it and so the Camel team has decided to deprecate this module and remove it from 3.1 onwards.) > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. A PR > has been submitted upstream, however we can work around it in Camel until > (if) it is applied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14532) Fix issues with camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-14532: Summary: Fix issues with camel-snakeyaml (was: Deprecate camel-snakeyaml ) > Fix issues with camel-snakeyaml > > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. > The snakeyaml project will not fix it and so the Camel team has decided to > deprecate this module and remove it from 3.1 onwards. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14532) Deprecate camel-snakeyaml
[ https://issues.apache.org/jira/browse/CAMEL-14532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned CAMEL-14532: --- Assignee: Colm O hEigeartaigh > Deprecate camel-snakeyaml > -- > > Key: CAMEL-14532 > URL: https://issues.apache.org/jira/browse/CAMEL-14532 > Project: Camel > Issue Type: Task > Components: camel-snakeyaml >Reporter: Claus Ibsen >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.2, 2.25.1 > > > There is an issue with this library that can cause endless recursion. > The snakeyaml project will not fix it and so the Camel team has decided to > deprecate this module and remove it from 3.1 onwards. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14477) camel-netty - Disable object serialization
[ https://issues.apache.org/jira/browse/CAMEL-14477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-14477. - Resolution: Fixed > camel-netty - Disable object serialization > -- > > Key: CAMEL-14477 > URL: https://issues.apache.org/jira/browse/CAMEL-14477 > Project: Camel > Issue Type: Improvement > Components: camel-netty >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.1.0, 3.0.2, 2.25.1 > > Time Spent: 20m > Remaining Estimate: 0h > > For the camel-netty component, we should disallow object serialization by > default, by removing the object encoders/decoders. If the user really wants > object serialization, they can configure custom encoders/decoders. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14477) Disable object serialization
Colm O hEigeartaigh created CAMEL-14477: --- Summary: Disable object serialization Key: CAMEL-14477 URL: https://issues.apache.org/jira/browse/CAMEL-14477 Project: Camel Issue Type: Improvement Components: camel-netty Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.1.0, 3.0.2, 2.25.1 For the camel-netty component, we should disallow object serialization by default, by removing the object encoders/decoders. If the user really wants object serialization, they can configure custom encoders/decoders. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14230) Disable RC4 and MD5 TLS ciphersuites by default
[ https://issues.apache.org/jira/browse/CAMEL-14230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-14230. - Resolution: Fixed > Disable RC4 and MD5 TLS ciphersuites by default > --- > > Key: CAMEL-14230 > URL: https://issues.apache.org/jira/browse/CAMEL-14230 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.1 > > > This task is to disable RC4 and MD5 TLS ciphersuites by default. They're > likely disabled by the JVM anyway so this should have no real impact. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14230) Disable RC4 and MD5 TLS ciphersuites by default
Colm O hEigeartaigh created CAMEL-14230: --- Summary: Disable RC4 and MD5 TLS ciphersuites by default Key: CAMEL-14230 URL: https://issues.apache.org/jira/browse/CAMEL-14230 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.0.1 This task is to disable RC4 and MD5 TLS ciphersuites by default. They're likely disabled by the JVM anyway so this should have no real impact. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14160) Update default algorithms in the Crypto Component/DataFormat
[ https://issues.apache.org/jira/browse/CAMEL-14160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-14160. - Resolution: Fixed > Update default algorithms in the Crypto Component/DataFormat > > > Key: CAMEL-14160 > URL: https://issues.apache.org/jira/browse/CAMEL-14160 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0 > > > This task is to update the default algorithms in the Crypto > Component/DataFormat. For the Crypto Component, the default algorithm will > change from SHA1WithDSA -> SHA256withRSA. For the Crypto DataFormat, the > default algorithm will change from "DES/CBC/PKCS5Padding" just to null, thus > forcing the client to specify a default algorithm. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14160) Update default algorithms in the Crypto Component/DataFormat
[ https://issues.apache.org/jira/browse/CAMEL-14160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-14160: Description: This task is to update the default algorithms in the Crypto Component/DataFormat. For the Crypto Component, the default algorithm will change from SHA1WithDSA -> SHA256withRSA. For the Crypto DataFormat, the default algorithm will change from "DES/CBC/PKCS5Padding" just to null, thus forcing the client to specify a default algorithm. (was: This task is to update the default algorithms in the Crypto Component/DataFormat. For the Crypto Component, the default algorithm will change from SHA1WithDSA -> SHA256withRSA. For the Crypto DataFormat, the default algorithm will change from) > Update default algorithms in the Crypto Component/DataFormat > > > Key: CAMEL-14160 > URL: https://issues.apache.org/jira/browse/CAMEL-14160 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0 > > > This task is to update the default algorithms in the Crypto > Component/DataFormat. For the Crypto Component, the default algorithm will > change from SHA1WithDSA -> SHA256withRSA. For the Crypto DataFormat, the > default algorithm will change from "DES/CBC/PKCS5Padding" just to null, thus > forcing the client to specify a default algorithm. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14161) Remove default key from camel-shiro
[ https://issues.apache.org/jira/browse/CAMEL-14161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-14161. - Resolution: Fixed > Remove default key from camel-shiro > --- > > Key: CAMEL-14161 > URL: https://issues.apache.org/jira/browse/CAMEL-14161 > Project: Camel > Issue Type: Improvement > Components: camel-shiro >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0 > > > We should remove the default encryption key from camel-shiro as it's not > secure. The user must specify an encryption key. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14161) Remove default key from camel-shiro
Colm O hEigeartaigh created CAMEL-14161: --- Summary: Remove default key from camel-shiro Key: CAMEL-14161 URL: https://issues.apache.org/jira/browse/CAMEL-14161 Project: Camel Issue Type: Improvement Components: camel-shiro Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.0.0 We should remove the default encryption key from camel-shiro as it's not secure. The user must specify an encryption key. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14157) Upgrade default signature algorithm for XML Signature to RSA-SHA256
[ https://issues.apache.org/jira/browse/CAMEL-14157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-14157. - Resolution: Fixed > Upgrade default signature algorithm for XML Signature to RSA-SHA256 > --- > > Key: CAMEL-14157 > URL: https://issues.apache.org/jira/browse/CAMEL-14157 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0 > > > For the 3.0.0 release we should update the default signature algorithm for > XML Signature from RSA-SHA1 to RSA-SHA256. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14160) Update default algorithms in the Crypto Component/DataFormat
Colm O hEigeartaigh created CAMEL-14160: --- Summary: Update default algorithms in the Crypto Component/DataFormat Key: CAMEL-14160 URL: https://issues.apache.org/jira/browse/CAMEL-14160 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.0.0 This task is to update the default algorithms in the Crypto Component/DataFormat. For the Crypto Component, the default algorithm will change from SHA1WithDSA -> SHA256withRSA. For the Crypto DataFormat, the default algorithm will change from -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14157) Upgrade default signature algorithm for XML Signature to RSA-SHA256
Colm O hEigeartaigh created CAMEL-14157: --- Summary: Upgrade default signature algorithm for XML Signature to RSA-SHA256 Key: CAMEL-14157 URL: https://issues.apache.org/jira/browse/CAMEL-14157 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.0.0 For the 3.0.0 release we should update the default signature algorithm for XML Signature from RSA-SHA1 to RSA-SHA256. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14151) Remove default key from camel-xmlsecurity XML Security Data Format and update the default encryption algorithm
[ https://issues.apache.org/jira/browse/CAMEL-14151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-14151. - Resolution: Fixed > Remove default key from camel-xmlsecurity XML Security Data Format and update > the default encryption algorithm > -- > > Key: CAMEL-14151 > URL: https://issues.apache.org/jira/browse/CAMEL-14151 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0 > > > For Camel 3.0.0, we should use the opportunity to get rid of the insecure > default encryption key for the XML Security component. In addition, update > the default encryption algorithm from 3DES to AES-256-GCM. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14151) Remove default key from camel-xmlsecurity XML Security Data Format and update the default encryption algorithm
Colm O hEigeartaigh created CAMEL-14151: --- Summary: Remove default key from camel-xmlsecurity XML Security Data Format and update the default encryption algorithm Key: CAMEL-14151 URL: https://issues.apache.org/jira/browse/CAMEL-14151 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.0.0 For Camel 3.0.0, we should use the opportunity to get rid of the insecure default encryption key for the XML Security component. In addition, update the default encryption algorithm from 3DES to AES-256-GCM. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13886) camel-servlet + camel-http4 with null body causes "Stream closed" IOException
[
https://issues.apache.org/jira/browse/CAMEL-13886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16912281#comment-16912281
]
Colm O hEigeartaigh commented on CAMEL-13886:
-
[~tadayosi] - looks like this issues caused some test failures on 2.x in
camel-servlet + camel-jetty:
https://builds.apache.org/job/Camel/job/camel-2.x/230/#showFailuresLink
> camel-servlet + camel-http4 with null body causes "Stream closed" IOException
> -
>
> Key: CAMEL-13886
> URL: https://issues.apache.org/jira/browse/CAMEL-13886
> Project: Camel
> Issue Type: Bug
> Components: camel-http-common, camel-http4, camel-servlet
>Affects Versions: 2.25.0, 3.0.0.M4
>Reporter: Tadayoshi Sato
>Assignee: Tadayoshi Sato
>Priority: Major
> Fix For: 2.25.0, 3.0.0.RC1
>
>
> A Rest DSL route like the following causes {{java.io.IOException: Stream
> closed}} when invoked at http://localhost:8000/test/proxy:
> {code:java}
> rest("/test")
> .get("/proxy")
> .to("direct:callInternalRestService");
> from("direct:callInternalRestService")
> .setHeader(Exchange.HTTP_METHOD, constant("DELETE"))
> //.setBody(constant("")) // workaround for null body and
> http4 component
> .to("http4://localhost:9000/test?bridgeEndpoint=true")
> .log("${body}");
> {code}
> The error stacktrace:
> {code}
> Caused by: java.io.IOException: Stream closed
> at org.apache.catalina.connector.InputBuffer.read(InputBuffer.java:372)
> at
> org.apache.catalina.connector.CoyoteInputStream.read(CoyoteInputStream.java:156)
> at org.apache.camel.util.IOHelper.copy(IOHelper.java:202)
> at org.apache.camel.util.IOHelper.copy(IOHelper.java:174)
> at org.apache.camel.util.IOHelper.copyAndCloseInput(IOHelper.java:234)
> at org.apache.camel.util.IOHelper.copyAndCloseInput(IOHelper.java:230)
> at
> org.apache.camel.http.common.HttpHelper.readResponseBodyFromInputStream(HttpHelper.java:245)
> at
> org.apache.camel.http.common.HttpHelper.readRequestBodyFromServletRequest(HttpHelper.java:196)
> at
> org.apache.camel.http.common.DefaultHttpBinding.parseBody(DefaultHttpBinding.java:577)
> at
> org.apache.camel.http.common.HttpMessage.createBody(HttpMessage.java:78)
> ... 54 common frames omitted
> {code}
> This seems to happen only when Tomcat is used as the container with Spring
> Boot. Undertow doesn't cause such an issue.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Resolved] (CAMEL-13726) Add support for PKCS8 keys and encrypted PKCS8 keys
[ https://issues.apache.org/jira/browse/CAMEL-13726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-13726. - Resolution: Fixed > Add support for PKCS8 keys and encrypted PKCS8 keys > --- > > Key: CAMEL-13726 > URL: https://issues.apache.org/jira/browse/CAMEL-13726 > Project: Camel > Issue Type: Improvement > Components: camel-ssh >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.25.0 > > > Add support for PKCS8 keys and encrypted PKCS8 keys. At the moment, the SSH > component only supports PKCS1 keys. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13726) Add support for PKCS8 keys and encrypted PKCS8 keys
Colm O hEigeartaigh created CAMEL-13726: --- Summary: Add support for PKCS8 keys and encrypted PKCS8 keys Key: CAMEL-13726 URL: https://issues.apache.org/jira/browse/CAMEL-13726 Project: Camel Issue Type: Improvement Components: camel-ssh Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.0.0, 2.25.0 Add support for PKCS8 keys and encrypted PKCS8 keys. At the moment, the SSH component only supports PKCS1 keys. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13715) Remove dummyTrustManager from camel-mail
[ https://issues.apache.org/jira/browse/CAMEL-13715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-13715. - Resolution: Fixed > Remove dummyTrustManager from camel-mail > > > Key: CAMEL-13715 > URL: https://issues.apache.org/jira/browse/CAMEL-13715 > Project: Camel > Issue Type: Improvement > Components: camel-mail >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0 > > > The camel-mail has a "*dummyTrustManager*" boolean configuration switch that > disables all TLS verification. This is not a good idea as it can easily be > set to false in development and not changed thereafter. Better instead to > force the user to set the truststore appropriately. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13715) Remove dummyTrustManager from camel-mail
Colm O hEigeartaigh created CAMEL-13715: --- Summary: Remove dummyTrustManager from camel-mail Key: CAMEL-13715 URL: https://issues.apache.org/jira/browse/CAMEL-13715 Project: Camel Issue Type: Improvement Components: camel-mail Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.0.0 The camel-mail has a "*dummyTrustManager*" boolean configuration switch that disables all TLS verification. This is not a good idea as it can easily be set to false in development and not changed thereafter. Better instead to force the user to set the truststore appropriately. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13692) Don't use ssh-rsa as the default keytype for client keys
[ https://issues.apache.org/jira/browse/CAMEL-13692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-13692. - Resolution: Fixed > Don't use ssh-rsa as the default keytype for client keys > > > Key: CAMEL-13692 > URL: https://issues.apache.org/jira/browse/CAMEL-13692 > Project: Camel > Issue Type: Improvement > Components: camel-ssh >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.25.0 > > > By default, Camel SSH enforces that ssh-rsa is used as the default key for > clients. Instead we should just use whatever key is provided by the client, > and only enforce the type if the client specifies it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13692) Don't use ssh-rsa as the default keytype for client keys
Colm O hEigeartaigh created CAMEL-13692: --- Summary: Don't use ssh-rsa as the default keytype for client keys Key: CAMEL-13692 URL: https://issues.apache.org/jira/browse/CAMEL-13692 Project: Camel Issue Type: Improvement Components: camel-ssh Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.0.0, 2.25.0 By default, Camel SSH enforces that ssh-rsa is used as the default key for clients. Instead we should just use whatever key is provided by the client, and only enforce the type if the client specifies it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13638) camel-salesforce - Lookups to polymorphic relationship fields must include an attributes object with a type property
[
https://issues.apache.org/jira/browse/CAMEL-13638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866451#comment-16866451
]
Colm O hEigeartaigh commented on CAMEL-13638:
-
[~aldettinger] - I backported the fix to camel-2.x, as it was causing a test
failure there as well.
> camel-salesforce - Lookups to polymorphic relationship fields must include an
> attributes object with a type property
>
>
> Key: CAMEL-13638
> URL: https://issues.apache.org/jira/browse/CAMEL-13638
> Project: Camel
> Issue Type: Improvement
> Components: camel-salesforce
>Affects Versions: 2.24.0, 3.0.0-M2
>Reporter: Jeremy Ross
>Priority: Major
> Fix For: 2.24.1, 3.0.0.M4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When referencing a related record that is a polymorphic lookup, the JSON must
> include an {{attributes}} object with a {{type}} property indicating which
> type of Object is being referenced.
> E.g.:
> {code:json}
> {
> "Description": "Contact HR for further information",
> "Status": "Completed",
> "Who": {
> "attributes": {
> "type": "Contact"
> },
> "External_Id_Field__c": "cfcec54d-5d77-4ffa-a2ec-7fa2ce0e9616"
> },
> "Subject": "Comment"
> }
> {code}
> This {{attributes}} object is optional for non-polymorphic lookups, so no
> harm in including it in all lookups.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-13650) Properties component - loadProperties to return properties in order
[ https://issues.apache.org/jira/browse/CAMEL-13650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865760#comment-16865760 ] Colm O hEigeartaigh commented on CAMEL-13650: - [~davsclaus] - looks like this could have caused the failing tests on master with JDK 11? https://builds.apache.org/job/Camel%20JDK11/job/master/187/ > Properties component - loadProperties to return properties in order > --- > > Key: CAMEL-13650 > URL: https://issues.apache.org/jira/browse/CAMEL-13650 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.0.0, 3.0.0.M4 > > > The API > Properties loadProperties(); > Properties loadProperties(String... locations); > But the Properties is a Hashtable that is unordered, but it would be better > if we could get this as Map so we can use LinkedHashMap so they are in order. > This would work better with the order the end users may define in their > application.properties files etc > camel.component.jms.configuration.connectionFactory=#class:org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory > camel.component.jms.configuration.connectionFactory.brokerUrl=localhost:61616 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13563) Update Jetty to 9.4.18 + fix client authentication issues
[ https://issues.apache.org/jira/browse/CAMEL-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-13563. - Resolution: Fixed > Update Jetty to 9.4.18 + fix client authentication issues > - > > Key: CAMEL-13563 > URL: https://issues.apache.org/jira/browse/CAMEL-13563 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.25.0, 3.0.0.M4 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to update Jetty to 9.4.18, as there are several CVEs associated > with the versions under this that we are picking up. > In addition, a number of components have client authentication issues due to > the upgrade to Jetty 9.4.15. I'll fix this as part of this upgrade + add > tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13563) Update Jetty to 9.4.18 + fix client authentication issues
[ https://issues.apache.org/jira/browse/CAMEL-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-13563: Fix Version/s: (was: 2.24.1) (was: 2.23.3) 2.25.0 > Update Jetty to 9.4.18 + fix client authentication issues > - > > Key: CAMEL-13563 > URL: https://issues.apache.org/jira/browse/CAMEL-13563 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.25.0, 3.0.0.M4 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to update Jetty to 9.4.18, as there are several CVEs associated > with the versions under this that we are picking up. > In addition, a number of components have client authentication issues due to > the upgrade to Jetty 9.4.15. I'll fix this as part of this upgrade + add > tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13563) Update Jetty to 9.4.18 + fix client authentication issues
[ https://issues.apache.org/jira/browse/CAMEL-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861039#comment-16861039 ] Colm O hEigeartaigh commented on CAMEL-13563: - [~acosentino] By "I think it's safe to do this on 2.x" - do you mean only camel-2.x branch, or also for 2.24.1 + 2.23.3? > Update Jetty to 9.4.18 + fix client authentication issues > - > > Key: CAMEL-13563 > URL: https://issues.apache.org/jira/browse/CAMEL-13563 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.23.3, 2.24.1, 3.0.0.M4 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to update Jetty to 9.4.18, as there are several CVEs associated > with the versions under this that we are picking up. > In addition, a number of components have client authentication issues due to > the upgrade to Jetty 9.4.15. I'll fix this as part of this upgrade + add > tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13563) Update Jetty to 9.4.18 + fix client authentication issues
[ https://issues.apache.org/jira/browse/CAMEL-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861006#comment-16861006 ] Colm O hEigeartaigh commented on CAMEL-13563: - [~acosentino] I think the Jetty upgrade could be backported to the camel-2.x branch. Then I can merge the fixes that relate to client authentication only back to the older branches. WDYT? > Update Jetty to 9.4.18 + fix client authentication issues > - > > Key: CAMEL-13563 > URL: https://issues.apache.org/jira/browse/CAMEL-13563 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.23.3, 2.24.1, 3.0.0.M4 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to update Jetty to 9.4.18, as there are several CVEs associated > with the versions under this that we are picking up. > In addition, a number of components have client authentication issues due to > the upgrade to Jetty 9.4.15. I'll fix this as part of this upgrade + add > tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13471) Support TCP + TLS in Camel CoAP
[ https://issues.apache.org/jira/browse/CAMEL-13471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848821#comment-16848821 ] Colm O hEigeartaigh commented on CAMEL-13471: - The problem is that the scheme includes the + sign, so the URI scheme as per the spec is "coaps+tcp"...from the spec: * The "coap+tcp" URI scheme for CoAP over TCP. * The "coaps+tcp" URI scheme for CoAP over TCP secured by TLS. * The "coap+ws" URI scheme for CoAP over WebSockets. * The "coaps+ws" URI scheme for CoAP over WebSockets secured by TLS. > Support TCP + TLS in Camel CoAP > --- > > Key: CAMEL-13471 > URL: https://issues.apache.org/jira/browse/CAMEL-13471 > Project: Camel > Issue Type: Improvement > Components: camel-coap >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 3.0.0-M3, 2.25.0 > > > This task is to support TCP + TLS in Camel CoAP as per > https://tools.ietf.org/html/rfc8323 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13471) Support TCP + TLS in Camel CoAP
[ https://issues.apache.org/jira/browse/CAMEL-13471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-13471: Fix Version/s: 2.25.0 > Support TCP + TLS in Camel CoAP > --- > > Key: CAMEL-13471 > URL: https://issues.apache.org/jira/browse/CAMEL-13471 > Project: Camel > Issue Type: Improvement > Components: camel-coap >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 3.0.0-M3, 2.25.0 > > > This task is to support TCP + TLS in Camel CoAP as per > https://tools.ietf.org/html/rfc8323 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13402) Update to Californium 2.0.x and support DTLS
[ https://issues.apache.org/jira/browse/CAMEL-13402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-13402: Fix Version/s: 2.25.0 > Update to Californium 2.0.x and support DTLS > > > Key: CAMEL-13402 > URL: https://issues.apache.org/jira/browse/CAMEL-13402 > Project: Camel > Issue Type: Improvement > Components: camel-coap >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 3.0.0-M3, 2.25.0 > > > This task is to update to Californium 2.0.x and support DTLS in the > camel-coap component. Currently we only support plain UDP and not UDP / TLS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13563) Update Jetty to 9.4.18 + fix client authentication issues
Colm O hEigeartaigh created CAMEL-13563: --- Summary: Update Jetty to 9.4.18 + fix client authentication issues Key: CAMEL-13563 URL: https://issues.apache.org/jira/browse/CAMEL-13563 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.0.0, 2.23.3, 2.24.1 This task is to update Jetty to 9.4.18, as there are several CVEs associated with the versions under this that we are picking up. In addition, a number of components have client authentication issues due to the upgrade to Jetty 9.4.15. I'll fix this as part of this upgrade + add tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13471) Support TCP + TLS in Camel CoAP
[ https://issues.apache.org/jira/browse/CAMEL-13471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-13471. - Resolution: Fixed Fix Version/s: (was: 3.x) > Support TCP + TLS in Camel CoAP > --- > > Key: CAMEL-13471 > URL: https://issues.apache.org/jira/browse/CAMEL-13471 > Project: Camel > Issue Type: Improvement > Components: camel-coap >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 3.0.0-M3 > > > This task is to support TCP + TLS in Camel CoAP as per > https://tools.ietf.org/html/rfc8323 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13471) Support TCP + TLS in Camel CoAP
[ https://issues.apache.org/jira/browse/CAMEL-13471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-13471: Fix Version/s: 3.0.0-M3 3.x > Support TCP + TLS in Camel CoAP > --- > > Key: CAMEL-13471 > URL: https://issues.apache.org/jira/browse/CAMEL-13471 > Project: Camel > Issue Type: Improvement > Components: camel-coap >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 3.x, 3.0.0-M3 > > > This task is to support TCP + TLS in Camel CoAP as per > https://tools.ietf.org/html/rfc8323 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13471) Support TCP + TLS in Camel CoAP
Colm O hEigeartaigh created CAMEL-13471: --- Summary: Support TCP + TLS in Camel CoAP Key: CAMEL-13471 URL: https://issues.apache.org/jira/browse/CAMEL-13471 Project: Camel Issue Type: Improvement Components: camel-coap Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.0.0 This task is to support TCP + TLS in Camel CoAP as per https://tools.ietf.org/html/rfc8323 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-13402) Update to Californium 2.0.x and support DTLS
[ https://issues.apache.org/jira/browse/CAMEL-13402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815278#comment-16815278 ] Colm O hEigeartaigh commented on CAMEL-13402: - Yep I'm still working on it. I'll submit a PR for review when I'm done. > Update to Californium 2.0.x and support DTLS > > > Key: CAMEL-13402 > URL: https://issues.apache.org/jira/browse/CAMEL-13402 > Project: Camel > Issue Type: Improvement > Components: camel-coap >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0 > > > This task is to update to Californium 2.0.x and support DTLS in the > camel-coap component. Currently we only support plain UDP and not UDP / TLS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13402) Update to Californium 2.0.x and support DTLS
Colm O hEigeartaigh created CAMEL-13402: --- Summary: Update to Californium 2.0.x and support DTLS Key: CAMEL-13402 URL: https://issues.apache.org/jira/browse/CAMEL-13402 Project: Camel Issue Type: Improvement Components: camel-coap Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.0.0 This task is to update to Californium 2.0.x and support DTLS in the camel-coap component. Currently we only support plain UDP and not UDP / TLS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (CAMEL-13153) camel-mail - Strip newlines from exchange headers
[ https://issues.apache.org/jira/browse/CAMEL-13153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-13153. - Resolution: Fixed > camel-mail - Strip newlines from exchange headers > - > > Key: CAMEL-13153 > URL: https://issues.apache.org/jira/browse/CAMEL-13153 > Project: Camel > Issue Type: Task > Components: camel-mail >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.0, 2.23.2, 2.24.0, 2.22.4 > > Time Spent: 20m > Remaining Estimate: 0h > > We should strip newlines from exchange headers that are written out by > camel-mail. > PR: https://github.com/apache/camel/pull/2743 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (CAMEL-13153) Strip newlines from exchange headers
[ https://issues.apache.org/jira/browse/CAMEL-13153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-13153: Description: We should strip newlines from exchange headers that are written out by camel-mail. PR: https://github.com/apache/camel/pull/2743 was:We should strip newlines from exchange headers that are written out by camel-mail. > Strip newlines from exchange headers > > > Key: CAMEL-13153 > URL: https://issues.apache.org/jira/browse/CAMEL-13153 > Project: Camel > Issue Type: Task > Components: camel-mail >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.21.5, 2.23.2, 2.24.0, 2.22.4 > > Time Spent: 10m > Remaining Estimate: 0h > > We should strip newlines from exchange headers that are written out by > camel-mail. > PR: https://github.com/apache/camel/pull/2743 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (CAMEL-13153) Strip newlines from exchange headers
Colm O hEigeartaigh created CAMEL-13153: --- Summary: Strip newlines from exchange headers Key: CAMEL-13153 URL: https://issues.apache.org/jira/browse/CAMEL-13153 Project: Camel Issue Type: Task Components: camel-mail Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 2.21.5, 2.23.2, 2.24.0, 2.22.4 We should strip newlines from exchange headers that are written out by camel-mail. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12504) Test Apache Camel on Java 9 and newer
[
https://issues.apache.org/jira/browse/CAMEL-12504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16531215#comment-16531215
]
Colm O hEigeartaigh commented on CAMEL-12504:
-
CustomSchemaFactoryFeatureTest is failing on Java 10. It looks like this test
never worked as expected:
String jdkVendor = System.getProperty("java.vm.vendor");
if (jdkVendor != null && (jdkVendor.indexOf("Oracle") > 0 ||
jdkVendor.indexOf("Sun") > 0)) {
fail("Expect exception here");
}
I think the intention here is to "fail" with the Oracle JDK if an exception is
not thrown - but jdkVendor.indexOf("Oracle") returns 0 for Java 7/8, so the
test never actually failed (no exception is thrown). It returns "1" for Java
10, as the Java vendor is now enclosed in quotation marks.
> Test Apache Camel on Java 9 and newer
> -
>
> Key: CAMEL-12504
> URL: https://issues.apache.org/jira/browse/CAMEL-12504
> Project: Camel
> Issue Type: Test
> Components: build system
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: 2.23.0
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12504) Test Apache Camel on Java 9 and newer
[ https://issues.apache.org/jira/browse/CAMEL-12504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16531155#comment-16531155 ] Colm O hEigeartaigh commented on CAMEL-12504: - I pushed a fix for the failing RestDslXmlGeneratorTest on Java 9. > Test Apache Camel on Java 9 and newer > - > > Key: CAMEL-12504 > URL: https://issues.apache.org/jira/browse/CAMEL-12504 > Project: Camel > Issue Type: Test > Components: build system >Reporter: Luca Burgazzoli >Priority: Major > Fix For: 2.23.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CAMEL-12574) PGPDataFormat: java.lang.NoSuchMethodError: org.bouncycastle.openpgp.PGPPublicKeyRingCollection
[
https://issues.apache.org/jira/browse/CAMEL-12574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511433#comment-16511433
]
Colm O hEigeartaigh commented on CAMEL-12574:
-
Can you verify that you're getting that error with the sample project attached
to this JIRA? Do you see any other versions of BouncyCastle when you do:
mvn dependency:tree | grep bouncy
[INFO] | +- org.bouncycastle:bcpg-jdk15on:jar:1.57:compile
[INFO] | +- org.bouncycastle:bcprov-jdk15on:jar:1.57:compile
What version of Maven are you using? Try the latest 3.5.3. Also try upgrading
your JDK to 1.8.0_171/172.
> PGPDataFormat: java.lang.NoSuchMethodError:
> org.bouncycastle.openpgp.PGPPublicKeyRingCollection
> ---
>
> Key: CAMEL-12574
> URL: https://issues.apache.org/jira/browse/CAMEL-12574
> Project: Camel
> Issue Type: Bug
> Components: camel-crypto
>Affects Versions: 2.21.0
>Reporter: Ronak Patel
>Priority: Major
> Labels: crypto, pgp
> Attachments: camel_pgp.zip, test.out
>
>
> *Camel Version:* 2.21.0 (Springboot)
> *JDK version:* 1.8.0_121
> *unit test:* [^camel_pgp.zip]
> ^*more details:* [on
> StackOverflow|https://stackoverflow.com/questions/50610962/camel-2-21-0-pgp-encryption-not-working]^
> *issue:*
> {code:java}
> Caused by: java.lang.NoSuchMethodError:
> org.bouncycastle.openpgp.PGPPublicKeyRingCollection.(Ljava/io/InputStream;Lorg/bouncycastle/openpgp/operator/KeyFingerPrintCalculator;)V
> at
> org.apache.camel.converter.crypto.PGPDataFormatUtil.findPublicKeys(PGPDataFormatUtil.java:204)
> at
> org.apache.camel.converter.crypto.PGPDataFormatUtil.findPublicKeys(PGPDataFormatUtil.java:96)
> at
> org.apache.camel.converter.crypto.PGPDataFormat.getEncryptionKeys(PGPDataFormat.java:235)
> at
> org.apache.camel.converter.crypto.PGPKeyAccessDataFormat.marshal(PGPKeyAccessDataFormat.java:222)
> at
> org.apache.camel.processor.MarshalProcessor.process(MarshalProcessor.java:69)
> ... 17 common frames omitted{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12574) PGPDataFormat: java.lang.NoSuchMethodError: org.bouncycastle.openpgp.PGPPublicKeyRingCollection
[
https://issues.apache.org/jira/browse/CAMEL-12574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511382#comment-16511382
]
Colm O hEigeartaigh commented on CAMEL-12574:
-
The tests fail for me with "mvn clean install" but there is no error about
'PGPPublicKeyRingCollection' in the output.
> PGPDataFormat: java.lang.NoSuchMethodError:
> org.bouncycastle.openpgp.PGPPublicKeyRingCollection
> ---
>
> Key: CAMEL-12574
> URL: https://issues.apache.org/jira/browse/CAMEL-12574
> Project: Camel
> Issue Type: Bug
> Components: camel-crypto
>Affects Versions: 2.21.0
>Reporter: Ronak Patel
>Priority: Major
> Labels: crypto, pgp
> Attachments: camel_pgp.zip
>
>
> *Camel Version:* 2.21.0 (Springboot)
> *JDK version:* 1.8.0_121
> *unit test:* [^camel_pgp.zip]
> ^*more details:* [on
> StackOverflow|https://stackoverflow.com/questions/50610962/camel-2-21-0-pgp-encryption-not-working]^
> *issue:*
> {code:java}
> Caused by: java.lang.NoSuchMethodError:
> org.bouncycastle.openpgp.PGPPublicKeyRingCollection.(Ljava/io/InputStream;Lorg/bouncycastle/openpgp/operator/KeyFingerPrintCalculator;)V
> at
> org.apache.camel.converter.crypto.PGPDataFormatUtil.findPublicKeys(PGPDataFormatUtil.java:204)
> at
> org.apache.camel.converter.crypto.PGPDataFormatUtil.findPublicKeys(PGPDataFormatUtil.java:96)
> at
> org.apache.camel.converter.crypto.PGPDataFormat.getEncryptionKeys(PGPDataFormat.java:235)
> at
> org.apache.camel.converter.crypto.PGPKeyAccessDataFormat.marshal(PGPKeyAccessDataFormat.java:222)
> at
> org.apache.camel.processor.MarshalProcessor.process(MarshalProcessor.java:69)
> ... 17 common frames omitted{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12574) PGPDataFormat: java.lang.NoSuchMethodError: org.bouncycastle.openpgp.PGPPublicKeyRingCollection
[
https://issues.apache.org/jira/browse/CAMEL-12574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511289#comment-16511289
]
Colm O hEigeartaigh commented on CAMEL-12574:
-
Please update the attached test-case so that we can simply unzip and run the
tests with the correct Camel version etc.
> PGPDataFormat: java.lang.NoSuchMethodError:
> org.bouncycastle.openpgp.PGPPublicKeyRingCollection
> ---
>
> Key: CAMEL-12574
> URL: https://issues.apache.org/jira/browse/CAMEL-12574
> Project: Camel
> Issue Type: Bug
> Components: camel-crypto
>Affects Versions: 2.21.0
>Reporter: Ronak Patel
>Priority: Major
> Labels: crypto, pgp
> Attachments: junitTest.zip
>
>
> *Camel Version:* 2.21.0 (Springboot)
> *JDK version:* 1.8.0_121
> *unit test:* [^junitTest.zip]
> ^*more details:* [on
> StackOverflow|https://stackoverflow.com/questions/50610962/camel-2-21-0-pgp-encryption-not-working]^
> *issue:*
> {code:java}
> Caused by: java.lang.NoSuchMethodError:
> org.bouncycastle.openpgp.PGPPublicKeyRingCollection.(Ljava/io/InputStream;Lorg/bouncycastle/openpgp/operator/KeyFingerPrintCalculator;)V
> at
> org.apache.camel.converter.crypto.PGPDataFormatUtil.findPublicKeys(PGPDataFormatUtil.java:204)
> at
> org.apache.camel.converter.crypto.PGPDataFormatUtil.findPublicKeys(PGPDataFormatUtil.java:96)
> at
> org.apache.camel.converter.crypto.PGPDataFormat.getEncryptionKeys(PGPDataFormat.java:235)
> at
> org.apache.camel.converter.crypto.PGPKeyAccessDataFormat.marshal(PGPKeyAccessDataFormat.java:222)
> at
> org.apache.camel.processor.MarshalProcessor.process(MarshalProcessor.java:69)
> ... 17 common frames omitted{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CAMEL-12262) DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
[
https://issues.apache.org/jira/browse/CAMEL-12262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363861#comment-16363861
]
Colm O hEigeartaigh commented on CAMEL-12262:
-
Hi [~davsclaus],
I disagree that the documentation states that 3DES is excluded - the filter
given is "{{.*_DES_.*}}" which only applies to DES. It would be ".*_3DES_.*" if
it applied to 3DES.
I don't think we need to exclude 3DES as well, it's still considered secure.
For example it is on the default "enabled" cipher suite algorithms in Java 8:
[https://docs.oracle.com/javase/8/docs/technotes/guides/security/SunProviders.html]
However, I think maybe we could change how we filter algorithms in general
starting with the next major release. CXF only applies the default "excludes"
if there is a corresponding "includes" filter. If there are no filters it just
uses the JVM defaults, which already exclude the weak algorithms by default in
recent JDK versions.
Colm.
> DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE Incorrect
> --
>
> Key: CAMEL-12262
> URL: https://issues.apache.org/jira/browse/CAMEL-12262
> Project: Camel
> Issue Type: Task
> Components: documentation
>Reporter: Lyubomir
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 2.21.0
>
>
> The [official
> documentation|http://camel.apache.org/camel-configuration-utilities.html]
> states the default cipher suites exclude filters are:
> {code:java}
> .*NULL.*
> .*anon.*
> .*DES.* Camel 2.15.4 =>Means 3DES **is** excluded
> .*EXPORT.* Camel 2.15.4
> {code}
> The default cipher suite exclude filter declared is:
> {code:java}
> /camel-core/src/main/java/org/apache/camel/util/jsse/BaseSSLContextParameters.java
> {code}
> {code:java}
> protected static final List DEFAULT_CIPHER_SUITES_FILTER_EXCLUDE =
> Collections.unmodifiableList(Arrays.asList(".*_NULL_.*",
> ".*_anon_.*", ".*_EXPORT_.*", ".*_DES_.*"));
> {code}
> According to the documentation 3DES will be excluded by default. Based on the
> code only DES will be excluded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CAMEL-8045) Not possible to load a public key from a a PrivateKeyEntry in a keystore
Colm O hEigeartaigh created CAMEL-8045: -- Summary: Not possible to load a public key from a a PrivateKeyEntry in a keystore Key: CAMEL-8045 URL: https://issues.apache.org/jira/browse/CAMEL-8045 Project: Camel Issue Type: Bug Components: camel-xmlsecurity Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Priority: Minor Fix For: 2.14.1, 2.15.0, 2.13.4 It's not possible to retrieve a certificate/public-key for encryption in the camel-xmlsecurity component, if the certificate in question is stored in a PrivateKeyEntry in the keystore. This is because the truststore password is incorrectly used (instead of the keyPassword) to retrieve the key. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8045) Not possible to load a public key from a a PrivateKeyEntry in a keystore
[ https://issues.apache.org/jira/browse/CAMEL-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-8045. Resolution: Fixed Not possible to load a public key from a a PrivateKeyEntry in a keystore Key: CAMEL-8045 URL: https://issues.apache.org/jira/browse/CAMEL-8045 Project: Camel Issue Type: Bug Components: camel-xmlsecurity Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Priority: Minor Fix For: 2.14.1, 2.15.0, 2.13.4 It's not possible to retrieve a certificate/public-key for encryption in the camel-xmlsecurity component, if the certificate in question is stored in a PrivateKeyEntry in the keystore. This is because the truststore password is incorrectly used (instead of the keyPassword) to retrieve the key. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7948) Add support for more/new encryption/signature algorithms
[ https://issues.apache.org/jira/browse/CAMEL-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-7948: --- Attachment: camel-7498-revised.patch Hi Willem, See attached for a revised patch. Some of the tests failed when the JDK does not have unlimited security policies installed. Thanks, Colm. Add support for more/new encryption/signature algorithms Key: CAMEL-7948 URL: https://issues.apache.org/jira/browse/CAMEL-7948 Project: Camel Issue Type: Improvement Components: camel-xmlsecurity Reporter: Colm O hEigeartaigh Assignee: Willem Jiang Priority: Minor Attachments: camel-7498-revised.patch, camel-7948.patch See attached for a patch to support some new (to XML Security) digest algorithms such as RIPE-MD160 and SEED + CAMELLIA encryption algorithms. Also added a fairly comprehensive set of tests for different encryption/signature algorithms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7948) Add support for more/new encryption/signature algorithms
[ https://issues.apache.org/jira/browse/CAMEL-7948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-7948: --- Attachment: camel-7948.patch Add support for more/new encryption/signature algorithms Key: CAMEL-7948 URL: https://issues.apache.org/jira/browse/CAMEL-7948 Project: Camel Issue Type: Improvement Components: camel-xmlsecurity Reporter: Colm O hEigeartaigh Priority: Minor Attachments: camel-7948.patch See attached for a patch to support some new (to XML Security) digest algorithms such as RIPE-MD160 and SEED + CAMELLIA encryption algorithms. Also added a fairly comprehensive set of tests for different encryption/signature algorithms. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7895) Upgrade XML Security + BouncyCastle dependencies
[ https://issues.apache.org/jira/browse/CAMEL-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14179793#comment-14179793 ] Colm O hEigeartaigh commented on CAMEL-7895: Thanks Christian! Colm. Upgrade XML Security + BouncyCastle dependencies Key: CAMEL-7895 URL: https://issues.apache.org/jira/browse/CAMEL-7895 Project: Camel Issue Type: Improvement Components: camel-xmlsecurity Reporter: Colm O hEigeartaigh Assignee: Christian Müller Priority: Minor Fix For: 2.13.3, 2.14.1, 2.15.0 Attachments: camel-7895.patch This task is to upgrade BouncyCastle + XML Security to pick up the latest releases. The former can be applied to all branches, the latter should only be applied to 2.15 + 2.14. A patch will be attached with a test fix caused by the XML Security upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7895) Upgrade XML Security + BouncyCastle dependencies
[ https://issues.apache.org/jira/browse/CAMEL-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178469#comment-14178469 ] Colm O hEigeartaigh commented on CAMEL-7895: Hi Willem, Can the patch be applied please? Colm. Upgrade XML Security + BouncyCastle dependencies Key: CAMEL-7895 URL: https://issues.apache.org/jira/browse/CAMEL-7895 Project: Camel Issue Type: Improvement Components: camel-xmlsecurity Reporter: Colm O hEigeartaigh Assignee: Willem Jiang Priority: Minor Fix For: 2.15.0 Attachments: camel-7895.patch This task is to upgrade BouncyCastle + XML Security to pick up the latest releases. The former can be applied to all branches, the latter should only be applied to 2.15 + 2.14. A patch will be attached with a test fix caused by the XML Security upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7895) Upgrade XML Security + BouncyCastle dependencies
[ https://issues.apache.org/jira/browse/CAMEL-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14166562#comment-14166562 ] Colm O hEigeartaigh commented on CAMEL-7895: Hi Willem, Sorry, my comment wasn't very clear - the test fix is included in the patch I submitted. It's just a one-line fix for a regression in Santuario, that I've since fixed but not yet released. Colm. Upgrade XML Security + BouncyCastle dependencies Key: CAMEL-7895 URL: https://issues.apache.org/jira/browse/CAMEL-7895 Project: Camel Issue Type: Improvement Components: camel-xmlsecurity Reporter: Colm O hEigeartaigh Assignee: Willem Jiang Priority: Minor Fix For: 2.15.0 Attachments: camel-7895.patch This task is to upgrade BouncyCastle + XML Security to pick up the latest releases. The former can be applied to all branches, the latter should only be applied to 2.15 + 2.14. A patch will be attached with a test fix caused by the XML Security upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-7895) Upgrade XML Security + BouncyCastle dependencies
[ https://issues.apache.org/jira/browse/CAMEL-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-7895: --- Attachment: camel-7895.patch Upgrade XML Security + BouncyCastle dependencies Key: CAMEL-7895 URL: https://issues.apache.org/jira/browse/CAMEL-7895 Project: Camel Issue Type: Improvement Components: camel-xmlsecurity Reporter: Colm O hEigeartaigh Priority: Minor Fix For: 2.15.0 Attachments: camel-7895.patch This task is to upgrade BouncyCastle + XML Security to pick up the latest releases. The former can be applied to all branches, the latter should only be applied to 2.15 + 2.14. A patch will be attached with a test fix caused by the XML Security upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-7895) Upgrade XML Security + BouncyCastle dependencies
Colm O hEigeartaigh created CAMEL-7895: -- Summary: Upgrade XML Security + BouncyCastle dependencies Key: CAMEL-7895 URL: https://issues.apache.org/jira/browse/CAMEL-7895 Project: Camel Issue Type: Improvement Components: camel-xmlsecurity Reporter: Colm O hEigeartaigh Priority: Minor Fix For: 2.15.0 Attachments: camel-7895.patch This task is to upgrade BouncyCastle + XML Security to pick up the latest releases. The former can be applied to all branches, the latter should only be applied to 2.15 + 2.14. A patch will be attached with a test fix caused by the XML Security upgrade. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-7416) Improve WS-Security testing
[ https://issues.apache.org/jira/browse/CAMEL-7416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998811#comment-13998811 ] Colm O hEigeartaigh commented on CAMEL-7416: WSS4J is now passing with JDK 8, as are all of the WS-Security related tests in CXF. The errors in Camel only crop up when encryption is used, no idea why though. Colm. Improve WS-Security testing --- Key: CAMEL-7416 URL: https://issues.apache.org/jira/browse/CAMEL-7416 Project: Camel Issue Type: Test Components: camel-cxf Reporter: Colm O hEigeartaigh Assignee: Aki Yoshida Fix For: 2.13.2, 2.14.0 Attachments: camel-7416.patch The WS-Security testing in the camel-cxf component is a bit of a mess and only covers one use-case. Please apply the attached patch, which covers the main use-cases of Signature + Timestamp, Encryption, UsernameToken and WS-SecurityPolicy. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CAMEL-7416) Improve WS-Security testing
[ https://issues.apache.org/jira/browse/CAMEL-7416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998811#comment-13998811 ] Colm O hEigeartaigh edited comment on CAMEL-7416 at 5/15/14 2:52 PM: - WSS4J is now passing with JDK 8, as are all of the WS-Security related tests in CXF trunk. The errors in Camel only crop up when encryption is used, no idea why though. Colm. was (Author: coheigea): WSS4J is now passing with JDK 8, as are all of the WS-Security related tests in CXF. The errors in Camel only crop up when encryption is used, no idea why though. Colm. Improve WS-Security testing --- Key: CAMEL-7416 URL: https://issues.apache.org/jira/browse/CAMEL-7416 Project: Camel Issue Type: Test Components: camel-cxf Reporter: Colm O hEigeartaigh Assignee: Aki Yoshida Fix For: 2.13.2, 2.14.0 Attachments: camel-7416.patch The WS-Security testing in the camel-cxf component is a bit of a mess and only covers one use-case. Please apply the attached patch, which covers the main use-cases of Signature + Timestamp, Encryption, UsernameToken and WS-SecurityPolicy. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7416) Improve WS-Security testing
Colm O hEigeartaigh created CAMEL-7416: -- Summary: Improve WS-Security testing Key: CAMEL-7416 URL: https://issues.apache.org/jira/browse/CAMEL-7416 Project: Camel Issue Type: Test Components: camel-cxf Reporter: Colm O hEigeartaigh Fix For: 2.14.0 The WS-Security testing in the camel-cxf component is a bit of a mess and only covers one use-case. Please apply the attached patch, which covers the main use-cases of Signature + Timestamp, Encryption, UsernameToken and WS-SecurityPolicy. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7416) Improve WS-Security testing
[ https://issues.apache.org/jira/browse/CAMEL-7416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-7416: --- Attachment: camel-7416.patch Improve WS-Security testing --- Key: CAMEL-7416 URL: https://issues.apache.org/jira/browse/CAMEL-7416 Project: Camel Issue Type: Test Components: camel-cxf Reporter: Colm O hEigeartaigh Fix For: 2.14.0 Attachments: camel-7416.patch The WS-Security testing in the camel-cxf component is a bit of a mess and only covers one use-case. Please apply the attached patch, which covers the main use-cases of Signature + Timestamp, Encryption, UsernameToken and WS-SecurityPolicy. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CAMEL-7281) Add support for certAlias in SSLContextParameters
[ https://issues.apache.org/jira/browse/CAMEL-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13930259#comment-13930259 ] Colm O hEigeartaigh commented on CAMEL-7281: Documentation updated... Colm. Add support for certAlias in SSLContextParameters --- Key: CAMEL-7281 URL: https://issues.apache.org/jira/browse/CAMEL-7281 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Colm O hEigeartaigh Assignee: Claus Ibsen Fix For: 2.13.0 Attachments: camel-7281.patch, localhost-alias.ks There is no support for a certAlias type parameters in SSLContextParameters, as in CXF. This means that it's not possible to use Keystores with more than one entry for TLS. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7281) Add support for certAlias in SSLContextParameters
Colm O hEigeartaigh created CAMEL-7281: -- Summary: Add support for certAlias in SSLContextParameters Key: CAMEL-7281 URL: https://issues.apache.org/jira/browse/CAMEL-7281 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Colm O hEigeartaigh Fix For: 2.13.0 Attachments: camel-7281.patch, localhost-alias.ks There is no support for a certAlias type parameters in SSLContextParameters, as in CXF. This means that it's not possible to use Keystores with more than one entry for TLS. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7281) Add support for certAlias in SSLContextParameters
[ https://issues.apache.org/jira/browse/CAMEL-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-7281: --- Attachment: localhost-alias.ks camel-7281.patch A patch + tests for this issue. The path of the attached keystore should be: components/camel-jetty/src/test/resources/jsse/localhost-alias.ks Colm. Add support for certAlias in SSLContextParameters --- Key: CAMEL-7281 URL: https://issues.apache.org/jira/browse/CAMEL-7281 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Colm O hEigeartaigh Fix For: 2.13.0 Attachments: camel-7281.patch, localhost-alias.ks There is no support for a certAlias type parameters in SSLContextParameters, as in CXF. This means that it's not possible to use Keystores with more than one entry for TLS. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CAMEL-7274) Support roles in the camel-shiro component
Colm O hEigeartaigh created CAMEL-7274: -- Summary: Support roles in the camel-shiro component Key: CAMEL-7274 URL: https://issues.apache.org/jira/browse/CAMEL-7274 Project: Camel Issue Type: Bug Reporter: Colm O hEigeartaigh Fix For: 2.13.0 The Camel-shiro component allows the ability to perform authorization based on permissions. However, it does not allow using straight-forward roles for authorization. While using permissions is more flexible, we should also support authorization using roles. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7274) Support roles in the camel-shiro component
[ https://issues.apache.org/jira/browse/CAMEL-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-7274: --- Attachment: camel-7274.patch A patch + tests for this issue. Colm. Support roles in the camel-shiro component -- Key: CAMEL-7274 URL: https://issues.apache.org/jira/browse/CAMEL-7274 Project: Camel Issue Type: Bug Reporter: Colm O hEigeartaigh Fix For: 2.13.0 Attachments: camel-7274.patch The Camel-shiro component allows the ability to perform authorization based on permissions. However, it does not allow using straight-forward roles for authorization. While using permissions is more flexible, we should also support authorization using roles. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CAMEL-7104) Add support for all permissions for authorization in camel-shiro
[ https://issues.apache.org/jira/browse/CAMEL-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated CAMEL-7104: --- Attachment: camel-7104.patch A patch for this issue. Colm. Add support for all permissions for authorization in camel-shiro -- Key: CAMEL-7104 URL: https://issues.apache.org/jira/browse/CAMEL-7104 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Priority: Minor Fix For: 2.13.0 Attachments: camel-7104.patch Currently, the ShiroSecurityPolicy takes a List of Shiro Permission objects for authorization. Authorization succeeds if any of the permissions match that of the current user. However, it's not possible to support requiring all of the permissions, expect via the permission wildcard syntax, which may not be convenient for every circumstance. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
