[jira] [Closed] (CAMEL-19856) NoopHostnameVerifier seems to not working any longer
[
https://issues.apache.org/jira/browse/CAMEL-19856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas closed CAMEL-19856.
-
Resolution: Information Provided
Works as expected.
> NoopHostnameVerifier seems to not working any longer
>
>
> Key: CAMEL-19856
> URL: https://issues.apache.org/jira/browse/CAMEL-19856
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 3.20.2
>Reporter: Gerald Kallas
>Priority: Minor
>
> we had a code (XML DSL) that was already working to skip SSL hostname
> validation like
> {code:java}
> class="org.apache.http.conn.ssl.NoopHostnameVerifier"/>
> ...
> uri='https://server/api/v1/entity/integrationservice/delta?x509HostnameVerifier=noopHostnameVerifier'/>{code}
> It's not working anymore, getting
>
> {code:java}
> javax.net.ssl.SSLHandshakeException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target {code}
> I tried also
>
> {code:java}
> uri='https://server/api/v1/entity/integrationservice/delta?x509HostnameVerifier=#noopHostnameVerifier'/>{code}
> same error.
>
> The underlying Java (within a Docker containe) is
>
> {code:java}
> openjdk version "11.0.11" 2021-04-20 OpenJDK Runtime Environment
> AdoptOpenJDK-11.0.11+9 (build 11.0.11+9) OpenJDK 64-Bit Server VM
> AdoptOpenJDK-11.0.11+9 (build 11.0.11+9, mixed mode){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19856) NoopHostnameVerifier seems to not working any longer
[
https://issues.apache.org/jira/browse/CAMEL-19856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1177#comment-1177
]
Gerald Kallas commented on CAMEL-19856:
---
Former we did work with Camel 3.4.4. There was a truststore defined and filled
at Karaf level, containing the server certificate.
I think now it's more clear and the ticket can be closed.
Tx Karen.
> NoopHostnameVerifier seems to not working any longer
>
>
> Key: CAMEL-19856
> URL: https://issues.apache.org/jira/browse/CAMEL-19856
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 3.20.2
>Reporter: Gerald Kallas
>Priority: Minor
>
> we had a code (XML DSL) that was already working to skip SSL hostname
> validation like
> {code:java}
> class="org.apache.http.conn.ssl.NoopHostnameVerifier"/>
> ...
> uri='https://server/api/v1/entity/integrationservice/delta?x509HostnameVerifier=noopHostnameVerifier'/>{code}
> It's not working anymore, getting
>
> {code:java}
> javax.net.ssl.SSLHandshakeException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target {code}
> I tried also
>
> {code:java}
> uri='https://server/api/v1/entity/integrationservice/delta?x509HostnameVerifier=#noopHostnameVerifier'/>{code}
> same error.
>
> The underlying Java (within a Docker containe) is
>
> {code:java}
> openjdk version "11.0.11" 2021-04-20 OpenJDK Runtime Environment
> AdoptOpenJDK-11.0.11+9 (build 11.0.11+9) OpenJDK 64-Bit Server VM
> AdoptOpenJDK-11.0.11+9 (build 11.0.11+9, mixed mode){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-19856) NoopHostnameVerifier seems to not working any longer
[
https://issues.apache.org/jira/browse/CAMEL-19856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776578#comment-17776578
]
Gerald Kallas edited comment on CAMEL-19856 at 10/18/23 9:44 AM:
-
Find attached the DEBUG log
{code:java}
2023-10-18T09:34:00,433 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #8 -
timer://isp.route.system.deployment.service.scheduler |
SSLConnectionSocketFactory | 152 - org.apache.httpcomponents.httpclient -
4.5.13 | Connecting socket to
xxx.eu-central-1.compute.amazonaws.com/10.0.0.6:8446 with timeout 0
2023-10-18T09:34:00,435 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #8 -
timer://isp.route.system.deployment.service.scheduler |
SSLConnectionSocketFactory | 152 - org.apache.httpcomponents.httpclient -
4.5.13 | Enabled protocols: [TLSv1.3, TLSv1.2]
2023-10-18T09:34:00,436 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #8 -
timer://isp.route.system.deployment.service.scheduler |
SSLConnectionSocketFactory | 152 - org.apache.httpcomponents.httpclient -
4.5.13 | Enabled cipher suites:[TLS_AES_128_GCM_SHA256, TLS_AES_256_GCM_SHA384,
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384,
TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,
TLS_DHE_DSS_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256,
TLS_ECDH_RS
2023-10-18T09:34:00,436 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #8 -
timer://isp.route.system.deployment.service.scheduler |
SSLConnectionSocketFactory | 152 - org.apache.httpcomponents.httpclient -
4.5.13 | Starting handshake
2023-10-18T09:34:00,478 | ERROR | Camel
(isp.route.system.deployment.service.scheduler) thread #8 -
timer://isp.route.system.deployment.service.scheduler | DefaultErrorHandler
| 91 - org.apache.camel.camel-core-reifier - 3.20.2 | Failed delivery
for (MessageId: 96246179F423722- on ExchangeId:
96246179F423722-). Exhausted after delivery attempt: 1 caught:
javax.net.ssl.SSLHandshakeException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target\n\nMessage History (source
location and message history is
disabled)\n--
javax.net.ssl.SSLHandshakeException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target {code}
In the case that a certificate is available the log shows
{code:java}
2023-10-18T09:38:50,803 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #10 -
timer://isp.route.system.deployment.service.scheduler |
SSLConnectionSocketFactory | 152 - org.apache.httpcomponents.httpclient -
4.5.13 | Connecting socket to
xxx.eu-central-1.compute.amazonaws.com/10.0.0.6:8446 with timeout 0
2023-10-18T09:38:50,805 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #10 -
timer://isp.route.system.deployment.service.scheduler |
SSLConnectionSocketFactory | 152 - org.apache.httpcomponents.httpclient -
4.5.13 | Enabled protocols: [TLSv1.3, TLSv1.2]
2023-10-18T09:38:50,806 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #10 -
timer://isp.route.system.deployment.service.scheduler |
SSLConnectionSocketFactory | 152 - org.apache.httpcomponents.httpclient -
4.5.13 | Enabled cipher suites:[TLS_AES_128_GCM_SHA256, TLS_AES_256_GCM_SHA384,
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384,
TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,
TLS_DHE_DSS_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256,
TLS_ECDH_RS
2023-10-18T09:38:50,806 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #10 -
timer://isp.route.system.deployment.service.scheduler |
SSLConnectionSocketFactory | 152 - org.apache.httpcomponents.httpclient -
4.5.13 | Starting handshake
2023-10-18T09:38:50,829 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #10 -
timer://isp.route.system.deployment.service.scheduler |
SSLConnectionSocketFactory | 152 - org.apache.httpcomponents.httpclient -
4.5.13 | Secure session established
2023-10-18T09:38:50,830 | DEBUG | Camel
[jira] [Commented] (CAMEL-19856) NoopHostnameVerifier seems to not working any longer
[
https://issues.apache.org/jira/browse/CAMEL-19856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776578#comment-17776578
]
Gerald Kallas commented on CAMEL-19856:
---
Find attached the DEBUG log
{code:java}
2023-10-18T09:34:00,433 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #8 -
timer://isp.route.system.deployment.service.scheduler |
SSLConnectionSocketFactory | 152 - org.apache.httpcomponents.httpclient -
4.5.13 | Connecting socket to
xxx.eu-central-1.compute.amazonaws.com/10.0.0.6:8446 with timeout 0
2023-10-18T09:34:00,435 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #8 -
timer://isp.route.system.deployment.service.scheduler |
SSLConnectionSocketFactory | 152 - org.apache.httpcomponents.httpclient -
4.5.13 | Enabled protocols: [TLSv1.3, TLSv1.2]
2023-10-18T09:34:00,436 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #8 -
timer://isp.route.system.deployment.service.scheduler |
SSLConnectionSocketFactory | 152 - org.apache.httpcomponents.httpclient -
4.5.13 | Enabled cipher suites:[TLS_AES_128_GCM_SHA256, TLS_AES_256_GCM_SHA384,
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384,
TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,
TLS_DHE_DSS_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256,
TLS_ECDH_RS
2023-10-18T09:34:00,436 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #8 -
timer://isp.route.system.deployment.service.scheduler |
SSLConnectionSocketFactory | 152 - org.apache.httpcomponents.httpclient -
4.5.13 | Starting handshake
2023-10-18T09:34:00,478 | ERROR | Camel
(isp.route.system.deployment.service.scheduler) thread #8 -
timer://isp.route.system.deployment.service.scheduler | DefaultErrorHandler
| 91 - org.apache.camel.camel-core-reifier - 3.20.2 | Failed delivery
for (MessageId: 96246179F423722- on ExchangeId:
96246179F423722-). Exhausted after delivery attempt: 1 caught:
javax.net.ssl.SSLHandshakeException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target\n\nMessage History (source
location and message history is
disabled)\n--
javax.net.ssl.SSLHandshakeException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target {code}
In the case that a certificate is available the log shows
{code:java}
2023-10-18T09:38:50,803 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #10 -
timer://isp.route.system.deployment.service.scheduler |
SSLConnectionSocketFactory | 152 - org.apache.httpcomponents.httpclient -
4.5.13 | Connecting socket to
xxx.eu-central-1.compute.amazonaws.com/10.0.0.6:8446 with timeout 0
2023-10-18T09:38:50,805 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #10 -
timer://isp.route.system.deployment.service.scheduler |
SSLConnectionSocketFactory | 152 - org.apache.httpcomponents.httpclient -
4.5.13 | Enabled protocols: [TLSv1.3, TLSv1.2]
2023-10-18T09:38:50,806 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #10 -
timer://isp.route.system.deployment.service.scheduler |
SSLConnectionSocketFactory | 152 - org.apache.httpcomponents.httpclient -
4.5.13 | Enabled cipher suites:[TLS_AES_128_GCM_SHA256, TLS_AES_256_GCM_SHA384,
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384,
TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,
TLS_DHE_DSS_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256,
TLS_ECDH_RS
2023-10-18T09:38:50,806 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #10 -
timer://isp.route.system.deployment.service.scheduler |
SSLConnectionSocketFactory | 152 - org.apache.httpcomponents.httpclient -
4.5.13 | Starting handshake
2023-10-18T09:38:50,829 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #10 -
timer://isp.route.system.deployment.service.scheduler |
SSLConnectionSocketFactory | 152 - org.apache.httpcomponents.httpclient -
4.5.13 | Secure session established
2023-10-18T09:38:50,830 | DEBUG | Camel
(isp.route.system.deployment.service.scheduler) thread #10 -
[jira] [Commented] (CAMEL-19856) NoopHostnameVerifier seems to not working any longer
[
https://issues.apache.org/jira/browse/CAMEL-19856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776150#comment-17776150
]
Gerald Kallas commented on CAMEL-19856:
---
That seems to be different to older Camel versions. We did always use the
noopHostnameVerifier bean when no server certificate was contained in the
system's or frameworks truststore.
I'll increase the log level and let you know.
> NoopHostnameVerifier seems to not working any longer
>
>
> Key: CAMEL-19856
> URL: https://issues.apache.org/jira/browse/CAMEL-19856
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 3.20.2
>Reporter: Gerald Kallas
>Priority: Minor
>
> we had a code (XML DSL) that was already working to skip SSL hostname
> validation like
> {code:java}
> class="org.apache.http.conn.ssl.NoopHostnameVerifier"/>
> ...
> uri='https://server/api/v1/entity/integrationservice/delta?x509HostnameVerifier=noopHostnameVerifier'/>{code}
> It's not working anymore, getting
>
> {code:java}
> javax.net.ssl.SSLHandshakeException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target {code}
> I tried also
>
> {code:java}
> uri='https://server/api/v1/entity/integrationservice/delta?x509HostnameVerifier=#noopHostnameVerifier'/>{code}
> same error.
>
> The underlying Java (within a Docker containe) is
>
> {code:java}
> openjdk version "11.0.11" 2021-04-20 OpenJDK Runtime Environment
> AdoptOpenJDK-11.0.11+9 (build 11.0.11+9) OpenJDK 64-Bit Server VM
> AdoptOpenJDK-11.0.11+9 (build 11.0.11+9, mixed mode){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-19856) NoopHostnameVerifier seems to not working any longer
[
https://issues.apache.org/jira/browse/CAMEL-19856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767950#comment-17767950
]
Gerald Kallas edited comment on CAMEL-19856 at 9/22/23 10:52 AM:
-
The other ticket https://issues.apache.org/jira/browse/CAMEL-19858 has been
solved but here the error remains the same.
If no valid certificate is being found, the error occurs but it shouldn't with
this parameter.
was (Author: catshout):
The other ticket https://issues.apache.org/jira/browse/CAMEL-19858 has been
solved but here the error remains the same.
> NoopHostnameVerifier seems to not working any longer
>
>
> Key: CAMEL-19856
> URL: https://issues.apache.org/jira/browse/CAMEL-19856
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 3.20.2
>Reporter: Gerald Kallas
>Priority: Minor
>
> we had a code (XML DSL) that was already working to skip SSL hostname
> validation like
> {code:java}
> class="org.apache.http.conn.ssl.NoopHostnameVerifier"/>
> ...
> uri='https://server/api/v1/entity/integrationservice/delta?x509HostnameVerifier=noopHostnameVerifier'/>{code}
> It's not working anymore, getting
>
> {code:java}
> javax.net.ssl.SSLHandshakeException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target {code}
> I tried also
>
> {code:java}
> uri='https://server/api/v1/entity/integrationservice/delta?x509HostnameVerifier=#noopHostnameVerifier'/>{code}
> same error.
>
> The underlying Java (within a Docker containe) is
>
> {code:java}
> openjdk version "11.0.11" 2021-04-20 OpenJDK Runtime Environment
> AdoptOpenJDK-11.0.11+9 (build 11.0.11+9) OpenJDK 64-Bit Server VM
> AdoptOpenJDK-11.0.11+9 (build 11.0.11+9, mixed mode){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19856) NoopHostnameVerifier seems to not working any longer
[
https://issues.apache.org/jira/browse/CAMEL-19856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767950#comment-17767950
]
Gerald Kallas commented on CAMEL-19856:
---
The other ticket https://issues.apache.org/jira/browse/CAMEL-19858 has been
solved but here the error remains the same.
> NoopHostnameVerifier seems to not working any longer
>
>
> Key: CAMEL-19856
> URL: https://issues.apache.org/jira/browse/CAMEL-19856
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 3.20.2
>Reporter: Gerald Kallas
>Priority: Minor
>
> we had a code (XML DSL) that was already working to skip SSL hostname
> validation like
> {code:java}
> class="org.apache.http.conn.ssl.NoopHostnameVerifier"/>
> ...
> uri='https://server/api/v1/entity/integrationservice/delta?x509HostnameVerifier=noopHostnameVerifier'/>{code}
> It's not working anymore, getting
>
> {code:java}
> javax.net.ssl.SSLHandshakeException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target {code}
> I tried also
>
> {code:java}
> uri='https://server/api/v1/entity/integrationservice/delta?x509HostnameVerifier=#noopHostnameVerifier'/>{code}
> same error.
>
> The underlying Java (within a Docker containe) is
>
> {code:java}
> openjdk version "11.0.11" 2021-04-20 OpenJDK Runtime Environment
> AdoptOpenJDK-11.0.11+9 (build 11.0.11+9) OpenJDK 64-Bit Server VM
> AdoptOpenJDK-11.0.11+9 (build 11.0.11+9, mixed mode){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19858) Truststore can't be found with sslContextParameters
[
https://issues.apache.org/jira/browse/CAMEL-19858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767840#comment-17767840
]
Gerald Kallas commented on CAMEL-19858:
---
??You need to use [file:/|file:///] for your resources.??
This did the trick, many thanks. I'm going to close the ticket.
Best
Gerald
> Truststore can't be found with sslContextParameters
> ---
>
> Key: CAMEL-19858
> URL: https://issues.apache.org/jira/browse/CAMEL-19858
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 3.20.2
>Reporter: Gerald Kallas
>Priority: Major
>
> I've following code
> {code:java}
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> password="xxx"/>
>
>
> resource="/opt/apache-karaf/etc/truststore.jks" password="xxx"/>
>
>
> ...
> uri='https://server/api/v1/entity/integrationservice/delta?sslContextParameters=#sslContextParameters'/>{code}
> and I'm getting the error
> {code:java}
> javax.net.ssl.SSLException: Unexpected error:
> java.security.InvalidAlgorithmParameterException: the trustAnchors parameter
> must be non-empty{code}
> This error relates normally to the fact that a keystore or truststore can't
> be found.
> Both are there and the truststore contains the appropriate certificate.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-19858) Truststore can't be found with sslContextParameters
[
https://issues.apache.org/jira/browse/CAMEL-19858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767840#comment-17767840
]
Gerald Kallas edited comment on CAMEL-19858 at 9/22/23 6:04 AM:
??You need to use [file:/|file:///] for your resources.??
This did the trick, many thanks. The ticket is already marked as solved.
Best
Gerald
was (Author: catshout):
??You need to use [file:/|file:///] for your resources.??
This did the trick, many thanks. I'm going to close the ticket.
Best
Gerald
> Truststore can't be found with sslContextParameters
> ---
>
> Key: CAMEL-19858
> URL: https://issues.apache.org/jira/browse/CAMEL-19858
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 3.20.2
>Reporter: Gerald Kallas
>Priority: Major
>
> I've following code
> {code:java}
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> password="xxx"/>
>
>
> resource="/opt/apache-karaf/etc/truststore.jks" password="xxx"/>
>
>
> ...
> uri='https://server/api/v1/entity/integrationservice/delta?sslContextParameters=#sslContextParameters'/>{code}
> and I'm getting the error
> {code:java}
> javax.net.ssl.SSLException: Unexpected error:
> java.security.InvalidAlgorithmParameterException: the trustAnchors parameter
> must be non-empty{code}
> This error relates normally to the fact that a keystore or truststore can't
> be found.
> Both are there and the truststore contains the appropriate certificate.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19896) DeadLetterChannelBuilder can't be configured with a redeliveryPolicy
Gerald Kallas created CAMEL-19896:
-
Summary: DeadLetterChannelBuilder can't be configured with a
redeliveryPolicy
Key: CAMEL-19896
URL: https://issues.apache.org/jira/browse/CAMEL-19896
Project: Camel
Issue Type: Bug
Components: came-core
Affects Versions: 3.20.2
Reporter: Gerald Kallas
The following snippet is contained in a global ActiveMQ definition XML
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;>
...
{code}
During the deployment the following error occurs
{code:java}
org.osgi.service.blueprint.container.ComponentDefinitionException: Error
setting property: PropertyDescriptor
[jira] [Created] (CAMEL-19858) Truststore can't be found with sslContextParameters
Gerald Kallas created CAMEL-19858:
-
Summary: Truststore can't be found with sslContextParameters
Key: CAMEL-19858
URL: https://issues.apache.org/jira/browse/CAMEL-19858
Project: Camel
Issue Type: Bug
Components: camel-http4
Affects Versions: 3.20.2
Reporter: Gerald Kallas
I've following code
{code:java}
http://camel.apache.org/schema/blueprint;>
...
{code}
and I'm getting the error
{code:java}
javax.net.ssl.SSLException: Unexpected error:
java.security.InvalidAlgorithmParameterException: the trustAnchors parameter
must be non-empty{code}
This error relates normally to the fact that a keystore or truststore can't be
found.
Both are there and the truststore contains the appropriate certificate.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19858) Truststore can't be found with sslContextParameters
[
https://issues.apache.org/jira/browse/CAMEL-19858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-19858:
--
Description:
I've following code
{code:java}
http://camel.apache.org/schema/blueprint;>
...
{code}
and I'm getting the error
{code:java}
javax.net.ssl.SSLException: Unexpected error:
java.security.InvalidAlgorithmParameterException: the trustAnchors parameter
must be non-empty{code}
This error relates normally to the fact that a keystore or truststore can't be
found.
Both are there and the truststore contains the appropriate certificate.
was:
I've following code
{code:java}
http://camel.apache.org/schema/blueprint;>
...
{code}
and I'm getting the error
{code:java}
javax.net.ssl.SSLException: Unexpected error:
java.security.InvalidAlgorithmParameterException: the trustAnchors parameter
must be non-empty{code}
This error relates normally to the fact that a keystore or truststore can't be
found.
Both are there and the truststore contains the appropriate certificate.
> Truststore can't be found with sslContextParameters
> ---
>
> Key: CAMEL-19858
> URL: https://issues.apache.org/jira/browse/CAMEL-19858
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 3.20.2
>Reporter: Gerald Kallas
>Priority: Major
>
> I've following code
> {code:java}
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> password="xxx"/>
>
>
> resource="/opt/apache-karaf/etc/truststore.jks" password="xxx"/>
>
>
> ...
> uri='https://server/api/v1/entity/integrationservice/delta?sslContextParameters=#sslContextParameters'/>{code}
> and I'm getting the error
> {code:java}
> javax.net.ssl.SSLException: Unexpected error:
> java.security.InvalidAlgorithmParameterException: the trustAnchors parameter
> must be non-empty{code}
> This error relates normally to the fact that a keystore or truststore can't
> be found.
> Both are there and the truststore contains the appropriate certificate.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19856) NoopHostnameVerifier seems to not working any longer
[
https://issues.apache.org/jira/browse/CAMEL-19856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-19856:
--
Description:
we had a code (XML DSL) that was already working to skip SSL hostname
validation like
{code:java}
...
{code}
It's not working anymore, getting
{code:java}
javax.net.ssl.SSLHandshakeException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target {code}
I tried also
{code:java}
{code}
same error.
The underlying Java (within a Docker containe) is
{code:java}
openjdk version "11.0.11" 2021-04-20 OpenJDK Runtime Environment
AdoptOpenJDK-11.0.11+9 (build 11.0.11+9) OpenJDK 64-Bit Server VM
AdoptOpenJDK-11.0.11+9 (build 11.0.11+9, mixed mode){code}
was:
we had a code (XML DSL) that was already working to skip SSL hostname
validation like
{code:java}
...
{code}
It's not working anymore, getting
{code:java}
javax.net.ssl.SSLHandshakeException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target {code}
I tried also
{code:java}
{code}
same error.
The underlying Java (within a Docker containe) is
{code:java}
openjdk version "11.0.11" 2021-04-20 OpenJDK Runtime Environment
AdoptOpenJDK-11.0.11+9 (build 11.0.11+9) OpenJDK 64-Bit Server VM
AdoptOpenJDK-11.0.11+9 (build 11.0.11+9, mixed mode){code}
> NoopHostnameVerifier seems to not working any longer
>
>
> Key: CAMEL-19856
> URL: https://issues.apache.org/jira/browse/CAMEL-19856
> Project: Camel
> Issue Type: Bug
> Components: camel-http4
>Affects Versions: 3.20.2
>Reporter: Gerald Kallas
>Priority: Major
>
> we had a code (XML DSL) that was already working to skip SSL hostname
> validation like
> {code:java}
> class="org.apache.http.conn.ssl.NoopHostnameVerifier"/>
> ...
> uri='https://server/api/v1/entity/integrationservice/delta?x509HostnameVerifier=noopHostnameVerifier'/>{code}
> It's not working anymore, getting
>
> {code:java}
> javax.net.ssl.SSLHandshakeException: PKIX path building failed:
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find
> valid certification path to requested target {code}
> I tried also
>
> {code:java}
> uri='https://server/api/v1/entity/integrationservice/delta?x509HostnameVerifier=#noopHostnameVerifier'/>{code}
> same error.
>
> The underlying Java (within a Docker containe) is
>
> {code:java}
> openjdk version "11.0.11" 2021-04-20 OpenJDK Runtime Environment
> AdoptOpenJDK-11.0.11+9 (build 11.0.11+9) OpenJDK 64-Bit Server VM
> AdoptOpenJDK-11.0.11+9 (build 11.0.11+9, mixed mode){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19856) NoopHostnameVerifier seems to not working any longer
Gerald Kallas created CAMEL-19856:
-
Summary: NoopHostnameVerifier seems to not working any longer
Key: CAMEL-19856
URL: https://issues.apache.org/jira/browse/CAMEL-19856
Project: Camel
Issue Type: Bug
Components: camel-http4
Affects Versions: 3.20.2
Reporter: Gerald Kallas
we had a code (XML DSL) that was already working to skip SSL hostname
validation like
{code:java}
...
{code}
It's not working anymore, getting
{code:java}
javax.net.ssl.SSLHandshakeException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target {code}
I tried also
{code:java}
{code}
same error.
The underlying Java (within a Docker containe) is
{code:java}
openjdk version "11.0.11" 2021-04-20 OpenJDK Runtime Environment
AdoptOpenJDK-11.0.11+9 (build 11.0.11+9) OpenJDK 64-Bit Server VM
AdoptOpenJDK-11.0.11+9 (build 11.0.11+9, mixed mode){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-16464) Remove Camel-jsonpath karaf feature
[ https://issues.apache.org/jira/browse/CAMEL-16464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17364744#comment-17364744 ] Gerald Kallas commented on CAMEL-16464: --- Hi [~davsclaus] [~acosentino] as we're using the [https://camel.apache.org/components/3.7.x/languages/jsonpath-language.html] component in our routes, what is your recommendation to include this with Karaf/Camel based runtime? Best Gerald > Remove Camel-jsonpath karaf feature > --- > > Key: CAMEL-16464 > URL: https://issues.apache.org/jira/browse/CAMEL-16464 > Project: Camel > Issue Type: Task > Components: karaf >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.10.0 > > > The needed upgrade of json-smart and accessors smart shows troubles with asm > version. Since the karaf features maintenace is best effort, I'm going to > remove it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15663) camel-json-validator should return full error message by default
Gerald Kallas created CAMEL-15663:
-
Summary: camel-json-validator should return full error message by
default
Key: CAMEL-15663
URL: https://issues.apache.org/jira/browse/CAMEL-15663
Project: Camel
Issue Type: Improvement
Affects Versions: 3.4.4
Reporter: Gerald Kallas
When the camel-json-validator throws an error occurs it shows only in log
"JSON validation error with 1 errors.
Exchange[ID-700bc59e90f0-1601310667823-12-4]"
${exception.message} shows no details as well. The following
${exception.getErrors()}
shows all details what is wrong in the JSON structure.
For convenience it would be helpfull when the error message itself contains
these details.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-15662) Camel 3.4.4 feature:install camel-json-validator causes an error
Gerald Kallas created CAMEL-15662:
-
Summary: Camel 3.4.4 feature:install camel-json-validator causes
an error
Key: CAMEL-15662
URL: https://issues.apache.org/jira/browse/CAMEL-15662
Project: Camel
Issue Type: Bug
Affects Versions: 3.4.4
Reporter: Gerald Kallas
feature:install camel-json-validator
on Karaf 4.2.9. It causes an error
{code:java}
java.lang.ArrayIndexOutOfBoundsException: Index 19 out of bounds for length 19
at aQute.bnd.osgi.Clazz.parseClassFile(Clazz.java:576)
at aQute.bnd.osgi.Clazz.parseClassFile(Clazz.java:494)
at aQute.bnd.osgi.Clazz.parseClassFileWithCollector(Clazz.java:483)
at aQute.bnd.osgi.Clazz.parseClassFile(Clazz.java:473)
at aQute.bnd.osgi.Analyzer.analyzeJar(Analyzer.java:2177)
at aQute.bnd.osgi.Analyzer.analyzeBundleClasspath(Analyzer.java:2083)
at aQute.bnd.osgi.Analyzer.analyze(Analyzer.java:138)
at aQute.bnd.osgi.Analyzer.calcManifest(Analyzer.java:616)
at org.ops4j.pax.swissbox.bnd.BndUtils.createBundle(BndUtils.java:161)
at org.ops4j.pax.url.wrap.internal.Connection.getInputStream(Connection.java:83)
at java.base/java.net.URL.openStream(URL.java:1140)
at
org.apache.karaf.features.internal.download.impl.SimpleDownloadTask.download(SimpleDownloadTask.java:78)
at
org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:60)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
java.lang.ArrayIndexOutOfBoundsException: Index 19 out of bounds for length 19
at aQute.bnd.osgi.Clazz.parseClassFile(Clazz.java:576)
at aQute.bnd.osgi.Clazz.parseClassFile(Clazz.java:494)
at aQute.bnd.osgi.Clazz.parseClassFileWithCollector(Clazz.java:483)
at aQute.bnd.osgi.Clazz.parseClassFile(Clazz.java:473)
at aQute.bnd.osgi.Analyzer.analyzeJar(Analyzer.java:2177)
at aQute.bnd.osgi.Analyzer.analyzeBundleClasspath(Analyzer.java:2083)
at aQute.bnd.osgi.Analyzer.analyze(Analyzer.java:138)
at aQute.bnd.osgi.Analyzer.calcManifest(Analyzer.java:616)
at org.ops4j.pax.swissbox.bnd.BndUtils.createBundle(BndUtils.java:161)
at org.ops4j.pax.url.wrap.internal.Connection.getInputStream(Connection.java:83)
at java.base/java.net.URL.openStream(URL.java:1140)
at
org.apache.karaf.features.internal.download.impl.SimpleDownloadTask.download(SimpleDownloadTask.java:78)
at
org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:60)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-15000) Using a registered ConstraintSecurityHandler in another Blueprint file causes an java.lang.IllegalStateException: STARTED
[
https://issues.apache.org/jira/browse/CAMEL-15000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17099742#comment-17099742
]
Gerald Kallas edited comment on CAMEL-15000 at 5/5/20, 10:10 AM:
-
[~davsclaus]
At 1st I've done a vanilla installation of karaf 4.2.8. The deployed files for
reference see at the bottom.
My etc/user.properties looks like ..
{code:java}
...
username1 = password1,TSTISP001
{code}
Afterwards I did execute these commands ..
{code:java}
feature:repo-add camel 3.2.0
feature:install camel camel-jetty
{code}
No error but the security handler seems to be ignored completely. The blueprint
all-in-one works but the security handler is being ignored. The 2 blueprints
separated show no errors during deployment, the security handler is being
ignored either (means the route is working but with no auth).
At 2nd I've done again a vanilla installation of karaf 4.2.8. Same
etc/user.properties.
I did execute (you may recognize additionally the webconsole feature)
{code:java}
feature:repo-add camel 3.2.0
feature:install webconsole camel camel-jetty
{code}
The blueprint all-in-one now works with authentication. The 2 blueprints
separated shows the errors during deployment ..
{code:java}
2020-05-05T09:55:57,808 | INFO | fileinstall-/opt/apache-karaf-4.2.8/deploy |
fileinstall | 10 - org.apache.felix.fileinstall - 3.6.4 |
Installing bundle isp.jettyHttpComponent.xml / 0.0.0
2020-05-05T09:55:57,845 | INFO | paxweb-config-1-thread-2 |
HttpServiceFactoryImpl | 160 - org.ops4j.pax.web.pax-web-runtime -
7.2.14 | Unbinding bundle: [org.apache.karaf.webconsole.console [117]]
2020-05-05T09:55:57,850 | INFO | paxweb-config-1-thread-2 | ContextHandler
| 142 - org.eclipse.jetty.util - 9.4.22.v20191022 | Stopped
HttpServiceContext{httpContext=DefaultHttpContext
[bundle=org.apache.karaf.webconsole.console [117], contextID=custom]}
2020-05-05T09:55:57,851 | INFO | paxweb-config-1-thread-2 |
HttpServiceFactoryImpl | 160 - org.ops4j.pax.web.pax-web-runtime -
7.2.14 | Unbinding bundle: [org.apache.karaf.http.core [113]]
2020-05-05T09:55:57,856 | INFO | activator-1-thread-3 | CommandExtension
| 34 - org.apache.karaf.shell.core - 4.2.8 | Unregistering commands
for bundle org.apache.karaf.http.core/4.2.8
2020-05-05T09:55:57,895 | INFO | activator-1-thread-3 | HttpPlugin
| 120 - org.apache.karaf.webconsole.http - 4.2.8 | Http plugin
deactivated
2020-05-05T09:55:57,897 | INFO | paxweb-config-1-thread-2 | AbstractConnector
| 142 - org.eclipse.jetty.util - 9.4.22.v20191022 | Stopped
default@4dcfa0eb{HTTP/1.1,[http/1.1]}{0.0.0.0:8181}
2020-05-05T09:55:57,897 | INFO | paxweb-config-1-thread-2 | session
| 142 - org.eclipse.jetty.util - 9.4.22.v20191022 | node0 Stopped
scavenging
2020-05-05T09:55:57,900 | INFO | paxweb-config-1-thread-2 | Activator
| 160 - org.ops4j.pax.web.pax-web-runtime - 7.2.14 |
ServerControllerFactory is gone, HTTP Service is not available now.
2020-05-05T09:55:57,902 | INFO | fileinstall-/opt/apache-karaf-4.2.8/deploy |
BlueprintContainerImpl | 49 - org.apache.aries.blueprint.core -
1.10.2 | Blueprint bundle isp.jettyHttpComponent.xml/0.0.0 has been started
2020-05-05T09:55:57,910 | INFO | fileinstall-/opt/apache-karaf-4.2.8/deploy |
fileinstall | 10 - org.apache.felix.fileinstall - 3.6.4 |
Started bundle:
blueprint:file:/opt/apache-karaf-4.2.8/deploy/isp.jettyHttpComponent.xml
2020-05-05T09:55:57,931 | INFO | paxweb-config-1-thread-2 | JettyFactoryImpl
| 159 - org.ops4j.pax.web.pax-web-jetty - 7.2.14 | No ALPN class
available
2020-05-05T09:55:57,931 | INFO | paxweb-config-1-thread-2 | JettyFactoryImpl
| 159 - org.ops4j.pax.web.pax-web-jetty - 7.2.14 | HTTP/2 not
available, creating standard ServerConnector for Http
2020-05-05T09:55:57,932 | INFO | paxweb-config-1-thread-2 | JettyServerImpl
| 159 - org.ops4j.pax.web.pax-web-jetty - 7.2.14 | Pax Web
available at [0.0.0.0]:[8181]
2020-05-05T09:55:57,936 | INFO | paxweb-config-1-thread-2 |
HttpServiceFactoryImpl | 160 - org.ops4j.pax.web.pax-web-runtime -
7.2.14 | Binding bundle: [org.apache.karaf.http.core [113]] to http service
2020-05-05T09:55:57,941 | INFO | paxweb-config-1-thread-2 |
HttpServiceFactoryImpl | 160 - org.ops4j.pax.web.pax-web-runtime -
7.2.14 | Binding bundle: [org.apache.karaf.webconsole.console [117]] to http
service
2020-05-05T09:55:57,949 | INFO | paxweb-config-1-thread-2 |
ServletContainerInitializerScanner | 158 - org.ops4j.pax.web.pax-web-api -
7.2.14 | will add
org.eclipse.jetty.websocket.server.NativeWebSocketServletContainerInitializer
to ServletContainerInitializers
2020-05-05T09:55:57,949 | INFO |
[jira] [Commented] (CAMEL-15000) Using a registered ConstraintSecurityHandler in another Blueprint file causes an java.lang.IllegalStateException: STARTED
[
https://issues.apache.org/jira/browse/CAMEL-15000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17099742#comment-17099742
]
Gerald Kallas commented on CAMEL-15000:
---
[~davsclaus]
At 1st I've done a vanilla installation of karaf 4.2.8. The deployed files for
reference see at the bottom.
My etc/user.properties looks like ..
{code:java}
...
username1 = password1,TSTISP001
{code}
Afterwards I did execute these commands ..
{code:java}
feature:repo-add camel 3.2.0
feature:install camel camel-jetty
{code}
No error but the security handler seems to be ignored completely. The blueprint
all-in-one works but the security handler is being ignored. The 2 blueprints
separated show no errors during deployment, the security handler is being
ignored either (means the route is working but with no auth).
At 2nd I've done again a vanilla installation of karaf 4.2.8. Same
etc/user.properties.
I did execute (you may recognize additionally the webconsole feature)
{code:java}
feature:repo-add camel 3.2.0
feature:install webconsole camel camel-jetty
{code}
The blueprint all-in-one now works with authentication. The 2 blueprints
separated shows the errors during deployment ..
{code:java}
2020-05-05T09:55:57,808 | INFO | fileinstall-/opt/apache-karaf-4.2.8/deploy |
fileinstall | 10 - org.apache.felix.fileinstall - 3.6.4 |
Installing bundle isp.jettyHttpComponent.xml / 0.0.0
2020-05-05T09:55:57,845 | INFO | paxweb-config-1-thread-2 |
HttpServiceFactoryImpl | 160 - org.ops4j.pax.web.pax-web-runtime -
7.2.14 | Unbinding bundle: [org.apache.karaf.webconsole.console [117]]
2020-05-05T09:55:57,850 | INFO | paxweb-config-1-thread-2 | ContextHandler
| 142 - org.eclipse.jetty.util - 9.4.22.v20191022 | Stopped
HttpServiceContext{httpContext=DefaultHttpContext
[bundle=org.apache.karaf.webconsole.console [117], contextID=custom]}
2020-05-05T09:55:57,851 | INFO | paxweb-config-1-thread-2 |
HttpServiceFactoryImpl | 160 - org.ops4j.pax.web.pax-web-runtime -
7.2.14 | Unbinding bundle: [org.apache.karaf.http.core [113]]
2020-05-05T09:55:57,856 | INFO | activator-1-thread-3 | CommandExtension
| 34 - org.apache.karaf.shell.core - 4.2.8 | Unregistering commands
for bundle org.apache.karaf.http.core/4.2.8
2020-05-05T09:55:57,895 | INFO | activator-1-thread-3 | HttpPlugin
| 120 - org.apache.karaf.webconsole.http - 4.2.8 | Http plugin
deactivated
2020-05-05T09:55:57,897 | INFO | paxweb-config-1-thread-2 | AbstractConnector
| 142 - org.eclipse.jetty.util - 9.4.22.v20191022 | Stopped
default@4dcfa0eb{HTTP/1.1,[http/1.1]}{0.0.0.0:8181}
2020-05-05T09:55:57,897 | INFO | paxweb-config-1-thread-2 | session
| 142 - org.eclipse.jetty.util - 9.4.22.v20191022 | node0 Stopped
scavenging
2020-05-05T09:55:57,900 | INFO | paxweb-config-1-thread-2 | Activator
| 160 - org.ops4j.pax.web.pax-web-runtime - 7.2.14 |
ServerControllerFactory is gone, HTTP Service is not available now.
2020-05-05T09:55:57,902 | INFO | fileinstall-/opt/apache-karaf-4.2.8/deploy |
BlueprintContainerImpl | 49 - org.apache.aries.blueprint.core -
1.10.2 | Blueprint bundle isp.jettyHttpComponent.xml/0.0.0 has been started
2020-05-05T09:55:57,910 | INFO | fileinstall-/opt/apache-karaf-4.2.8/deploy |
fileinstall | 10 - org.apache.felix.fileinstall - 3.6.4 |
Started bundle:
blueprint:file:/opt/apache-karaf-4.2.8/deploy/isp.jettyHttpComponent.xml
2020-05-05T09:55:57,931 | INFO | paxweb-config-1-thread-2 | JettyFactoryImpl
| 159 - org.ops4j.pax.web.pax-web-jetty - 7.2.14 | No ALPN class
available
2020-05-05T09:55:57,931 | INFO | paxweb-config-1-thread-2 | JettyFactoryImpl
| 159 - org.ops4j.pax.web.pax-web-jetty - 7.2.14 | HTTP/2 not
available, creating standard ServerConnector for Http
2020-05-05T09:55:57,932 | INFO | paxweb-config-1-thread-2 | JettyServerImpl
| 159 - org.ops4j.pax.web.pax-web-jetty - 7.2.14 | Pax Web
available at [0.0.0.0]:[8181]
2020-05-05T09:55:57,936 | INFO | paxweb-config-1-thread-2 |
HttpServiceFactoryImpl | 160 - org.ops4j.pax.web.pax-web-runtime -
7.2.14 | Binding bundle: [org.apache.karaf.http.core [113]] to http service
2020-05-05T09:55:57,941 | INFO | paxweb-config-1-thread-2 |
HttpServiceFactoryImpl | 160 - org.ops4j.pax.web.pax-web-runtime -
7.2.14 | Binding bundle: [org.apache.karaf.webconsole.console [117]] to http
service
2020-05-05T09:55:57,949 | INFO | paxweb-config-1-thread-2 |
ServletContainerInitializerScanner | 158 - org.ops4j.pax.web.pax-web-api -
7.2.14 | will add
org.eclipse.jetty.websocket.server.NativeWebSocketServletContainerInitializer
to ServletContainerInitializers
2020-05-05T09:55:57,949 | INFO | paxweb-config-1-thread-2 |
[jira] [Commented] (CAMEL-15000) Using a registered ConstraintSecurityHandler in another Blueprint file causes an java.lang.IllegalStateException: STARTED
[
https://issues.apache.org/jira/browse/CAMEL-15000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17099156#comment-17099156
]
Gerald Kallas commented on CAMEL-15000:
---
The line
{code:java}
https://0.0.0.0:8444/hello1?sslContextParameters=#sslContextParametershandlers=#securityHandlerIsp;
/>
{code}
with a '#' doesn't work either.
> Using a registered ConstraintSecurityHandler in another Blueprint file causes
> an java.lang.IllegalStateException: STARTED
> -
>
> Key: CAMEL-15000
> URL: https://issues.apache.org/jira/browse/CAMEL-15000
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Minor
>
> I've defined a Blueprint DSL file with a securityHandler configuration for
> multiple paths as following
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
> class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP001
>
>
>
> class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
> class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP002
>
>
>
> class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
> class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>
> value="/opt/apache-karaf/etc/users.properties" />
>
>
>
> class="org.eclipse.jetty.security.authentication.BasicAuthenticator" />
>
>
>
>
>
>
>
>
> interface="org.eclipse.jetty.server.Handler" />
> xmlns="http://camel.apache.org/schema/blueprint;>
> ...
>
>
>
> {code}
> The use in another Blueprint DSL file as attached
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
> interface="org.apache.camel.support.jsse.SSLContextParameters"
> ext:proxy-method="classes" />
>
> interface="org.eclipse.jetty.server.Handler" />
> xmlns="http://camel.apache.org/schema/blueprint; streamCache="true"
> useBreadcrumb="true">
>
> uri="jetty:https://0.0.0.0:8444/hello1?sslContextParameters=#sslContextParametershandlers=securityHandlerIsp;
> />
> Hello 1
>
>
>
> {code}
> causes an error
> {code:java}
> 2020-05-02T19:15:46,202 | ERROR | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 92 - org.apache.camel.camel-api - 3.0.0 |
> Error starting CamelContext (isp.context.user.TSTISP001) due to exception
> thrown: STARTED
> java.lang.IllegalStateException: STARTED
> at
> org.eclipse.jetty.server.handler.AbstractHandlerContainer.setServer(AbstractHandlerContainer.java:131)
> ~[!/:9.4.20.v20190813]
> at Proxyb4d61c20_c161_4396_a800_1fa982bbaaea.setServer(Unknown
> Source) ~[?:?]
> at
> org.eclipse.jetty.server.handler.HandlerCollection.updateHandlers(HandlerCollection.java:117)
> ~[!/:9.4.20.v20190813]
> at
> org.eclipse.jetty.server.handler.HandlerCollection.addHandler(HandlerCollection.java:180)
> ~[!/:9.4.20.v20190813]
> at
> org.apache.camel.component.jetty.JettyHttpComponent.addJettyHandlers(JettyHttpComponent.java:1182)
> ~[!/:3.0.0]
> at
> org.apache.camel.component.jetty.JettyHttpComponent.createServletForConnector(JettyHttpComponent.java:1145)
> ~[!/:3.0.0]
> at
> org.apache.camel.component.jetty.JettyHttpComponent.connect(JettyHttpComponent.java:329)
> ~[!/:3.0.0]
> at
> org.apache.camel.http.common.HttpCommonEndpoint.connect(HttpCommonEndpoint.java:177)
> ~[!/:3.0.0]
> at
> org.apache.camel.http.common.HttpConsumer.doStart(HttpConsumer.java:58)
> ~[!/:3.0.0]
> at
> org.apache.camel.component.jetty.JettyHttpConsumer.doStart(JettyHttpConsumer.java:31)
> ~[!/:3.0.0]
> at
> org.apache.camel.support.service.ServiceSupport.start(ServiceSupport.java:117)
> ~[!/:3.0.0]
> at
> org.apache.camel.impl.engine.AbstractCamelContext.startService(AbstractCamelContext.java:2900)
> ~[!/:3.0.0]
[jira] [Commented] (CAMEL-15000) Using a registered ConstraintSecurityHandler in another Blueprint file causes an java.lang.IllegalStateException: STARTED
[
https://issues.apache.org/jira/browse/CAMEL-15000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17098790#comment-17098790
]
Gerald Kallas commented on CAMEL-15000:
---
[~cib...@e-ma.net] I was digging into the details a bit more. When I'm going to
update the first Blueprint file with the securityHandler definition than the
embedded Jetty seems to be stopped gracefully und restarted again after
updating the securityHandler.
{code:java}
2020-05-04T08:52:18,722 | INFO | fileinstall-/opt/apache-karaf-4.2.7/deploy |
fileinstall | 10 - org.apache.felix.fileinstall - 3.6.4 |
Updating bundle isp.jettyHttpComponent.xml / 0.0.0
2020-05-04T08:52:18,723 | INFO | fileinstall-/opt/apache-karaf-4.2.7/deploy |
BlueprintExtender| 84 - org.apache.aries.blueprint.core -
1.10.2 | Destroying container for blueprint bundle
isp.jettyHttpComponent.xml/0.0.0
2020-05-04T08:52:19,200 | INFO | paxweb-config-2-thread-3 |
HttpServiceFactoryImpl | 258 - org.ops4j.pax.web.pax-web-runtime -
7.2.11 | Unbinding bundle: [org.apache.karaf.webconsole.gogo [178]]
2020-05-04T08:52:19,210 | INFO | paxweb-config-2-thread-3 |
HttpServiceFactoryImpl | 258 - org.ops4j.pax.web.pax-web-runtime -
7.2.11 | Unbinding bundle: [org.apache.felix.inventory [154]]
2020-05-04T08:52:19,249 | INFO | paxweb-config-2-thread-3 |
HttpServiceFactoryImpl | 258 - org.ops4j.pax.web.pax-web-runtime -
7.2.11 | Unbinding bundle: [org.apache.karaf.webconsole.console [176]]
2020-05-04T08:52:19,253 | INFO | paxweb-config-2-thread-3 | ContextHandler
| 223 - org.eclipse.jetty.util - 9.4.20.v20190813 | Stopped
HttpServiceContext{httpContext=DefaultHttpContext
[bundle=org.apache.karaf.webconsole.console [176], contextID=custom]}
2020-05-04T08:52:19,301 | INFO | paxweb-config-2-thread-3 |
HttpServiceFactoryImpl | 258 - org.ops4j.pax.web.pax-web-runtime -
7.2.11 | Unbinding bundle: [org.ops4j.pax.web.pax-web-extender-whiteboard [255]]
2020-05-04T08:52:19,331 | INFO | paxweb-config-2-thread-3 |
HttpServiceFactoryImpl | 258 - org.ops4j.pax.web.pax-web-runtime -
7.2.11 | Unbinding bundle: [org.apache.karaf.webconsole.instance [180]]
2020-05-04T08:52:19,332 | INFO | paxweb-config-2-thread-3 |
HttpServiceFactoryImpl | 258 - org.ops4j.pax.web.pax-web-runtime -
7.2.11 | Unbinding bundle: [org.apache.karaf.webconsole.features [177]]
2020-05-04T08:52:19,381 | INFO | paxweb-config-2-thread-3 |
AuthenticationFilter | 63 - io.hawt.hawtio-war - 2.9.1 | Destroying
hawtio authentication filter
2020-05-04T08:52:19,417 | INFO | activator-1-thread-5 | CommandExtension
| 34 - org.apache.karaf.shell.core - 4.2.7 | Unregistering commands
for bundle org.apache.karaf.http.core/4.2.7
2020-05-04T08:52:19,433 | INFO | activator-1-thread-5 | HttpServiceFactoryImpl
| 258 - org.ops4j.pax.web.pax-web-runtime - 7.2.11 | Unbinding
bundle: [org.apache.karaf.webconsole.http [179]]
2020-05-04T08:52:19,516 | INFO | activator-1-thread-5 | HttpPlugin
| 179 - org.apache.karaf.webconsole.http - 4.2.7 | Http plugin
deactivated
2020-05-04T08:52:19,583 | INFO | paxweb-config-2-thread-3 |
HttpServiceFactoryImpl | 258 - org.ops4j.pax.web.pax-web-runtime -
7.2.11 | Unbinding bundle: [io.hawt.hawtio-war [63]]
2020-05-04T08:52:19,596 | INFO | paxweb-config-2-thread-3 |
HawtioContextListener| 63 - io.hawt.hawtio-war - 2.9.1 | Destroying
hawtio services
2020-05-04T08:52:19,597 | INFO | paxweb-config-2-thread-3 | ContextHandler
| 223 - org.eclipse.jetty.util - 9.4.20.v20190813 | Stopped
HttpServiceContext{httpContext=WebAppHttpContext{io.hawt.hawtio-war - 63}}
2020-05-04T08:52:19,598 | INFO | paxweb-config-2-thread-3 |
HttpServiceFactoryImpl | 258 - org.ops4j.pax.web.pax-web-runtime -
7.2.11 | Unbinding bundle: [org.apache.felix.webconsole.plugins.ds [156]]
2020-05-04T08:52:19,598 | INFO | paxweb-config-2-thread-3 |
HttpServiceFactoryImpl | 258 - org.ops4j.pax.web.pax-web-runtime -
7.2.11 | Unbinding bundle: [org.apache.felix.webconsole.plugins.memoryusage
[158]]
2020-05-04T08:52:19,600 | INFO | paxweb-config-2-thread-3 |
CamelHttpTransportServlet| 326 - org.apache.camel.camel-servlet - 3.0.0
| Destroyed CamelHttpTransportServlet[CamelServlet]
2020-05-04T08:52:19,600 | INFO | paxweb-config-2-thread-3 |
HttpServiceFactoryImpl | 258 - org.ops4j.pax.web.pax-web-runtime -
7.2.11 | Unbinding bundle: [isp.servletHttpComponent.xml [324]]
2020-05-04T08:52:19,615 | INFO | paxweb-config-2-thread-3 | ContextHandler
| 223 - org.eclipse.jetty.util - 9.4.20.v20190813 | Stopped
HttpServiceContext{httpContext=DefaultHttpContext
[bundle=isp.servletHttpComponent.xml [324], contextID=default]}
2020-05-04T08:52:19,617 | INFO |
[jira] [Updated] (CAMEL-15000) Using a registered ConstraintSecurityHandler in another Blueprint file causes an java.lang.IllegalStateException: STARTED
[
https://issues.apache.org/jira/browse/CAMEL-15000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-15000:
--
Description:
I've defined a Blueprint DSL file with a securityHandler configuration for
multiple paths as following
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
TSTISP001
TSTISP002
http://camel.apache.org/schema/blueprint;>
...
{code}
The use in another Blueprint DSL file as attached
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
http://camel.apache.org/schema/blueprint; streamCache="true"
useBreadcrumb="true">
https://0.0.0.0:8444/hello1?sslContextParameters=#sslContextParametershandlers=securityHandlerIsp;
/>
Hello 1
{code}
causes an error
{code:java}
2020-05-02T19:15:46,202 | ERROR | Blueprint Event Dispatcher: 1 |
BlueprintCamelContext| 92 - org.apache.camel.camel-api - 3.0.0 |
Error starting CamelContext (isp.context.user.TSTISP001) due to exception
thrown: STARTED
java.lang.IllegalStateException: STARTED
at
org.eclipse.jetty.server.handler.AbstractHandlerContainer.setServer(AbstractHandlerContainer.java:131)
~[!/:9.4.20.v20190813]
at Proxyb4d61c20_c161_4396_a800_1fa982bbaaea.setServer(Unknown Source)
~[?:?]
at
org.eclipse.jetty.server.handler.HandlerCollection.updateHandlers(HandlerCollection.java:117)
~[!/:9.4.20.v20190813]
at
org.eclipse.jetty.server.handler.HandlerCollection.addHandler(HandlerCollection.java:180)
~[!/:9.4.20.v20190813]
at
org.apache.camel.component.jetty.JettyHttpComponent.addJettyHandlers(JettyHttpComponent.java:1182)
~[!/:3.0.0]
at
org.apache.camel.component.jetty.JettyHttpComponent.createServletForConnector(JettyHttpComponent.java:1145)
~[!/:3.0.0]
at
org.apache.camel.component.jetty.JettyHttpComponent.connect(JettyHttpComponent.java:329)
~[!/:3.0.0]
at
org.apache.camel.http.common.HttpCommonEndpoint.connect(HttpCommonEndpoint.java:177)
~[!/:3.0.0]
at
org.apache.camel.http.common.HttpConsumer.doStart(HttpConsumer.java:58)
~[!/:3.0.0]
at
org.apache.camel.component.jetty.JettyHttpConsumer.doStart(JettyHttpConsumer.java:31)
~[!/:3.0.0]
at
org.apache.camel.support.service.ServiceSupport.start(ServiceSupport.java:117)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.startService(AbstractCamelContext.java:2900)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.doStartOrResumeRouteConsumers(AbstractCamelContext.java:3227)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.doStartRouteConsumers(AbstractCamelContext.java:3161)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.safelyStartRouteServices(AbstractCamelContext.java:3071)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.doStartOrResumeRoutes(AbstractCamelContext.java:2836)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.doStartCamel(AbstractCamelContext.java:2640)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.lambda$doStart$2(AbstractCamelContext.java:2445)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.doWithDefinedClassLoader(AbstractCamelContext.java:2462)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.doStart(AbstractCamelContext.java:2443)
~[!/:3.0.0]
at
org.apache.camel.support.service.ServiceSupport.start(ServiceSupport.java:117)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2352)
[!/:3.0.0]
at
org.apache.camel.blueprint.BlueprintCamelContext.start(BlueprintCamelContext.java:244)
[!/:3.0.0]
at
org.apache.camel.blueprint.BlueprintCamelContext.maybeStart(BlueprintCamelContext.java:286)
[!/:3.0.0]
at
org.apache.camel.blueprint.BlueprintCamelContext.blueprintEvent(BlueprintCamelContext.java:183)
[!/:3.0.0]
[jira] [Created] (CAMEL-15000) Using a registered ConstraintSecurityHandler in another Blueprint file causes an java.lang.IllegalStateException: STARTED
Gerald Kallas created CAMEL-15000:
-
Summary: Using a registered ConstraintSecurityHandler in another
Blueprint file causes an java.lang.IllegalStateException: STARTED
Key: CAMEL-15000
URL: https://issues.apache.org/jira/browse/CAMEL-15000
Project: Camel
Issue Type: Bug
Components: camel-jetty
Affects Versions: 3.0.1
Reporter: Gerald Kallas
I've defined a Blueprint DSL file with a securityHandler configuration for
multiple paths as following
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
TSTISP001
TSTISP002
http://camel.apache.org/schema/blueprint;>
...
{code}
The use in another Blueprint DSL file as attached
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
http://camel.apache.org/schema/blueprint; streamCache="true"
useBreadcrumb="true">
https://0.0.0.0:8444/hello1?sslContextParameters=#sslContextParametershandlers=securityHandlerIsp;
/>
Hello 1
{code}
causes an error
{code:java}
2020-05-02T19:15:46,202 | ERROR | Blueprint Event Dispatcher: 1 |
BlueprintCamelContext| 92 - org.apache.camel.camel-api - 3.0.0 |
Error starting CamelContext (isp.context.user.TSTISP001) due to exception
thrown: STARTED
java.lang.IllegalStateException: STARTED
at
org.eclipse.jetty.server.handler.AbstractHandlerContainer.setServer(AbstractHandlerContainer.java:131)
~[!/:9.4.20.v20190813]
at Proxyb4d61c20_c161_4396_a800_1fa982bbaaea.setServer(Unknown Source)
~[?:?]
at
org.eclipse.jetty.server.handler.HandlerCollection.updateHandlers(HandlerCollection.java:117)
~[!/:9.4.20.v20190813]
at
org.eclipse.jetty.server.handler.HandlerCollection.addHandler(HandlerCollection.java:180)
~[!/:9.4.20.v20190813]
at
org.apache.camel.component.jetty.JettyHttpComponent.addJettyHandlers(JettyHttpComponent.java:1182)
~[!/:3.0.0]
at
org.apache.camel.component.jetty.JettyHttpComponent.createServletForConnector(JettyHttpComponent.java:1145)
~[!/:3.0.0]
at
org.apache.camel.component.jetty.JettyHttpComponent.connect(JettyHttpComponent.java:329)
~[!/:3.0.0]
at
org.apache.camel.http.common.HttpCommonEndpoint.connect(HttpCommonEndpoint.java:177)
~[!/:3.0.0]
at
org.apache.camel.http.common.HttpConsumer.doStart(HttpConsumer.java:58)
~[!/:3.0.0]
at
org.apache.camel.component.jetty.JettyHttpConsumer.doStart(JettyHttpConsumer.java:31)
~[!/:3.0.0]
at
org.apache.camel.support.service.ServiceSupport.start(ServiceSupport.java:117)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.startService(AbstractCamelContext.java:2900)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.doStartOrResumeRouteConsumers(AbstractCamelContext.java:3227)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.doStartRouteConsumers(AbstractCamelContext.java:3161)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.safelyStartRouteServices(AbstractCamelContext.java:3071)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.doStartOrResumeRoutes(AbstractCamelContext.java:2836)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.doStartCamel(AbstractCamelContext.java:2640)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.lambda$doStart$2(AbstractCamelContext.java:2445)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.doWithDefinedClassLoader(AbstractCamelContext.java:2462)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.doStart(AbstractCamelContext.java:2443)
~[!/:3.0.0]
at
org.apache.camel.support.service.ServiceSupport.start(ServiceSupport.java:117)
~[!/:3.0.0]
at
org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2352)
[!/:3.0.0]
at
[jira] [Commented] (CAMEL-14990) camel-jetty consumers w/ different security handlers on different paths and same port don't work
[
https://issues.apache.org/jira/browse/CAMEL-14990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097345#comment-17097345
]
Gerald Kallas commented on CAMEL-14990:
---
It's quite clear now that the securityHandler is bind to a port. I've moved the
open questions to the appropriate mailing lists. The bug can be closed as
"works as designed". Thanks.
> camel-jetty consumers w/ different security handlers on different paths and
> same port don't work
>
>
> Key: CAMEL-14990
> URL: https://issues.apache.org/jira/browse/CAMEL-14990
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Minor
>
> I've created two Blueprint DSLs. The 1st one works as expected w/ basic auth.
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP001
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP001.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP001"/>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello1?handlers=securityHandler_TSTISP001; />
> ...
> {code}
> The property file TSTISP001.properties looks like
> {code:xml}
> username1=password1,TSTISP001
> {code}
> After deploying a 2nd Blueprint DSL like
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP002
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP002.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP002"/>
>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello2?handlers=securityHandler_TSTISP002; />
> ...
> {code}
> with the corresponding TSTISP002.properties file
> {code:xml}
> username2=password2,TSTISP002
> {code}
> the 2nd route works as expected.
> The 1st route doesn't have any authentication anymore after the deployment of
> the 1st route.
> A platform restart doesn't help. The 2nd route started of both has
> authentication, the 1st one is loosing the authentication.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14990) camel-jetty consumers w/ different security handlers on different paths and same port don't work
[
https://issues.apache.org/jira/browse/CAMEL-14990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097269#comment-17097269
]
Gerald Kallas edited comment on CAMEL-14990 at 5/1/20, 9:41 AM:
2nd question .. when I'm going to remove the handlers=securityHandler from the
2nd route (in the 2nd camel context) it will nevertheless remain there and
challenge the basic authentication.
{code:java}
http://camel.apache.org/schema/blueprint; streamCache="true"
useBreadcrumb="true">
https://0.0.0.0:8444/hello2?sslContextParameters=#sslContextParameters;
/>
Hello 2
{code}
The constraintMapping mapping must be explicitly removed from the
securityHandler itself. Does that mean that the securityHandler binds to the
port?
It's a very common use case that an authentication could be set on different
paths and same port in a different manner. Seems that this is not possible here?
was (Author: catshout):
2nd question .. when I'm going to remove the securityHandler from the 2nd route
(in the 2nd camel context) it will nevertheless remain there and challenge the
basic authentication.
{code:java}
http://camel.apache.org/schema/blueprint; streamCache="true"
useBreadcrumb="true">
https://0.0.0.0:8444/hello2?sslContextParameters=#sslContextParameters;
/>
Hello 2
{code}
The constraintMapping mapping must be explicitly removed from the
securityHandler itself. Does that mean that the securityHandler binds to the
port?
It's a very common use case that an authentication could be set on different
paths and same port in a different manner. Seems that this is not possible here?
> camel-jetty consumers w/ different security handlers on different paths and
> same port don't work
>
>
> Key: CAMEL-14990
> URL: https://issues.apache.org/jira/browse/CAMEL-14990
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Minor
>
> I've created two Blueprint DSLs. The 1st one works as expected w/ basic auth.
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP001
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP001.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP001"/>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello1?handlers=securityHandler_TSTISP001; />
> ...
> {code}
> The property file TSTISP001.properties looks like
> {code:xml}
> username1=password1,TSTISP001
> {code}
> After deploying a 2nd Blueprint DSL like
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP002
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
[jira] [Comment Edited] (CAMEL-14990) camel-jetty consumers w/ different security handlers on different paths and same port don't work
[
https://issues.apache.org/jira/browse/CAMEL-14990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097269#comment-17097269
]
Gerald Kallas edited comment on CAMEL-14990 at 5/1/20, 9:39 AM:
2nd question .. when I'm going to remove the securityHandler from the 2nd route
(in the 2nd camel context) it will nevertheless remain there and challenge the
basic authentication.
{code:java}
http://camel.apache.org/schema/blueprint; streamCache="true"
useBreadcrumb="true">
https://0.0.0.0:8444/hello2?sslContextParameters=#sslContextParameters;
/>
Hello 2
{code}
The constraintMapping mapping must be explicitly removed from the
securityHandler itself. Does that mean that the securityHandler binds to the
port?
It's a very common use case that an authentication could be set on different
paths and same port in a different manner. Seems that this is not possible here?
was (Author: catshout):
2nd question .. when I'm going to remove the securityHandler from the 2nd route
(in another camel context) it will nevertheless remain there and challenge the
basic authentication.
{code:java}
http://camel.apache.org/schema/blueprint; streamCache="true"
useBreadcrumb="true">
https://0.0.0.0:8444/hello2?sslContextParameters=#sslContextParameters;
/>
Hello 2
{code}
The constraintMapping mapping must be explicitly removed from the
securityHandler itself. Does that mean that the securityHandler binds to the
port?
It's a very common use case that an authentication could be set on different
paths and same port in a different manner. Seems that this is not possible here.
> camel-jetty consumers w/ different security handlers on different paths and
> same port don't work
>
>
> Key: CAMEL-14990
> URL: https://issues.apache.org/jira/browse/CAMEL-14990
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Minor
>
> I've created two Blueprint DSLs. The 1st one works as expected w/ basic auth.
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP001
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP001.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP001"/>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello1?handlers=securityHandler_TSTISP001; />
> ...
> {code}
> The property file TSTISP001.properties looks like
> {code:xml}
> username1=password1,TSTISP001
> {code}
> After deploying a 2nd Blueprint DSL like
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP002
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
[jira] [Commented] (CAMEL-14990) camel-jetty consumers w/ different security handlers on different paths and same port don't work
[
https://issues.apache.org/jira/browse/CAMEL-14990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097269#comment-17097269
]
Gerald Kallas commented on CAMEL-14990:
---
2nd question .. when I'm going to remove the securityHandler from the 2nd route
(in another camel context) it will nevertheless remain there and challenge the
basic authentication.
{code:java}
http://camel.apache.org/schema/blueprint; streamCache="true"
useBreadcrumb="true">
https://0.0.0.0:8444/hello2?sslContextParameters=#sslContextParameters;
/>
Hello 2
{code}
The constraintMapping mapping must be explicitly removed from the
securityHandler itself. Does that mean that the securityHandler binds to the
port?
It's a very common use case that an authentication could be set on different
paths and same port in a different manner. Seems that this is not possible here.
> camel-jetty consumers w/ different security handlers on different paths and
> same port don't work
>
>
> Key: CAMEL-14990
> URL: https://issues.apache.org/jira/browse/CAMEL-14990
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Minor
>
> I've created two Blueprint DSLs. The 1st one works as expected w/ basic auth.
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP001
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP001.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP001"/>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello1?handlers=securityHandler_TSTISP001; />
> ...
> {code}
> The property file TSTISP001.properties looks like
> {code:xml}
> username1=password1,TSTISP001
> {code}
> After deploying a 2nd Blueprint DSL like
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP002
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP002.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP002"/>
>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello2?handlers=securityHandler_TSTISP002; />
> ...
> {code}
> with the corresponding
[jira] [Commented] (CAMEL-14990) camel-jetty consumers w/ different security handlers on different paths and same port don't work
[
https://issues.apache.org/jira/browse/CAMEL-14990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097262#comment-17097262
]
Gerald Kallas commented on CAMEL-14990:
---
Tx [~davsclaus]. Following your comment I've created a Blueprint DSL that works
as expected. It contains
* 2 different constraintMappings w/ a constraint each referring to a dedicated
path
* 1 securityHandler that includes both contraintMappings
* 2 different camel contexts w/ a route each listening on same port and on a
different path
With this approach the authentication works. See the Blueprint DSL below.
One question ..
Is there a way to externalize the constraint / constraintMapping /
securityHandler configuration to another Blueprint DSL file and refer to it (as
the same w/ sslContextParameters) in the Blueprint DSL files containing the
camel context / camel routes? I tried several ways but no one works.
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
TSTISP001
TSTISP002
http://camel.apache.org/schema/blueprint; streamCache="true"
useBreadcrumb="true">
https://0.0.0.0:8444/hello1?sslContextParameters=#sslContextParametershandlers=securityHandler;
/>
Hello 1
http://camel.apache.org/schema/blueprint; streamCache="true"
useBreadcrumb="true">
https://0.0.0.0:8444/hello2?sslContextParameters=#sslContextParametershandlers=securityHandler;
/>
Hello 2
{code}
> camel-jetty consumers w/ different security handlers on different paths and
> same port don't work
>
>
> Key: CAMEL-14990
> URL: https://issues.apache.org/jira/browse/CAMEL-14990
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Minor
>
> I've created two Blueprint DSLs. The 1st one works as expected w/ basic auth.
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP001
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP001.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP001"/>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello1?handlers=securityHandler_TSTISP001; />
> ...
> {code}
> The property file TSTISP001.properties looks like
> {code:xml}
> username1=password1,TSTISP001
> {code}
> After deploying a 2nd Blueprint DSL like
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
>
[jira] [Updated] (CAMEL-14990) camel-jetty consumers w/ different security handlers on different paths and same port don't work
[
https://issues.apache.org/jira/browse/CAMEL-14990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14990:
--
Summary: camel-jetty consumers w/ different security handlers on different
paths and same port don't work (was: camel-jetty multiple consumer auth w/
different paths and security handlers on same port doesn't work)
> camel-jetty consumers w/ different security handlers on different paths and
> same port don't work
>
>
> Key: CAMEL-14990
> URL: https://issues.apache.org/jira/browse/CAMEL-14990
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Critical
>
> I've created two Blueprint DSLs. The 1st one works as expected w/ basic auth.
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP001
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP001.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP001"/>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello1?handlers=securityHandler_TSTISP001; />
> ...
> {code}
> The property file TSTISP001.properties looks like
> {code:xml}
> username1=password1,TSTISP001
> {code}
> After deploying a 2nd Blueprint DSL like
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP002
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP002.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP002"/>
>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello2?handlers=securityHandler_TSTISP002; />
> ...
> {code}
> with the corresponding TSTISP002.properties file
> {code:xml}
> username2=password2,TSTISP002
> {code}
> the 2nd route works as expected.
> The 1st route doesn't have any authentication anymore after the deployment of
> the 1st route.
> A platform restart doesn't help. The 2nd route started of both has
> authentication, the 1st one is loosing the authentication.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14990) camel-jetty multiple consumer auth w/ different paths and security handlers on same port doesn't work
[
https://issues.apache.org/jira/browse/CAMEL-14990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14990:
--
Summary: camel-jetty multiple consumer auth w/ different paths and security
handlers on same port doesn't work (was: camel-jetty multiple consumer auth w/
different paths and security handlers on same port don't work)
> camel-jetty multiple consumer auth w/ different paths and security handlers
> on same port doesn't work
> -
>
> Key: CAMEL-14990
> URL: https://issues.apache.org/jira/browse/CAMEL-14990
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Critical
>
> I've created two Blueprint DSLs. The 1st one works as expected w/ basic auth.
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP001
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP001.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP001"/>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello1?handlers=securityHandler_TSTISP001; />
> ...
> {code}
> The property file TSTISP001.properties looks like
> {code:xml}
> username1=password1,TSTISP001
> {code}
> After deploying a 2nd Blueprint DSL like
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP002
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP002.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP002"/>
>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello2?handlers=securityHandler_TSTISP002; />
> ...
> {code}
> with the corresponding TSTISP002.properties file
> {code:xml}
> username2=password2,TSTISP002
> {code}
> the 2nd route works as expected.
> The 1st route doesn't have any authentication anymore after the deployment of
> the 1st route.
> A platform restart doesn't help. The 2nd route started of both has
> authentication, the 1st one is loosing the authentication.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14990) camel-jetty multiple consumer auth w/ different paths and security handlers on same port don't work
[
https://issues.apache.org/jira/browse/CAMEL-14990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14990:
--
Summary: camel-jetty multiple consumer auth w/ different paths and security
handlers on same port don't work (was: camel-jetty consumers auth w/ different
paths and security handlers don't work)
> camel-jetty multiple consumer auth w/ different paths and security handlers
> on same port don't work
> ---
>
> Key: CAMEL-14990
> URL: https://issues.apache.org/jira/browse/CAMEL-14990
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Critical
>
> I've created two Blueprint DSLs. The 1st one works as expected w/ basic auth.
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP001
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP001.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP001"/>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello1?handlers=securityHandler_TSTISP001; />
> ...
> {code}
> The property file TSTISP001.properties looks like
> {code:xml}
> username1=password1,TSTISP001
> {code}
> After deploying a 2nd Blueprint DSL like
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP002
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP002.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP002"/>
>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello2?handlers=securityHandler_TSTISP002; />
> ...
> {code}
> with the corresponding TSTISP002.properties file
> {code:xml}
> username2=password2,TSTISP002
> {code}
> the 2nd route works as expected.
> The 1st route doesn't have any authentication anymore after the deployment of
> the 1st route.
> A platform restart doesn't help. The 2nd route started of both has
> authentication, the 1st one is loosing the authentication.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14990) camel-jetty consumers auth w/ different paths and security handlers don't work
[
https://issues.apache.org/jira/browse/CAMEL-14990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17096653#comment-17096653
]
Gerald Kallas edited comment on CAMEL-14990 at 4/30/20, 3:29 PM:
-
I added even a different realm name to each, no success.
{code:}
{code}
and
{code:}
{code}
was (Author: catshout):
I added even a different realm name to each, no success.
{code:}
{code}
and
{code:}
{code}
> camel-jetty consumers auth w/ different paths and security handlers don't work
> --
>
> Key: CAMEL-14990
> URL: https://issues.apache.org/jira/browse/CAMEL-14990
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Critical
>
> I've created two Blueprint DSLs. The 1st one works as expected w/ basic auth.
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP001
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP001.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP001"/>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello1?handlers=securityHandler_TSTISP001; />
> ...
> {code}
> The property file TSTISP001.properties looks like
> {code:xml}
> username1=password1,TSTISP001
> {code}
> After deploying a 2nd Blueprint DSL like
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP002
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP002.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP002"/>
>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello2?handlers=securityHandler_TSTISP002; />
> ...
> {code}
> with the corresponding TSTISP002.properties file
> {code:xml}
> username2=password2,TSTISP002
> {code}
> the 2nd route works as expected.
> The 1st route doesn't have any authentication anymore after the deployment of
> the 1st route.
> A platform restart doesn't help. The 2nd route started of both has
> authentication, the 1st one is loosing the authentication.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14990) camel-jetty consumers auth w/ different paths and security handlers don't work
[
https://issues.apache.org/jira/browse/CAMEL-14990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17096653#comment-17096653
]
Gerald Kallas commented on CAMEL-14990:
---
I added even a different realm name to each, no success.
{code:}
{code}
and
{code:}
{code}
> camel-jetty consumers auth w/ different paths and security handlers don't work
> --
>
> Key: CAMEL-14990
> URL: https://issues.apache.org/jira/browse/CAMEL-14990
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Critical
>
> I've created two Blueprint DSLs. The 1st one works as expected w/ basic auth.
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP001
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP001.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP001"/>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello1?handlers=securityHandler_TSTISP001; />
> ...
> {code}
> The property file TSTISP001.properties looks like
> {code:xml}
> username1=password1,TSTISP001
> {code}
> After deploying a 2nd Blueprint DSL like
> {code:xml}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>
> xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
>
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP002
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP002.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP002"/>
>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello2?handlers=securityHandler_TSTISP002; />
> ...
> {code}
> with the corresponding TSTISP002.properties file
> {code:xml}
> username2=password2,TSTISP002
> {code}
> the 2nd route works as expected.
> The 1st route doesn't have any authentication anymore after the deployment of
> the 1st route.
> A platform restart doesn't help. The 2nd route started of both has
> authentication, the 1st one is loosing the authentication.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14990) camel-jetty consumers auth w/ different paths and security handlers don't work
[
https://issues.apache.org/jira/browse/CAMEL-14990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14990:
--
Description:
I've created two Blueprint DSLs. The 1st one works as expected w/ basic auth.
{code:xml}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
TSTISP001
http://camel.apache.org/schema/blueprint;
streamCache="true" useBreadcrumb="true">
http://0.0.0.0:8182/hello1?handlers=securityHandler_TSTISP001; />
...
{code}
The property file TSTISP001.properties looks like
{code:xml}
username1=password1,TSTISP001
{code}
After deploying a 2nd Blueprint DSL like
{code:xml}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
TSTISP002
http://camel.apache.org/schema/blueprint;
streamCache="true" useBreadcrumb="true">
http://0.0.0.0:8182/hello2?handlers=securityHandler_TSTISP002; />
...
{code}
with the corresponding TSTISP002.properties file
{code:xml}
username2=password2,TSTISP002
{code}
the 2nd route works as expected.
The 1st route doesn't have any authentication anymore after the deployment of
the 1st route.
A platform restart doesn't help. The 2nd route started of both has
authentication, the 1st one is loosing the authentication.
was:
I've created to Blueprint DSLs. The 1st one works as expected w/ basic auth.
{code:xml}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
TSTISP001
http://camel.apache.org/schema/blueprint;
streamCache="true" useBreadcrumb="true">
http://0.0.0.0:8182/hello1?handlers=securityHandler_TSTISP001; />
...
{code}
The property file TSTISP001.properties looks like
{code:xml}
username1=password1,TSTISP001
{code}
After deploying a 2nd Blueprint DSL like
{code:xml}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
[jira] [Updated] (CAMEL-14990) camel-jetty consumers auth w/ different paths and security handlers don't work
[
https://issues.apache.org/jira/browse/CAMEL-14990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14990:
--
Description:
I've created to Blueprint DSLs. The 1st one works as expected w/ basic auth.
{code:xml}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
TSTISP001
http://camel.apache.org/schema/blueprint;
streamCache="true" useBreadcrumb="true">
http://0.0.0.0:8182/hello1?handlers=securityHandler_TSTISP001; />
...
{code}
The property file TSTISP001.properties looks like
{code:xml}
username1=password1,TSTISP001
{code}
After deploying a 2nd Blueprint DSL like
{code:xml}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
TSTISP002
http://camel.apache.org/schema/blueprint;
streamCache="true" useBreadcrumb="true">
http://0.0.0.0:8182/hello2?handlers=securityHandler_TSTISP002; />
...
{code}
with the corresponding TSTISP002.properties file
{code:xml}
username2=password2,TSTISP002
{code}
the 2nd route works as expected.
The 1st route doesn't have any authentication anymore after the deployment of
the 1st route.
A platform restart doesn't help. The 2nd route started of both has
authentication, the 1st one is loosing the authentication.
was:
I've created to Blueprint DSLs. The 1st one works as expected w/ basic auth.
{code:xml}
...
TSTISP001
http://camel.apache.org/schema/blueprint;
streamCache="true" useBreadcrumb="true">
http://0.0.0.0:8182/hello1?handlers=securityHandler_TSTISP001; />
...
{code}
The property file TSTISP001.properties looks like
{code:xml}
username1=password1,TSTISP001
{code}
After deploying a 2nd Blueprint DSL like
{code:xml}
...
TSTISP002
http://camel.apache.org/schema/blueprint;
streamCache="true" useBreadcrumb="true">
[jira] [Updated] (CAMEL-14990) camel-jetty consumers auth w/ different paths and security handlers don't work
[
https://issues.apache.org/jira/browse/CAMEL-14990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14990:
--
Summary: camel-jetty consumers auth w/ different paths and security
handlers don't work (was: camel-jetty consumer auth w/ different paths and
security handlers don't work)
> camel-jetty consumers auth w/ different paths and security handlers don't work
> --
>
> Key: CAMEL-14990
> URL: https://issues.apache.org/jira/browse/CAMEL-14990
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Critical
>
> I've created to Blueprint DSLs. The 1st one works as expected w/ basic auth.
> {code:xml}
> ...
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP001
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP001.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP001"/>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello1?handlers=securityHandler_TSTISP001; />
> ...
> {code}
> The property file TSTISP001.properties looks like
> {code:xml}
> username1=password1,TSTISP001
> {code}
> After deploying a 2nd Blueprint DSL like
> {code:xml}
> ...
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP002
>
>
>
>class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
>class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
>class="org.eclipse.jetty.security.HashLoginService">
>value="/opt/apache-karaf/etc/TSTISP002.properties"/>
>
>
>
>class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>component-id="constraintMapping_TSTISP002"/>
>
>
>
>
> http://camel.apache.org/schema/blueprint;
> streamCache="true" useBreadcrumb="true">
>
>uri="jetty:http://0.0.0.0:8182/hello2?handlers=securityHandler_TSTISP002; />
> ...
> {code}
> with the corresponding TSTISP002.properties
> {code:xml}
> username2=password2,TSTISP002
> {code}
> the 2nd route works as expected.
> The 1st route doesn't have any authentication anymore.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-14990) camel-jetty consumer auth w/ different paths and security handlers don't work
Gerald Kallas created CAMEL-14990:
-
Summary: camel-jetty consumer auth w/ different paths and security
handlers don't work
Key: CAMEL-14990
URL: https://issues.apache.org/jira/browse/CAMEL-14990
Project: Camel
Issue Type: Bug
Components: camel-jetty
Affects Versions: 3.0.1
Reporter: Gerald Kallas
I've created to Blueprint DSLs. The 1st one works as expected w/ basic auth.
{code:xml}
...
TSTISP001
http://camel.apache.org/schema/blueprint;
streamCache="true" useBreadcrumb="true">
http://0.0.0.0:8182/hello1?handlers=securityHandler_TSTISP001; />
...
{code}
The property file TSTISP001.properties looks like
{code:xml}
username1=password1,TSTISP001
{code}
After deploying a 2nd Blueprint DSL like
{code:xml}
...
TSTISP002
http://camel.apache.org/schema/blueprint;
streamCache="true" useBreadcrumb="true">
http://0.0.0.0:8182/hello2?handlers=securityHandler_TSTISP002; />
...
{code}
with the corresponding TSTISP002.properties
{code:xml}
username2=password2,TSTISP002
{code}
the 2nd route works as expected.
The 1st route doesn't have any authentication anymore.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14990) camel-jetty consumers auth w/ different paths and security handlers don't work
[
https://issues.apache.org/jira/browse/CAMEL-14990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14990:
--
Description:
I've created to Blueprint DSLs. The 1st one works as expected w/ basic auth.
{code:xml}
...
TSTISP001
http://camel.apache.org/schema/blueprint;
streamCache="true" useBreadcrumb="true">
http://0.0.0.0:8182/hello1?handlers=securityHandler_TSTISP001; />
...
{code}
The property file TSTISP001.properties looks like
{code:xml}
username1=password1,TSTISP001
{code}
After deploying a 2nd Blueprint DSL like
{code:xml}
...
TSTISP002
http://camel.apache.org/schema/blueprint;
streamCache="true" useBreadcrumb="true">
http://0.0.0.0:8182/hello2?handlers=securityHandler_TSTISP002; />
...
{code}
with the corresponding TSTISP002.properties file
{code:xml}
username2=password2,TSTISP002
{code}
the 2nd route works as expected.
The 1st route doesn't have any authentication anymore.
was:
I've created to Blueprint DSLs. The 1st one works as expected w/ basic auth.
{code:xml}
...
TSTISP001
http://camel.apache.org/schema/blueprint;
streamCache="true" useBreadcrumb="true">
http://0.0.0.0:8182/hello1?handlers=securityHandler_TSTISP001; />
...
{code}
The property file TSTISP001.properties looks like
{code:xml}
username1=password1,TSTISP001
{code}
After deploying a 2nd Blueprint DSL like
{code:xml}
...
TSTISP002
http://camel.apache.org/schema/blueprint;
streamCache="true" useBreadcrumb="true">
http://0.0.0.0:8182/hello2?handlers=securityHandler_TSTISP002; />
...
{code}
with the corresponding TSTISP002.properties
{code:xml}
username2=password2,TSTISP002
{code}
the 2nd route works as expected.
The 1st route doesn't have any authentication anymore.
> camel-jetty consumers auth w/ different paths and security handlers don't work
> --
>
> Key: CAMEL-14990
> URL: https://issues.apache.org/jira/browse/CAMEL-14990
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Critical
>
> I've created to Blueprint DSLs. The 1st one works as expected w/ basic auth.
> {code:xml}
> ...
>
>class="org.eclipse.jetty.util.security.Constraint">
>
>
>
>
> TSTISP001
>
>
>
>
[jira] [Updated] (CAMEL-14971) HTTP producer NTLM auth shows "Cannot locate default realm" WARN
[
https://issues.apache.org/jira/browse/CAMEL-14971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14971:
--
Summary: HTTP producer NTLM auth shows "Cannot locate default realm" WARN
(was: HTTP producer NTLM auth shows an "Cannot locate default realm" WARN)
> HTTP producer NTLM auth shows "Cannot locate default realm" WARN
>
>
> Key: CAMEL-14971
> URL: https://issues.apache.org/jira/browse/CAMEL-14971
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Minor
>
> See below a route that calls an endpoint with NTLM auth.
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>http://camel.apache.org/schema/blueprint;>
>
>
>
> GET
>
> uri="http://host?authMethod=NTLMauthDomain=xxxauthHost=xxxauthUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
> />
>
>
>
> {code}
>
> When starting the route than I'm getting an error (Camel WARN)
> {code:java}
> 2020-04-23T22:36:31,980 | WARN | qtp711860658-153 | HttpAuthenticator
> | 164 - org.apache.httpcomponents.httpclient - 4.5.10 | NEGOTIATE
> authentication error: Invalid name provided (Mechanism level: KrbException:
> Cannot locate default realm){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14971) HTTP producer NTLM auth shows an "Cannot locate default realm" WARN
[
https://issues.apache.org/jira/browse/CAMEL-14971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14971:
--
Description:
See below a route that calls an endpoint with NTLM auth.
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
GET
http://host?authMethod=NTLMauthDomain=xxxauthHost=xxxauthUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
When starting the route than I'm getting an error (Camel WARN)
{code:java}
2020-04-23T22:36:31,980 | WARN | qtp711860658-153 | HttpAuthenticator
| 164 - org.apache.httpcomponents.httpclient - 4.5.10 | NEGOTIATE
authentication error: Invalid name provided (Mechanism level: KrbException:
Cannot locate default realm){code}
was:
See below a route that calls an endpoint with NTLM auth.
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
GET
http://host?authMethod=NTLMauthDomain=xxxauthHost=xxxauthUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
When starting the route than I'm getting an error (Camel WARN)
{code:java}
2020-04-23T22:36:31,980 | WARN | qtp711860658-153 | HttpAuthenticator
| 164 - org.apache.httpcomponents.httpclient - 4.5.10 | NEGOTIATE
authentication error: Invalid name provided (Mechanism level: KrbException:
Cannot locate default realm){code}
> HTTP producer NTLM auth shows an "Cannot locate default realm" WARN
> ---
>
> Key: CAMEL-14971
> URL: https://issues.apache.org/jira/browse/CAMEL-14971
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Minor
>
> See below a route that calls an endpoint with NTLM auth.
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>http://camel.apache.org/schema/blueprint;>
>
>
>
> GET
>
> uri="http://host?authMethod=NTLMauthDomain=xxxauthHost=xxxauthUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
> />
>
>
>
> {code}
>
> When starting the route than I'm getting an error (Camel WARN)
> {code:java}
> 2020-04-23T22:36:31,980 | WARN | qtp711860658-153 | HttpAuthenticator
> | 164 - org.apache.httpcomponents.httpclient - 4.5.10 | NEGOTIATE
> authentication error: Invalid name provided (Mechanism level: KrbException:
> Cannot locate default realm){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14971) HTTP producer NTLM auth shows an "Cannot locate default realm" WARN
[
https://issues.apache.org/jira/browse/CAMEL-14971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14971:
--
Description:
See below a route that calls an endpoint with NTLM auth.
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
GET
http://host?authMethod=NTLMauthDomain=xxxauthHost=xxxauthUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
When starting the route than I'm getting an error (Camel WARN)
{code:java}
2020-04-23T22:36:31,980 | WARN | qtp711860658-153 | HttpAuthenticator
| 164 - org.apache.httpcomponents.httpclient - 4.5.10 | NEGOTIATE
authentication error: Invalid name provided (Mechanism level: KrbException:
Cannot locate default realm){code}
was:
See below a route that calls an endpoint with NTLM auth. It works pretty when
calling the route on a HTTP consumer endpoint.
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/NTLM; />
GET
http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
When the consumer changed from HTTP consumer to Timer consumer like
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
GET
http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
than I'm getting an error
{code:java}
2020-04-23T22:36:31,980 | WARN | qtp711860658-153 | HttpAuthenticator
| 164 - org.apache.httpcomponents.httpclient - 4.5.10 | NEGOTIATE
authentication error: Invalid name provided (Mechanism level: KrbException:
Cannot locate default realm){code}
> HTTP producer NTLM auth shows an "Cannot locate default realm" WARN
> ---
>
> Key: CAMEL-14971
> URL: https://issues.apache.org/jira/browse/CAMEL-14971
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Minor
>
> See below a route that calls an endpoint with NTLM auth.
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>http://camel.apache.org/schema/blueprint;>
>
>
>
> GET
>
> uri="http://host?authMethod=NTLMauthDomain=xxxauthHost=xxxauthUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
> />
>
>
>
> {code}
>
> When starting the route than I'm getting an error (Camel WARN)
>
> {code:java}
> 2020-04-23T22:36:31,980 | WARN | qtp711860658-153 | HttpAuthenticator
> | 164 - org.apache.httpcomponents.httpclient - 4.5.10 | NEGOTIATE
> authentication error: Invalid name provided (Mechanism level: KrbException:
> Cannot locate default realm){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14971) HTTP producer NTLM auth shows an "Cannot locate default realm" WARN
[
https://issues.apache.org/jira/browse/CAMEL-14971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14971:
--
Summary: HTTP producer NTLM auth shows an "Cannot locate default realm"
WARN (was: HTTP producer NTLM auth shows an )
> HTTP producer NTLM auth shows an "Cannot locate default realm" WARN
> ---
>
> Key: CAMEL-14971
> URL: https://issues.apache.org/jira/browse/CAMEL-14971
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Minor
>
> See below a route that calls an endpoint with NTLM auth. It works pretty when
> calling the route on a HTTP consumer endpoint.
>
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/NTLM; />
>
> GET
>
> uri="http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
> />
>
>
> {code}
>
> When the consumer changed from HTTP consumer to Timer consumer like
>
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>http://camel.apache.org/schema/blueprint;>
>
>
>
> GET
>
> uri="http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
> />
>
>
>
> {code}
>
> than I'm getting an error
>
> {code:java}
> 2020-04-23T22:36:31,980 | WARN | qtp711860658-153 | HttpAuthenticator
> | 164 - org.apache.httpcomponents.httpclient - 4.5.10 | NEGOTIATE
> authentication error: Invalid name provided (Mechanism level: KrbException:
> Cannot locate default realm){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14971) HTTP producer NTLM auth shows an
[
https://issues.apache.org/jira/browse/CAMEL-14971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14971:
--
Summary: HTTP producer NTLM auth shows an (was: HTTP producer NTLM auth
behavior depends on consumer)
> HTTP producer NTLM auth shows an
> -
>
> Key: CAMEL-14971
> URL: https://issues.apache.org/jira/browse/CAMEL-14971
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Minor
>
> See below a route that calls an endpoint with NTLM auth. It works pretty when
> calling the route on a HTTP consumer endpoint.
>
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/NTLM; />
>
> GET
>
> uri="http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
> />
>
>
> {code}
>
> When the consumer changed from HTTP consumer to Timer consumer like
>
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>http://camel.apache.org/schema/blueprint;>
>
>
>
> GET
>
> uri="http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
> />
>
>
>
> {code}
>
> than I'm getting an error
>
> {code:java}
> 2020-04-23T22:36:31,980 | WARN | qtp711860658-153 | HttpAuthenticator
> | 164 - org.apache.httpcomponents.httpclient - 4.5.10 | NEGOTIATE
> authentication error: Invalid name provided (Mechanism level: KrbException:
> Cannot locate default realm){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14971) HTTP producer NTLM auth behavior depends on consumer
[
https://issues.apache.org/jira/browse/CAMEL-14971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17093234#comment-17093234
]
Gerald Kallas commented on CAMEL-14971:
---
I was executing a couple more tests. First of all I was seen the same error
(Camel WARN) as well when using the Timer Consumer. So far the ticket is
misleading and I changed the title and description accordingly.
The error refers to the point that either the krb5.conf file isn't found or
contains the wrong configuration. See for that
[https://docs.oracle.com/javase/8/docs/technotes/guides/security/jgss/tutorials/KerberosReq.html]
If you're going to provide both, realm and kdc in the system.properties file
like
{code:java}
java.security.krb5.realm=EXAMPLE.COM
java.security.krb5.kdc=example.com
{code}
than an other error (Camel WARN) occurs
{code:java}
2020-04-27T09:07:31,480 | WARN | Camel thread #9 - timer://default |
HttpAuthenticator| 164 - org.apache.httpcomponents.httpclient -
4.5.10 | NEGOTIATE authentication error: No valid credentials provided
(Mechanism level: No valid credentials provided (Mechanism level: Failed to
find any Kerberos tgt))
{code}
The content will be properly shown while testing against an IIS instance.
I'll proceed with the tests against other targets.
> HTTP producer NTLM auth behavior depends on consumer
>
>
> Key: CAMEL-14971
> URL: https://issues.apache.org/jira/browse/CAMEL-14971
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Minor
>
> See below a route that calls an endpoint with NTLM auth. It works pretty when
> calling the route on a HTTP consumer endpoint.
>
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/NTLM; />
>
> GET
>
> uri="http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
> />
>
>
> {code}
>
> When the consumer changed from HTTP consumer to Timer consumer like
>
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>http://camel.apache.org/schema/blueprint;>
>
>
>
> GET
>
> uri="http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
> />
>
>
>
> {code}
>
> than I'm getting an error
>
> {code:java}
> 2020-04-23T22:36:31,980 | WARN | qtp711860658-153 | HttpAuthenticator
> | 164 - org.apache.httpcomponents.httpclient - 4.5.10 | NEGOTIATE
> authentication error: Invalid name provided (Mechanism level: KrbException:
> Cannot locate default realm){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14971) HTTP producer NTLM auth behavior depends on consumer
[
https://issues.apache.org/jira/browse/CAMEL-14971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14971:
--
Description:
See below a route that calls an endpoint with NTLM auth. It works pretty when
calling the route on a HTTP consumer endpoint.
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/NTLM; />
GET
http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
When the consumer changed from HTTP consumer to Timer consumer like
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
GET
http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
than I'm getting an error
{code:java}
2020-04-23T22:36:31,980 | WARN | qtp711860658-153 | HttpAuthenticator
| 164 - org.apache.httpcomponents.httpclient - 4.5.10 | NEGOTIATE
authentication error: Invalid name provided (Mechanism level: KrbException:
Cannot locate default realm){code}
was:
See below a route that calls an endpoint with NTLM auth. It works pretty when
calling the route on a HTTP consumer endpoint.
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/NTLM; />
GET
http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
When the consumer changed from HTTP consumer to Timer consumer like
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
GET
http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
than I'm getting an error
{code:java}
2020-04-23T22:36:31,980 | WARN | qtp711860658-153 | HttpAuthenticator
| 164 - org.apache.httpcomponents.httpclient - 4.5.10 | NEGOTIATE
authentication error: Invalid name provided (Mechanism level: KrbException:
Cannot locate default realm){code}
> HTTP producer NTLM auth behavior depends on consumer
>
>
> Key: CAMEL-14971
> URL: https://issues.apache.org/jira/browse/CAMEL-14971
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Minor
>
> See below a route that calls an endpoint with NTLM auth. It works pretty when
> calling the route on a HTTP consumer endpoint.
>
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/NTLM; />
>
> GET
>
> uri="http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
> />
>
>
> {code}
>
> When the consumer changed from HTTP consumer to Timer consumer like
>
>
[jira] [Updated] (CAMEL-14971) HTTP producer NTLM auth behavior depends on consumer
[
https://issues.apache.org/jira/browse/CAMEL-14971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14971:
--
Description:
See below a route that calls an endpoint with NTLM auth. It works pretty when
calling the route on a HTTP consumer endpoint.
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/NTLM; />
GET
http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
When the consumer changed from HTTP consumer to Timer consumer like
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
GET
http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
than I'm getting an error
{code:java}
2020-04-23T22:36:31,980 | WARN | qtp711860658-153 | HttpAuthenticator
| 164 - org.apache.httpcomponents.httpclient - 4.5.10 | NEGOTIATE
authentication error: Invalid name provided (Mechanism level: KrbException:
Cannot locate default realm){code}
was:
See below a route that calls an endpoint with NTLM auth. It works pretty when
calling the route on a HTTP consumer endpoint.
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/NTLM; />
GET
http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
When the consumer changed from HTTP consumer to Timer consumer like
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
GET
http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
than I'm getting an error
{code:java}
2020-04-23T22:36:31,980 | WARN | qtp711860658-153 | HttpAuthenticator
| 164 - org.apache.httpcomponents.httpclient - 4.5.10 | NEGOTIATE
authentication error: Invalid name provided (Mechanism level: KrbException:
Cannot locate default realm){code}
> HTTP producer NTLM auth behavior depends on consumer
>
>
> Key: CAMEL-14971
> URL: https://issues.apache.org/jira/browse/CAMEL-14971
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Minor
>
> See below a route that calls an endpoint with NTLM auth. It works pretty when
> calling the route on a HTTP consumer endpoint.
>
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/NTLM; />
>
> GET
>
> uri="http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
> />
>
>
> {code}
>
> When the consumer changed from HTTP consumer to Timer consumer like
>
>
[jira] [Updated] (CAMEL-14971) HTTP producer NTLM auth behavior depends on consumer
[
https://issues.apache.org/jira/browse/CAMEL-14971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14971:
--
Description:
See below a route that calls an endpoint with NTLM auth. It works pretty when
calling the route on a HTTP consumer endpoint.
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/NTLM; />
GET
http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
When the consumer changed from HTTP consumer to Timer consumer like
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
GET
http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
than I'm getting an error
{code:java}
2020-04-23T22:36:31,980 | WARN | qtp711860658-153 | HttpAuthenticator
| 164 - org.apache.httpcomponents.httpclient - 4.5.10 | NEGOTIATE
authentication error: Invalid name provided (Mechanism level: KrbException:
Cannot locate default realm){code}
was:
See below a route that calls an endpoint with NTLM auth. It works pretty when
calling the route on a HTTP consumer endpoint.
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/NTLM; />
GET
http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
When the consumer changed from HTTP consumer to Timer consumer like
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
GET
http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
than I'm getting an error
{code:java}
2020-04-23T22:36:31,980 | WARN | qtp711860658-153 | HttpAuthenticator
| 164 - org.apache.httpcomponents.httpclient - 4.5.10 | NEGOTIATE
authentication error: Invalid name provided (Mechanism level: KrbException:
Cannot locate default realm){code}
> HTTP producer NTLM auth behavior depends on consumer
>
>
> Key: CAMEL-14971
> URL: https://issues.apache.org/jira/browse/CAMEL-14971
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Major
>
> See below a route that calls an endpoint with NTLM auth. It works pretty when
> calling the route on a HTTP consumer endpoint.
>
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/NTLM; />
>
> GET
>
> uri="http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
> />
>
>
> {code}
>
> When the consumer changed from HTTP consumer to Timer consumer like
>
>
[jira] [Created] (CAMEL-14971) HTTP producer NTLM auth behavior depends on consumer
Gerald Kallas created CAMEL-14971:
-
Summary: HTTP producer NTLM auth behavior depends on consumer
Key: CAMEL-14971
URL: https://issues.apache.org/jira/browse/CAMEL-14971
Project: Camel
Issue Type: Bug
Components: camel-http
Affects Versions: 3.0.1
Reporter: Gerald Kallas
See below a route that calls an endpoint with NTLM auth. It works pretty when
calling the route on a HTTP consumer endpoint.
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/NTLM; />
GET
http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
When the consumer changed from HTTP consumer to Timer consumer like
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
GET
http://host?bridgeEndpoint=trueauthMethod=NTLMauthDomain=authUsername=xxxauthPassword=xxxthrowExceptionOnFailure=false;
/>
{code}
than I'm getting an error
{code:java}
2020-04-23T22:36:31,980 | WARN | qtp711860658-153 | HttpAuthenticator
| 164 - org.apache.httpcomponents.httpclient - 4.5.10 | NEGOTIATE
authentication error: Invalid name provided (Mechanism level: KrbException:
Cannot locate default realm){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14843) Outdated documentation for camel-jetty Basic Authentication
[
https://issues.apache.org/jira/browse/CAMEL-14843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17081899#comment-17081899
]
Gerald Kallas commented on CAMEL-14843:
---
[~acosentino] just opened the PR.
> Outdated documentation for camel-jetty Basic Authentication
> ---
>
> Key: CAMEL-14843
> URL: https://issues.apache.org/jira/browse/CAMEL-14843
> Project: Camel
> Issue Type: Improvement
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Major
> Fix For: 3.3.0
>
>
> The documentation for camel-jetty seems to be outdated as the HTTP Basic
> Authentication sample doesn't work as described. See the route below.
> I followed the documentation
> [https://camel.apache.org/components/latest/jetty-component.html]
> 2 observations
> * Unresolved requirements: [[WEBISP001.xml [264](R 264.12)]
> osgi.wiring.package; (osgi.wiring.package=org.eclipse.jetty.http.security)]
> * org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
> not allowed to appear in element 'ref'.
> The documentation should be updated to provide a working configuration for
> Camel 3.x
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>
>
>
>
>
> class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
> class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
> class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/hello; />
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14843) Outdated documentation for camel-jetty Basic Authentication
[
https://issues.apache.org/jira/browse/CAMEL-14843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17081854#comment-17081854
]
Gerald Kallas commented on CAMEL-14843:
---
[~davsclaus] I've updated the camel-jetty documentation with Blueprint code
samples für SSL context parameter definition and security configuration for
basic authentication. I've created a fork ready for review and merge. Thanks
[~arunmannuru], it's already done.
> Outdated documentation for camel-jetty Basic Authentication
> ---
>
> Key: CAMEL-14843
> URL: https://issues.apache.org/jira/browse/CAMEL-14843
> Project: Camel
> Issue Type: Improvement
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Major
> Fix For: 3.3.0
>
>
> The documentation for camel-jetty seems to be outdated as the HTTP Basic
> Authentication sample doesn't work as described. See the route below.
> I followed the documentation
> [https://camel.apache.org/components/latest/jetty-component.html]
> 2 observations
> * Unresolved requirements: [[WEBISP001.xml [264](R 264.12)]
> osgi.wiring.package; (osgi.wiring.package=org.eclipse.jetty.http.security)]
> * org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
> not allowed to appear in element 'ref'.
> The documentation should be updated to provide a working configuration for
> Camel 3.x
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>
>
>
>
>
> class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
> class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
> class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/hello; />
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14843) Outdated documentation for camel-jetty Basic Authentication
[
https://issues.apache.org/jira/browse/CAMEL-14843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17075828#comment-17075828
]
Gerald Kallas commented on CAMEL-14843:
---
Added the list of roles. Now it works like a charm.
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
hello
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/hello?handlers=securityHandler"/>
{code}
[~davsclaus] may be worth a documentation update because something in Jetty9
has changed?
> Outdated documentation for camel-jetty Basic Authentication
> ---
>
> Key: CAMEL-14843
> URL: https://issues.apache.org/jira/browse/CAMEL-14843
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Major
>
> The documentation for camel-jetty seems to be outdated as the HTTP Basic
> Authentication sample doesn't work as described. See the route below.
> I followed the documentation
> [https://camel.apache.org/components/latest/jetty-component.html]
> 2 observations
> * Unresolved requirements: [[WEBISP001.xml [264](R 264.12)]
> osgi.wiring.package; (osgi.wiring.package=org.eclipse.jetty.http.security)]
> * org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
> not allowed to appear in element 'ref'.
> The documentation should be updated to provide a working configuration for
> Camel 3.x
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>
>
>
>
>
> class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
> class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
> class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/hello; />
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14843) Outdated documentation for camel-jetty Basic Authentication
[
https://issues.apache.org/jira/browse/CAMEL-14843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17075824#comment-17075824
]
Gerald Kallas edited comment on CAMEL-14843 at 4/5/20, 12:54 PM:
-
Finally I got the deployment working as following
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/hello?handlers=securityHandler"/>
{code}
When calling the URL [http://localhost:8182/hello] I'm now getting a
HTTP 403 error with no further details. Any ideas about that?
The hello.properties file looks like
{code:java}
testuser=password
{code}
was (Author: catshout):
Finally I got the deployment working as following
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/hello?handlers=securityHandler"/>
{code}
When calling the URL [http://localhost:8182/hello] I'm now getting a
HTTP 403 error with no further details. Any ideas about that?
> Outdated documentation for camel-jetty Basic Authentication
> ---
>
> Key: CAMEL-14843
> URL: https://issues.apache.org/jira/browse/CAMEL-14843
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Major
>
> The documentation for camel-jetty seems to be outdated as the HTTP Basic
> Authentication sample doesn't work as described. See the route below.
> I followed the documentation
> [https://camel.apache.org/components/latest/jetty-component.html]
> 2 observations
> * Unresolved requirements: [[WEBISP001.xml [264](R 264.12)]
> osgi.wiring.package; (osgi.wiring.package=org.eclipse.jetty.http.security)]
> * org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
> not allowed to appear in element 'ref'.
> The documentation should be updated to provide a working configuration for
> Camel 3.x
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>
>
>
>
>
> class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
> class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
> class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/hello; />
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14843) Outdated documentation for camel-jetty Basic Authentication
[
https://issues.apache.org/jira/browse/CAMEL-14843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17075824#comment-17075824
]
Gerald Kallas edited comment on CAMEL-14843 at 4/5/20, 12:53 PM:
-
Finally I got the deployment working as following
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/hello?handlers=securityHandler"/>
{code}
When calling the URL [http://localhost:8182/hello] I'm now getting a
HTTP 403 error with no further details. Any ideas about that?
was (Author: catshout):
Finally I got the deployment working as followingFinally I got the deployment
working as following
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/hello?handlers=securityHandler"/>
{code}
When calling the URL http://localhost:8182/hello I'm now getting a
HTTP 403 error with no further details. Any ideas about that?
> Outdated documentation for camel-jetty Basic Authentication
> ---
>
> Key: CAMEL-14843
> URL: https://issues.apache.org/jira/browse/CAMEL-14843
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Major
>
> The documentation for camel-jetty seems to be outdated as the HTTP Basic
> Authentication sample doesn't work as described. See the route below.
> I followed the documentation
> [https://camel.apache.org/components/latest/jetty-component.html]
> 2 observations
> * Unresolved requirements: [[WEBISP001.xml [264](R 264.12)]
> osgi.wiring.package; (osgi.wiring.package=org.eclipse.jetty.http.security)]
> * org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
> not allowed to appear in element 'ref'.
> The documentation should be updated to provide a working configuration for
> Camel 3.x
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>
>
>
>
>
> class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
> class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
> class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/hello; />
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14843) Outdated documentation for camel-jetty Basic Authentication
[
https://issues.apache.org/jira/browse/CAMEL-14843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17075824#comment-17075824
]
Gerald Kallas commented on CAMEL-14843:
---
Finally I got the deployment working as followingFinally I got the deployment
working as following
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/hello?handlers=securityHandler"/>
{code}
When calling the URL http://localhost:8182/hello I'm now getting a
HTTP 403 error with no further details. Any ideas about that?
> Outdated documentation for camel-jetty Basic Authentication
> ---
>
> Key: CAMEL-14843
> URL: https://issues.apache.org/jira/browse/CAMEL-14843
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Major
>
> The documentation for camel-jetty seems to be outdated as the HTTP Basic
> Authentication sample doesn't work as described. See the route below.
> I followed the documentation
> [https://camel.apache.org/components/latest/jetty-component.html]
> 2 observations
> * Unresolved requirements: [[WEBISP001.xml [264](R 264.12)]
> osgi.wiring.package; (osgi.wiring.package=org.eclipse.jetty.http.security)]
> * org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
> not allowed to appear in element 'ref'.
> The documentation should be updated to provide a working configuration for
> Camel 3.x
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>
>
>
>
>
> class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
> class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
> class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/hello; />
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14843) Outdated documentation for camel-jetty Basic Authentication
[
https://issues.apache.org/jira/browse/CAMEL-14843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17075782#comment-17075782
]
Gerald Kallas commented on CAMEL-14843:
---
I was changing my DSL as followingI was changing my DSL as following
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/hello?handlers=securityHandler; />
{code}
Seems that the class
org.eclipse.jetty.util.security.Constraint
has been replaced with
org.eclipse.jetty.util.security.Constraint
in Jetty9. Now I'm getting an error
{code:java}
org.osgi.service.blueprint.container.ComponentDefinitionException: Error
setting property: PropertyDescriptor Outdated documentation for camel-jetty Basic Authentication
> ---
>
> Key: CAMEL-14843
> URL: https://issues.apache.org/jira/browse/CAMEL-14843
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Major
>
> The documentation for camel-jetty seems to be outdated as the HTTP Basic
> Authentication sample doesn't work as described. See the route below.
> I followed the documentation
> [https://camel.apache.org/components/latest/jetty-component.html]
> 2 observations
> * Unresolved requirements: [[WEBISP001.xml [264](R 264.12)]
> osgi.wiring.package; (osgi.wiring.package=org.eclipse.jetty.http.security)]
> * org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
> not allowed to appear in element 'ref'.
> The documentation should be updated to provide a working configuration for
> Camel 3.x
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>
>
>
>
>
> class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
> class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
> class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/hello; />
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14843) Outdated documentation for camel-jetty Basic Authentication
[
https://issues.apache.org/jira/browse/CAMEL-14843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17075764#comment-17075764
]
Gerald Kallas edited comment on CAMEL-14843 at 4/5/20, 9:36 AM:
[~davsclaus], I did some research as you suggested. The package
org.eclipse.jetty.http.security seems to be no longer available with Jetty 9.
The first part won't work with Jetty 9.4.20 embedded in Camel 3.x. So far, is
there an alternative to get this Basic Authentication running?
{code:java}
{code}
was (Author: catshout):
[~davsclaus], I did some research as you suggested. The package
org.eclipse.jetty.http.security seems to be no longer available with Jetty 9.
So far, is there an alternative to get this Basic Authentication running?
> Outdated documentation for camel-jetty Basic Authentication
> ---
>
> Key: CAMEL-14843
> URL: https://issues.apache.org/jira/browse/CAMEL-14843
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Major
>
> The documentation for camel-jetty seems to be outdated as the HTTP Basic
> Authentication sample doesn't work as described. See the route below.
> I followed the documentation
> [https://camel.apache.org/components/latest/jetty-component.html]
> 2 observations
> * Unresolved requirements: [[WEBISP001.xml [264](R 264.12)]
> osgi.wiring.package; (osgi.wiring.package=org.eclipse.jetty.http.security)]
> * org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
> not allowed to appear in element 'ref'.
> The documentation should be updated to provide a working configuration for
> Camel 3.x
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>
>
>
>
>
> class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
> class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
> class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/hello; />
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14843) Outdated documentation for camel-jetty Basic Authentication
[
https://issues.apache.org/jira/browse/CAMEL-14843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14843:
--
Description:
The documentation for camel-jetty seems to be outdated as the HTTP Basic
Authentication sample doesn't work as described. See the route below.
I followed the documentation
[https://camel.apache.org/components/latest/jetty-component.html]
2 observations
* Unresolved requirements: [[WEBISP001.xml [264](R 264.12)]
osgi.wiring.package; (osgi.wiring.package=org.eclipse.jetty.http.security)]
* org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
not allowed to appear in element 'ref'.
The documentation should be updated to provide a working configuration for
Camel 3.x
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/hello; />
{code}
was:
The documentation for camel-jetty seems to be outdated as the HTTP Basic
Authentication sample doesn't work as described. See the route below.
I followed the documentation
[https://camel.apache.org/components/latest/jetty-component.html]
2 observations
* Unresolved requirements: [[WEBISP001.xml [264](R 264.12)]
osgi.wiring.package; (osgi.wiring.package=org.eclipse.jetty.http.security)]
* org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
not allowed to appear in element 'ref'.
The documentation should be updated to provide a working configuration for
Camel 3.x
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/hello; />
{code}
> Outdated documentation for camel-jetty Basic Authentication
> ---
>
> Key: CAMEL-14843
> URL: https://issues.apache.org/jira/browse/CAMEL-14843
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Major
>
> The documentation for camel-jetty seems to be outdated as the HTTP Basic
> Authentication sample doesn't work as described. See the route below.
> I followed the documentation
> [https://camel.apache.org/components/latest/jetty-component.html]
> 2 observations
> * Unresolved requirements: [[WEBISP001.xml [264](R 264.12)]
> osgi.wiring.package; (osgi.wiring.package=org.eclipse.jetty.http.security)]
> * org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
> not allowed to appear in element 'ref'.
> The documentation should be updated to provide a working configuration for
> Camel 3.x
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>
>
>
>
>
> class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
> class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
> class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/hello; />
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14843) Outdated documentation for camel-jetty Basic Authentication
[
https://issues.apache.org/jira/browse/CAMEL-14843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17075764#comment-17075764
]
Gerald Kallas commented on CAMEL-14843:
---
[~davsclaus], I did some research as you suggested. The package
org.eclipse.jetty.http.security seems to be no longer available with Jetty 9.
So far, is there an alternative to get this Basic Authentication running?
> Outdated documentation for camel-jetty Basic Authentication
> ---
>
> Key: CAMEL-14843
> URL: https://issues.apache.org/jira/browse/CAMEL-14843
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Major
>
> The documentation for camel-jetty seems to be outdated as the HTTP Basic
> Authentication sample doesn't work as described. See the route below.
> I followed the documentation
> [https://camel.apache.org/components/latest/jetty-component.html]
> 2 observations
> * Unresolved requirements: [[WEBISP001.xml [264](R 264.12)]
> osgi.wiring.package; (osgi.wiring.package=org.eclipse.jetty.http.security)]
> * org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
> not allowed to appear in element 'ref'.
> The documentation should be updated to provide a working configuration for
> Camel 3.x
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>
>
>
>
>
> class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
> class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
> class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/hello; />
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14843) Outdated documentation for camel-jetty Basic Authentication
[
https://issues.apache.org/jira/browse/CAMEL-14843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14843:
--
Environment: (was: {code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/hello; />
{code})
> Outdated documentation for camel-jetty Basic Authentication
> ---
>
> Key: CAMEL-14843
> URL: https://issues.apache.org/jira/browse/CAMEL-14843
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Major
>
> The documentation for camel-jetty seems to be outdated as the HTTP Basic
> Authentication sample doesn't work as described. See the route below.
> I followed the documentation
> [https://camel.apache.org/components/latest/jetty-component.html]
> 2 observations
> * Unresolved requirements: [[WEBISP001.xml [264](R 264.12)]
> osgi.wiring.package; (osgi.wiring.package=org.eclipse.jetty.http.security)]
> * org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
> not allowed to appear in element 'ref'.
> The documentation should be updated to provide a working configuration for
> Camel 3.x
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>
>
>
>
>
> class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
> class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
> class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/hello; />
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14843) Outdated documentation for camel-jetty Basic Authentication
[
https://issues.apache.org/jira/browse/CAMEL-14843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14843:
--
Description:
The documentation for camel-jetty seems to be outdated as the HTTP Basic
Authentication sample doesn't work as described. See the route below.
I followed the documentation
[https://camel.apache.org/components/latest/jetty-component.html]
2 observations
* Unresolved requirements: [[WEBISP001.xml [264](R 264.12)]
osgi.wiring.package; (osgi.wiring.package=org.eclipse.jetty.http.security)]
* org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
not allowed to appear in element 'ref'.
The documentation should be updated to provide a working configuration for
Camel 3.x
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/hello; />
{code}
was:
The documentation for camel-jetty seems to be outdated as the HTTP Basic
Authentication sample doesn't work as described. See the route below.
I followed the documentation
[https://camel.apache.org/components/latest/jetty-component.html]
2 observations
* Unresolved requirements: [[WEBISP001.xml [264](R 264.12)]
osgi.wiring.package; (osgi.wiring.package=org.eclipse.jetty.http.security)]
* org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
not allowed to appear in element 'ref'.
> Outdated documentation for camel-jetty Basic Authentication
> ---
>
> Key: CAMEL-14843
> URL: https://issues.apache.org/jira/browse/CAMEL-14843
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
> Environment: {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>
>
>
>
>
> class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
> class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
> class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/hello; />
>
>
>
>
> {code}
>Reporter: Gerald Kallas
>Priority: Major
>
> The documentation for camel-jetty seems to be outdated as the HTTP Basic
> Authentication sample doesn't work as described. See the route below.
> I followed the documentation
> [https://camel.apache.org/components/latest/jetty-component.html]
> 2 observations
> * Unresolved requirements: [[WEBISP001.xml [264](R 264.12)]
> osgi.wiring.package; (osgi.wiring.package=org.eclipse.jetty.http.security)]
> * org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
> not allowed to appear in element 'ref'.
> The documentation should be updated to provide a working configuration for
> Camel 3.x
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>
>
>
>
>
> class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
> class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
> class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/hello; />
>
>
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14843) Outdated documentation for camel-jetty Basic Authentication
[
https://issues.apache.org/jira/browse/CAMEL-14843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14843:
--
Description:
The documentation for camel-jetty seems to be outdated as the HTTP Basic
Authentication sample doesn't work as described. See the route below.
I followed the documentation
[https://camel.apache.org/components/latest/jetty-component.html]
2 observations
* Unresolved requirements: [[WEBISP001.xml [264](R 264.12)]
osgi.wiring.package; (osgi.wiring.package=org.eclipse.jetty.http.security)]
* org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
not allowed to appear in element 'ref'.
was:
The documentation for camel-jetty seems to be outdated as the HTTP Basic
Authentication sample doesn't work as described. See the route below.
I followed the documentation
[https://camel.apache.org/components/latest/jetty-component.html]
2 observations
*
Unresolved requirements: [[WEBISP001.xml [264](R 264.12)] osgi.wiring.package;
(osgi.wiring.package=org.eclipse.jetty.http.security)]
* org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
not allowed to appear in element 'ref'.
> Outdated documentation for camel-jetty Basic Authentication
> ---
>
> Key: CAMEL-14843
> URL: https://issues.apache.org/jira/browse/CAMEL-14843
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
> Environment: {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
>xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
>
>
>
>
>
> class="org.eclipse.jetty.security.ConstraintMapping">
>
>
>
> class="org.eclipse.jetty.security.ConstraintSecurityHandler">
>
> class="org.eclipse.jetty.security.authentication.BasicAuthenticator"/>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> http://0.0.0.0:8182/hello; />
>
>
>
>
> {code}
>Reporter: Gerald Kallas
>Priority: Major
>
> The documentation for camel-jetty seems to be outdated as the HTTP Basic
> Authentication sample doesn't work as described. See the route below.
> I followed the documentation
> [https://camel.apache.org/components/latest/jetty-component.html]
> 2 observations
> * Unresolved requirements: [[WEBISP001.xml [264](R 264.12)]
> osgi.wiring.package; (osgi.wiring.package=org.eclipse.jetty.http.security)]
> * org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
> not allowed to appear in element 'ref'.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (CAMEL-14843) Outdated documentation for camel-jetty Basic Authentication
Gerald Kallas created CAMEL-14843:
-
Summary: Outdated documentation for camel-jetty Basic
Authentication
Key: CAMEL-14843
URL: https://issues.apache.org/jira/browse/CAMEL-14843
Project: Camel
Issue Type: Bug
Components: camel-jetty
Affects Versions: 3.0.1
Environment: {code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
http://0.0.0.0:8182/hello; />
{code}
Reporter: Gerald Kallas
The documentation for camel-jetty seems to be outdated as the HTTP Basic
Authentication sample doesn't work as described. See the route below.
I followed the documentation
[https://camel.apache.org/components/latest/jetty-component.html]
2 observations
*
Unresolved requirements: [[WEBISP001.xml [264](R 264.12)] osgi.wiring.package;
(osgi.wiring.package=org.eclipse.jetty.http.security)]
* org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'bean' is
not allowed to appear in element 'ref'.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14629) Install of camel-jackson on Karaf 4.2.7 w/ Camel 3.1.0 causes an error (same worked with Karaf 4.2.7 w/ Camel 3.0.1)
[
https://issues.apache.org/jira/browse/CAMEL-14629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17065939#comment-17065939
]
Gerald Kallas commented on CAMEL-14629:
---
Great [~davsclaus]. Many thanks, will wait for the next fix release than.
> Install of camel-jackson on Karaf 4.2.7 w/ Camel 3.1.0 causes an error (same
> worked with Karaf 4.2.7 w/ Camel 3.0.1)
>
>
> Key: CAMEL-14629
> URL: https://issues.apache.org/jira/browse/CAMEL-14629
> Project: Camel
> Issue Type: Bug
> Components: camel-jackson
>Affects Versions: 3.1.0
>Reporter: Gerald Kallas
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 3.2.0, 3.1.1
>
>
> I tried to upgrade from Karaf 4.2.7 w/ Camel 3.0.1 towards Karaf 4.2.7 w/
> Camel 3.1.0. Same behaviour also with Karaf 4.2.8 w/ Camel 3.1.0
>
> While executing these commands
>
>
> {code:java}
> karaf@root()> feature:repo-add hawtio 2.9.1
> Adding feature url mvn:io.hawt/hawtio-karaf/2.9.1/xml/features
> karaf@root()> feature:repo-add activemq 5.15.11
> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.15.11/xml/features
> karaf@root()> feature:repo-add camel 3.1.0
> Adding feature url mvn:org.apache.camel.karaf/apache-camel/3.1.0/xml/features
> karaf@root()> feature:install webconsole hawtio activemq-broker-noweb camel
> camel-jms jms camel-http camel-jetty camel-swagger-java camel-ftp
> camel-jackson camel-jsonpath camel-zipfile camel-velocity camel-groovy {code}
>
> I'm getting the following error
>
>
> {code:java}
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve root:
> missing requirement [root] osgi.identity; osgi.identity=camel-jackson;
> type=karaf.feature; version="[3.1.0,3.1.0]";
> filter:="(&(osgi.identity=camel-jackson)(type=karaf.feature)(version>=3.1.0)(version<=3.1.0))"
> [caused by: Unable to resolve camel-jackson/3.1.0: missing requirement
> [camel-jackson/3.1.0] osgi.identity;
> osgi.identity=org.apache.camel.camel-jackson; type=osgi.bundle;
> version="[3.1.0,3.1.0]"; resolution:=mandatory [caused by: Unable to resolve
> org.apache.camel.camel-jackson/3.1.0: missing requirement
> [org.apache.camel.camel-jackson/3.1.0] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=com.fasterxml.jackson.module.jaxb)(version>=2.9.0)(!(version>=3.0.0)))"
> [caused by: Unable to resolve
> com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2: missing
> requirement
> [com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2]
> osgi.wiring.package; filter:="(&(osgi.wiring.package=
> javax.xml.bind)(version>=2.3.0)(!(version>=3.0.0)))"]]] at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
> at org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:392)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:378) at
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:332) at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:393)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748) Caused by:
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve
> camel-jackson/3.1.0: missing requirement [camel-jackson/3.1.0] osgi.identity;
> osgi.identity=org.apache.camel.camel-jackson; type=osgi.bundle;
> version="[3.1.0,3.1.0]"; resolution:=mandatory [caused by: Unable to resolve
> org.apache.camel.camel-jackson/3.1.0: missing requirement
> [org.apache.camel.camel-jackson/3.1.0] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=com.fasterxml.jackson.module.jaxb)(version>=2.9.0)(!(version>=3.0.0)))"
> [caused by: Unable to resolve
> com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2: missing
> requirement
> [com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2]
> osgi.wiring.package;
> filter:="(&(osgi.wiring.package=javax.xml.bind)(version>=2.3.0)(!(version>=3.0.0)))"]]
> at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
> ... 12 more Caused by: org.apache.felix.resolver.reason.ReasonException:
>
[jira] [Commented] (CAMEL-14629) Install of camel-jackson on Karaf 4.2.7 w/ Camel 3.1.0 causes an error (same worked with Karaf 4.2.7 w/ Camel 3.0.1)
[
https://issues.apache.org/jira/browse/CAMEL-14629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064623#comment-17064623
]
Gerald Kallas commented on CAMEL-14629:
---
[~jbonofre] do you have any news in between? Client is still waiting for a
solution .. many thanks in advance.
Gerald
> Install of camel-jackson on Karaf 4.2.7 w/ Camel 3.1.0 causes an error (same
> worked with Karaf 4.2.7 w/ Camel 3.0.1)
>
>
> Key: CAMEL-14629
> URL: https://issues.apache.org/jira/browse/CAMEL-14629
> Project: Camel
> Issue Type: Bug
> Components: camel-jackson
>Affects Versions: 3.1.0
>Reporter: Gerald Kallas
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 3.1.1
>
>
> I tried to upgrade from Karaf 4.2.7 w/ Camel 3.0.1 towards Karaf 4.2.7 w/
> Camel 3.1.0. Same behaviour also with Karaf 4.2.8 w/ Camel 3.1.0
>
> While executing these commands
>
>
> {code:java}
> karaf@root()> feature:repo-add hawtio 2.9.1
> Adding feature url mvn:io.hawt/hawtio-karaf/2.9.1/xml/features
> karaf@root()> feature:repo-add activemq 5.15.11
> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.15.11/xml/features
> karaf@root()> feature:repo-add camel 3.1.0
> Adding feature url mvn:org.apache.camel.karaf/apache-camel/3.1.0/xml/features
> karaf@root()> feature:install webconsole hawtio activemq-broker-noweb camel
> camel-jms jms camel-http camel-jetty camel-swagger-java camel-ftp
> camel-jackson camel-jsonpath camel-zipfile camel-velocity camel-groovy {code}
>
> I'm getting the following error
>
>
> {code:java}
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve root:
> missing requirement [root] osgi.identity; osgi.identity=camel-jackson;
> type=karaf.feature; version="[3.1.0,3.1.0]";
> filter:="(&(osgi.identity=camel-jackson)(type=karaf.feature)(version>=3.1.0)(version<=3.1.0))"
> [caused by: Unable to resolve camel-jackson/3.1.0: missing requirement
> [camel-jackson/3.1.0] osgi.identity;
> osgi.identity=org.apache.camel.camel-jackson; type=osgi.bundle;
> version="[3.1.0,3.1.0]"; resolution:=mandatory [caused by: Unable to resolve
> org.apache.camel.camel-jackson/3.1.0: missing requirement
> [org.apache.camel.camel-jackson/3.1.0] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=com.fasterxml.jackson.module.jaxb)(version>=2.9.0)(!(version>=3.0.0)))"
> [caused by: Unable to resolve
> com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2: missing
> requirement
> [com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2]
> osgi.wiring.package; filter:="(&(osgi.wiring.package=
> javax.xml.bind)(version>=2.3.0)(!(version>=3.0.0)))"]]] at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
> at org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:392)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:378) at
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:332) at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:393)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748) Caused by:
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve
> camel-jackson/3.1.0: missing requirement [camel-jackson/3.1.0] osgi.identity;
> osgi.identity=org.apache.camel.camel-jackson; type=osgi.bundle;
> version="[3.1.0,3.1.0]"; resolution:=mandatory [caused by: Unable to resolve
> org.apache.camel.camel-jackson/3.1.0: missing requirement
> [org.apache.camel.camel-jackson/3.1.0] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=com.fasterxml.jackson.module.jaxb)(version>=2.9.0)(!(version>=3.0.0)))"
> [caused by: Unable to resolve
> com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2: missing
> requirement
> [com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2]
> osgi.wiring.package;
> filter:="(&(osgi.wiring.package=javax.xml.bind)(version>=2.3.0)(!(version>=3.0.0)))"]]
> at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
> ... 12 more Caused by:
[jira] [Created] (CAMEL-14748) Unmarshal ZIP w/ error handling in Camel 3.x
Gerald Kallas created CAMEL-14748:
-
Summary: Unmarshal ZIP w/ error handling in Camel 3.x
Key: CAMEL-14748
URL: https://issues.apache.org/jira/browse/CAMEL-14748
Project: Camel
Issue Type: Bug
Components: came-core
Affects Versions: 3.0.1
Reporter: Gerald Kallas
I've following route
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;>
http://camel.apache.org/schema/blueprint;>
{code}
When I'm sending a corrupted ZIP file to this route I'd expect a Camel runtime
error. This won't happen, I'm only getting an empty body.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14629) Install of camel-jackson on Karaf 4.2.7 w/ Camel 3.1.0 causes an error (same worked with Karaf 4.2.7 w/ Camel 3.0.1)
[
https://issues.apache.org/jira/browse/CAMEL-14629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053084#comment-17053084
]
Gerald Kallas commented on CAMEL-14629:
---
[~jbonofre], [~acosentino], do you have a forecast when this issue would be
fixed? Many thanks in advance.
> Install of camel-jackson on Karaf 4.2.7 w/ Camel 3.1.0 causes an error (same
> worked with Karaf 4.2.7 w/ Camel 3.0.1)
>
>
> Key: CAMEL-14629
> URL: https://issues.apache.org/jira/browse/CAMEL-14629
> Project: Camel
> Issue Type: Bug
> Components: camel-jackson
>Affects Versions: 3.1.0
>Reporter: Gerald Kallas
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 3.1.1
>
>
> I tried to upgrade from Karaf 4.2.7 w/ Camel 3.0.1 towards Karaf 4.2.7 w/
> Camel 3.1.0. Same behaviour also with Karaf 4.2.8 w/ Camel 3.1.0
>
> While executing these commands
>
>
> {code:java}
> karaf@root()> feature:repo-add hawtio 2.9.1
> Adding feature url mvn:io.hawt/hawtio-karaf/2.9.1/xml/features
> karaf@root()> feature:repo-add activemq 5.15.11
> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.15.11/xml/features
> karaf@root()> feature:repo-add camel 3.1.0
> Adding feature url mvn:org.apache.camel.karaf/apache-camel/3.1.0/xml/features
> karaf@root()> feature:install webconsole hawtio activemq-broker-noweb camel
> camel-jms jms camel-http camel-jetty camel-swagger-java camel-ftp
> camel-jackson camel-jsonpath camel-zipfile camel-velocity camel-groovy {code}
>
> I'm getting the following error
>
>
> {code:java}
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve root:
> missing requirement [root] osgi.identity; osgi.identity=camel-jackson;
> type=karaf.feature; version="[3.1.0,3.1.0]";
> filter:="(&(osgi.identity=camel-jackson)(type=karaf.feature)(version>=3.1.0)(version<=3.1.0))"
> [caused by: Unable to resolve camel-jackson/3.1.0: missing requirement
> [camel-jackson/3.1.0] osgi.identity;
> osgi.identity=org.apache.camel.camel-jackson; type=osgi.bundle;
> version="[3.1.0,3.1.0]"; resolution:=mandatory [caused by: Unable to resolve
> org.apache.camel.camel-jackson/3.1.0: missing requirement
> [org.apache.camel.camel-jackson/3.1.0] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=com.fasterxml.jackson.module.jaxb)(version>=2.9.0)(!(version>=3.0.0)))"
> [caused by: Unable to resolve
> com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2: missing
> requirement
> [com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2]
> osgi.wiring.package; filter:="(&(osgi.wiring.package=
> javax.xml.bind)(version>=2.3.0)(!(version>=3.0.0)))"]]] at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
> at org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:392)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:378) at
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:332) at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:393)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748) Caused by:
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve
> camel-jackson/3.1.0: missing requirement [camel-jackson/3.1.0] osgi.identity;
> osgi.identity=org.apache.camel.camel-jackson; type=osgi.bundle;
> version="[3.1.0,3.1.0]"; resolution:=mandatory [caused by: Unable to resolve
> org.apache.camel.camel-jackson/3.1.0: missing requirement
> [org.apache.camel.camel-jackson/3.1.0] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=com.fasterxml.jackson.module.jaxb)(version>=2.9.0)(!(version>=3.0.0)))"
> [caused by: Unable to resolve
> com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2: missing
> requirement
> [com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2]
> osgi.wiring.package;
> filter:="(&(osgi.wiring.package=javax.xml.bind)(version>=2.3.0)(!(version>=3.0.0)))"]]
> at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
> ... 12 more Caused by:
[jira] [Commented] (CAMEL-14629) Install of camel-jackson on Karaf 4.2.7 w/ Camel 3.1.0 causes an error (same worked with Karaf 4.2.7 w/ Camel 3.0.1)
[
https://issues.apache.org/jira/browse/CAMEL-14629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17047831#comment-17047831
]
Gerald Kallas commented on CAMEL-14629:
---
Add-On ..
I was using Java 8
{code:java}
$ java -version
openjdk version "1.8.0_222"
OpenJDK Runtime Environment (build 1.8.0_222-b10)
OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode){code}
> Install of camel-jackson on Karaf 4.2.7 w/ Camel 3.1.0 causes an error (same
> worked with Karaf 4.2.7 w/ Camel 3.0.1)
>
>
> Key: CAMEL-14629
> URL: https://issues.apache.org/jira/browse/CAMEL-14629
> Project: Camel
> Issue Type: Bug
> Components: camel-jackson
>Affects Versions: 3.1.0
>Reporter: Gerald Kallas
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 3.1.1
>
>
> I tried to upgrade from Karaf 4.2.7 w/ Camel 3.0.1 towards Karaf 4.2.7 w/
> Camel 3.1.0. Same behaviour also with Karaf 4.2.8 w/ Camel 3.1.0
>
> While executing these commands
>
>
> {code:java}
> karaf@root()> feature:repo-add hawtio 2.9.1
> Adding feature url mvn:io.hawt/hawtio-karaf/2.9.1/xml/features
> karaf@root()> feature:repo-add activemq 5.15.11
> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.15.11/xml/features
> karaf@root()> feature:repo-add camel 3.1.0
> Adding feature url mvn:org.apache.camel.karaf/apache-camel/3.1.0/xml/features
> karaf@root()> feature:install webconsole hawtio activemq-broker-noweb camel
> camel-jms jms camel-http camel-jetty camel-swagger-java camel-ftp
> camel-jackson camel-jsonpath camel-zipfile camel-velocity camel-groovy {code}
>
> I'm getting the following error
>
>
> {code:java}
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve root:
> missing requirement [root] osgi.identity; osgi.identity=camel-jackson;
> type=karaf.feature; version="[3.1.0,3.1.0]";
> filter:="(&(osgi.identity=camel-jackson)(type=karaf.feature)(version>=3.1.0)(version<=3.1.0))"
> [caused by: Unable to resolve camel-jackson/3.1.0: missing requirement
> [camel-jackson/3.1.0] osgi.identity;
> osgi.identity=org.apache.camel.camel-jackson; type=osgi.bundle;
> version="[3.1.0,3.1.0]"; resolution:=mandatory [caused by: Unable to resolve
> org.apache.camel.camel-jackson/3.1.0: missing requirement
> [org.apache.camel.camel-jackson/3.1.0] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=com.fasterxml.jackson.module.jaxb)(version>=2.9.0)(!(version>=3.0.0)))"
> [caused by: Unable to resolve
> com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2: missing
> requirement
> [com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2]
> osgi.wiring.package; filter:="(&(osgi.wiring.package=
> javax.xml.bind)(version>=2.3.0)(!(version>=3.0.0)))"]]] at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
> at org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:392)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:378) at
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:332) at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:393)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748) Caused by:
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve
> camel-jackson/3.1.0: missing requirement [camel-jackson/3.1.0] osgi.identity;
> osgi.identity=org.apache.camel.camel-jackson; type=osgi.bundle;
> version="[3.1.0,3.1.0]"; resolution:=mandatory [caused by: Unable to resolve
> org.apache.camel.camel-jackson/3.1.0: missing requirement
> [org.apache.camel.camel-jackson/3.1.0] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=com.fasterxml.jackson.module.jaxb)(version>=2.9.0)(!(version>=3.0.0)))"
> [caused by: Unable to resolve
> com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2: missing
> requirement
> [com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2]
> osgi.wiring.package;
> filter:="(&(osgi.wiring.package=javax.xml.bind)(version>=2.3.0)(!(version>=3.0.0)))"]]
> at
>
[jira] [Created] (CAMEL-14629) Install of camel-jackson on Karaf 4.2.7 w/ Camel 3.1.0 causes an error (same worked with Karaf 4.2.7 w/ Camel 3.0.1)
Gerald Kallas created CAMEL-14629:
-
Summary: Install of camel-jackson on Karaf 4.2.7 w/ Camel 3.1.0
causes an error (same worked with Karaf 4.2.7 w/ Camel 3.0.1)
Key: CAMEL-14629
URL: https://issues.apache.org/jira/browse/CAMEL-14629
Project: Camel
Issue Type: Bug
Components: camel-jackson
Affects Versions: 3.1.0
Reporter: Gerald Kallas
I tried to upgrade from Karaf 4.2.7 w/ Camel 3.0.1 towards Karaf 4.2.7 w/ Camel
3.1.0. Same behaviour also with Karaf 4.2.8 w/ Camel 3.1.0
While executing these commands
{code:java}
karaf@root()> feature:repo-add hawtio 2.9.1
Adding feature url mvn:io.hawt/hawtio-karaf/2.9.1/xml/features
karaf@root()> feature:repo-add activemq 5.15.11
Adding feature url mvn:org.apache.activemq/activemq-karaf/5.15.11/xml/features
karaf@root()> feature:repo-add camel 3.1.0
Adding feature url mvn:org.apache.camel.karaf/apache-camel/3.1.0/xml/features
karaf@root()> feature:install webconsole hawtio activemq-broker-noweb camel
camel-jms jms camel-http camel-jetty camel-swagger-java camel-ftp camel-jackson
camel-jsonpath camel-zipfile camel-velocity camel-groovy {code}
I'm getting the following error
{code:java}
org.apache.felix.resolver.reason.ReasonException: Unable to resolve root:
missing requirement [root] osgi.identity; osgi.identity=camel-jackson;
type=karaf.feature; version="[3.1.0,3.1.0]";
filter:="(&(osgi.identity=camel-jackson)(type=karaf.feature)(version>=3.1.0)(version<=3.1.0))"
[caused by: Unable to resolve camel-jackson/3.1.0: missing requirement
[camel-jackson/3.1.0] osgi.identity;
osgi.identity=org.apache.camel.camel-jackson; type=osgi.bundle;
version="[3.1.0,3.1.0]"; resolution:=mandatory [caused by: Unable to resolve
org.apache.camel.camel-jackson/3.1.0: missing requirement
[org.apache.camel.camel-jackson/3.1.0] osgi.wiring.package;
filter:="(&(osgi.wiring.package=com.fasterxml.jackson.module.jaxb)(version>=2.9.0)(!(version>=3.0.0)))"
[caused by: Unable to resolve
com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2: missing
requirement
[com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2]
osgi.wiring.package; filter:="(&(osgi.wiring.package=
javax.xml.bind)(version>=2.3.0)(!(version>=3.0.0)))"]]] at
org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
at org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:392) at
org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:378) at
org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:332) at
org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:393)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748) Caused by:
org.apache.felix.resolver.reason.ReasonException: Unable to resolve
camel-jackson/3.1.0: missing requirement [camel-jackson/3.1.0] osgi.identity;
osgi.identity=org.apache.camel.camel-jackson; type=osgi.bundle;
version="[3.1.0,3.1.0]"; resolution:=mandatory [caused by: Unable to resolve
org.apache.camel.camel-jackson/3.1.0: missing requirement
[org.apache.camel.camel-jackson/3.1.0] osgi.wiring.package;
filter:="(&(osgi.wiring.package=com.fasterxml.jackson.module.jaxb)(version>=2.9.0)(!(version>=3.0.0)))"
[caused by: Unable to resolve
com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2: missing
requirement
[com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2]
osgi.wiring.package;
filter:="(&(osgi.wiring.package=javax.xml.bind)(version>=2.3.0)(!(version>=3.0.0)))"]]
at
org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
... 12 more Caused by: org.apache.felix.resolver.reason.ReasonException:
Unable to resolve org.apache.camel.camel-jackson/3.1.0: missing requirement
[org.apache.camel.camel-jackson/3.1.0] osgi.wiring.package;
filter:="(&(osgi.wiring.package=com.fasterxml.jackson.module.jaxb)(version>=2.9.0)(!(version>=3.0.0)))"
[caused by: Unable to resolve
com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2: missing
requirement
[com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2]
osgi.wiring.package;
filter:="(&(osgi.wiring.package=javax.xml.bind)(version>=2.3.0)(!(version>=3.0.0)))"]
at
[jira] [Commented] (CAMEL-14527) camel-jetty HTTPS consumer still fails with handshake failure
[
https://issues.apache.org/jira/browse/CAMEL-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035714#comment-17035714
]
Gerald Kallas commented on CAMEL-14527:
---
Many thanks, [~jondruse], it works like a charm!
And, [~davsclaus], sorry for discuss here, I moved the answer to here
[https://camel.465427.n5.nabble.com/Re-camel-jetty-HTTPS-consumer-still-fails-with-handshake-failure-possible-bug-td5855702.html]
> camel-jetty HTTPS consumer still fails with handshake failure
> -
>
> Key: CAMEL-14527
> URL: https://issues.apache.org/jira/browse/CAMEL-14527
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Assignee: Jiri Ondrusek
>Priority: Major
>
> After several research I did create the following Blueprint DSL route that
> still fails with a TLS handshake failure.
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0; xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> TLSv1.2
> TLSv1.1
>
>
> .*
>
>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> uri="jetty:https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters;
> />
>
>
>
>
> {code}
> This is the deployment log
> {code:java}
> 2020-02-08T20:31:49,784 | INFO | fileinstall-/opt/apache-karaf-4.2.7/deploy
> | BlueprintContainerImpl | 80 - org.apache.aries.blueprint.core -
> 1.10.2 | Blueprint bundle WEBISP001.xml/0.0.0 has been started
> 2020-02-08T20:31:49,786 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> Attempting to start CamelContext: WEBISP001
> 2020-02-08T20:31:49,789 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> Apache Camel 3.0.1 (CamelContext: WEBISP001) is starting
> 2020-02-08T20:31:49,791 | INFO | Blueprint Event Dispatcher: 1 |
> JmxManagementStrategy| 88 - org.apache.camel.camel-api - 3.0.1 |
> JMX is enabled
> 2020-02-08T20:31:49,877 | INFO | Blueprint Event Dispatcher: 1 |
> HttpComponent| 88 - org.apache.camel.camel-api - 3.0.1 |
> Created ClientConnectionManager
> org.apache.http.impl.conn.PoolingHttpClientConnectionManager@12fc7e57
> 2020-02-08T20:31:49,881 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> StreamCaching is not in use. If using streams then its recommended to enable
> stream caching. See more details at
> http://camel.apache.org/stream-caching.html
> 2020-02-08T20:31:49,896 | INFO | Blueprint Event Dispatcher: 1 |
> SSLContextParameters | 88 - org.apache.camel.camel-api - 3.0.1 |
> Available providers: SUN version 1.8.
> 2020-02-08T20:31:49,906 | INFO | Blueprint Event Dispatcher: 1 |
> JettyHttpComponent9 | 112 - org.apache.camel.camel-jetty - 3.0.1
> | Connector on port: 8444 is using includeCipherSuites: [.*]
> excludeCipherSuites: [] includeProtocols: [TLSv1.3, TLSv1.2, TLSv1.1]
> excludeProtocols: [SSL, SSLv2, SSLv2Hello, SSLv3]
> 2020-02-08T20:31:49,907 | INFO | Blueprint Event Dispatcher: 1 | Server
> | 217 - org.eclipse.jetty.util - 9.4.20.v20190813 |
> jetty-9.4.20.v20190813; built: 2019-08-13T21:28:18.144Z; git:
> 84700530e645e812b336747464d6fbbf370c9a20; jvm 1.8.0_242-b08
> 2020-02-08T20:31:49,908 | INFO | Blueprint Event Dispatcher: 1 |
> ContextHandler | 217 - org.eclipse.jetty.util -
> 9.4.20.v20190813 | Started
> o.e.j.s.ServletContextHandler@4d63dc0b{/,null,AVAILABLE}
> 2020-02-08T20:31:49,915 | INFO | Blueprint Event Dispatcher: 1 |
> SslContextFactory| 217 - org.eclipse.jetty.util -
> 9.4.20.v20190813 | Protocol TLSv1.3 not supported in [SSLv2Hello, SSLv3,
> TLSv1, TLSv1.1, TLSv1.2]
> 2020-02-08T20:31:49,915 | WARN | Blueprint Event Dispatcher: 1 | config
> | 217 - org.eclipse.jetty.util - 9.4.20.v20190813 | Weak
> cipher suite TLS_RSA_WITH_AES_256_CBC_SHA256 enabled for
> SslContextFactory@6234ffd1[provider=null,keyStore=null,trustStore=null]
> 2020-02-08T20:31:49,916 | WARN | Blueprint Event Dispatcher: 1 | config
> | 217 - org.eclipse.jetty.util - 9.4.20.v20190813 | Weak
> cipher suite TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA enabled for
>
[jira] [Closed] (CAMEL-14527) camel-jetty HTTPS consumer still fails with handshake failure
[
https://issues.apache.org/jira/browse/CAMEL-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas closed CAMEL-14527.
-
Resolution: Not A Bug
Closed again after comment edit.
> camel-jetty HTTPS consumer still fails with handshake failure
> -
>
> Key: CAMEL-14527
> URL: https://issues.apache.org/jira/browse/CAMEL-14527
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Assignee: Jiri Ondrusek
>Priority: Major
>
> After several research I did create the following Blueprint DSL route that
> still fails with a TLS handshake failure.
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0; xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> TLSv1.2
> TLSv1.1
>
>
> .*
>
>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> uri="jetty:https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters;
> />
>
>
>
>
> {code}
> This is the deployment log
> {code:java}
> 2020-02-08T20:31:49,784 | INFO | fileinstall-/opt/apache-karaf-4.2.7/deploy
> | BlueprintContainerImpl | 80 - org.apache.aries.blueprint.core -
> 1.10.2 | Blueprint bundle WEBISP001.xml/0.0.0 has been started
> 2020-02-08T20:31:49,786 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> Attempting to start CamelContext: WEBISP001
> 2020-02-08T20:31:49,789 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> Apache Camel 3.0.1 (CamelContext: WEBISP001) is starting
> 2020-02-08T20:31:49,791 | INFO | Blueprint Event Dispatcher: 1 |
> JmxManagementStrategy| 88 - org.apache.camel.camel-api - 3.0.1 |
> JMX is enabled
> 2020-02-08T20:31:49,877 | INFO | Blueprint Event Dispatcher: 1 |
> HttpComponent| 88 - org.apache.camel.camel-api - 3.0.1 |
> Created ClientConnectionManager
> org.apache.http.impl.conn.PoolingHttpClientConnectionManager@12fc7e57
> 2020-02-08T20:31:49,881 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> StreamCaching is not in use. If using streams then its recommended to enable
> stream caching. See more details at
> http://camel.apache.org/stream-caching.html
> 2020-02-08T20:31:49,896 | INFO | Blueprint Event Dispatcher: 1 |
> SSLContextParameters | 88 - org.apache.camel.camel-api - 3.0.1 |
> Available providers: SUN version 1.8.
> 2020-02-08T20:31:49,906 | INFO | Blueprint Event Dispatcher: 1 |
> JettyHttpComponent9 | 112 - org.apache.camel.camel-jetty - 3.0.1
> | Connector on port: 8444 is using includeCipherSuites: [.*]
> excludeCipherSuites: [] includeProtocols: [TLSv1.3, TLSv1.2, TLSv1.1]
> excludeProtocols: [SSL, SSLv2, SSLv2Hello, SSLv3]
> 2020-02-08T20:31:49,907 | INFO | Blueprint Event Dispatcher: 1 | Server
> | 217 - org.eclipse.jetty.util - 9.4.20.v20190813 |
> jetty-9.4.20.v20190813; built: 2019-08-13T21:28:18.144Z; git:
> 84700530e645e812b336747464d6fbbf370c9a20; jvm 1.8.0_242-b08
> 2020-02-08T20:31:49,908 | INFO | Blueprint Event Dispatcher: 1 |
> ContextHandler | 217 - org.eclipse.jetty.util -
> 9.4.20.v20190813 | Started
> o.e.j.s.ServletContextHandler@4d63dc0b{/,null,AVAILABLE}
> 2020-02-08T20:31:49,915 | INFO | Blueprint Event Dispatcher: 1 |
> SslContextFactory| 217 - org.eclipse.jetty.util -
> 9.4.20.v20190813 | Protocol TLSv1.3 not supported in [SSLv2Hello, SSLv3,
> TLSv1, TLSv1.1, TLSv1.2]
> 2020-02-08T20:31:49,915 | WARN | Blueprint Event Dispatcher: 1 | config
> | 217 - org.eclipse.jetty.util - 9.4.20.v20190813 | Weak
> cipher suite TLS_RSA_WITH_AES_256_CBC_SHA256 enabled for
> SslContextFactory@6234ffd1[provider=null,keyStore=null,trustStore=null]
> 2020-02-08T20:31:49,916 | WARN | Blueprint Event Dispatcher: 1 | config
> | 217 - org.eclipse.jetty.util - 9.4.20.v20190813 | Weak
> cipher suite TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA enabled for
> SslContextFactory@6234ffd1[provider=null,keyStore=null,trustStore=null]
> 2020-02-08T20:31:49,916 | WARN | Blueprint Event Dispatcher: 1 | config
> | 217 - org.eclipse.jetty.util - 9.4.20.v20190813 | Weak
> cipher suite TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
[jira] [Reopened] (CAMEL-14527) camel-jetty HTTPS consumer still fails with handshake failure
[
https://issues.apache.org/jira/browse/CAMEL-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas reopened CAMEL-14527:
---
Just for edit one comment ..
> camel-jetty HTTPS consumer still fails with handshake failure
> -
>
> Key: CAMEL-14527
> URL: https://issues.apache.org/jira/browse/CAMEL-14527
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Assignee: Jiri Ondrusek
>Priority: Major
>
> After several research I did create the following Blueprint DSL route that
> still fails with a TLS handshake failure.
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0; xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> TLSv1.2
> TLSv1.1
>
>
> .*
>
>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> uri="jetty:https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters;
> />
>
>
>
>
> {code}
> This is the deployment log
> {code:java}
> 2020-02-08T20:31:49,784 | INFO | fileinstall-/opt/apache-karaf-4.2.7/deploy
> | BlueprintContainerImpl | 80 - org.apache.aries.blueprint.core -
> 1.10.2 | Blueprint bundle WEBISP001.xml/0.0.0 has been started
> 2020-02-08T20:31:49,786 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> Attempting to start CamelContext: WEBISP001
> 2020-02-08T20:31:49,789 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> Apache Camel 3.0.1 (CamelContext: WEBISP001) is starting
> 2020-02-08T20:31:49,791 | INFO | Blueprint Event Dispatcher: 1 |
> JmxManagementStrategy| 88 - org.apache.camel.camel-api - 3.0.1 |
> JMX is enabled
> 2020-02-08T20:31:49,877 | INFO | Blueprint Event Dispatcher: 1 |
> HttpComponent| 88 - org.apache.camel.camel-api - 3.0.1 |
> Created ClientConnectionManager
> org.apache.http.impl.conn.PoolingHttpClientConnectionManager@12fc7e57
> 2020-02-08T20:31:49,881 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> StreamCaching is not in use. If using streams then its recommended to enable
> stream caching. See more details at
> http://camel.apache.org/stream-caching.html
> 2020-02-08T20:31:49,896 | INFO | Blueprint Event Dispatcher: 1 |
> SSLContextParameters | 88 - org.apache.camel.camel-api - 3.0.1 |
> Available providers: SUN version 1.8.
> 2020-02-08T20:31:49,906 | INFO | Blueprint Event Dispatcher: 1 |
> JettyHttpComponent9 | 112 - org.apache.camel.camel-jetty - 3.0.1
> | Connector on port: 8444 is using includeCipherSuites: [.*]
> excludeCipherSuites: [] includeProtocols: [TLSv1.3, TLSv1.2, TLSv1.1]
> excludeProtocols: [SSL, SSLv2, SSLv2Hello, SSLv3]
> 2020-02-08T20:31:49,907 | INFO | Blueprint Event Dispatcher: 1 | Server
> | 217 - org.eclipse.jetty.util - 9.4.20.v20190813 |
> jetty-9.4.20.v20190813; built: 2019-08-13T21:28:18.144Z; git:
> 84700530e645e812b336747464d6fbbf370c9a20; jvm 1.8.0_242-b08
> 2020-02-08T20:31:49,908 | INFO | Blueprint Event Dispatcher: 1 |
> ContextHandler | 217 - org.eclipse.jetty.util -
> 9.4.20.v20190813 | Started
> o.e.j.s.ServletContextHandler@4d63dc0b{/,null,AVAILABLE}
> 2020-02-08T20:31:49,915 | INFO | Blueprint Event Dispatcher: 1 |
> SslContextFactory| 217 - org.eclipse.jetty.util -
> 9.4.20.v20190813 | Protocol TLSv1.3 not supported in [SSLv2Hello, SSLv3,
> TLSv1, TLSv1.1, TLSv1.2]
> 2020-02-08T20:31:49,915 | WARN | Blueprint Event Dispatcher: 1 | config
> | 217 - org.eclipse.jetty.util - 9.4.20.v20190813 | Weak
> cipher suite TLS_RSA_WITH_AES_256_CBC_SHA256 enabled for
> SslContextFactory@6234ffd1[provider=null,keyStore=null,trustStore=null]
> 2020-02-08T20:31:49,916 | WARN | Blueprint Event Dispatcher: 1 | config
> | 217 - org.eclipse.jetty.util - 9.4.20.v20190813 | Weak
> cipher suite TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA enabled for
> SslContextFactory@6234ffd1[provider=null,keyStore=null,trustStore=null]
> 2020-02-08T20:31:49,916 | WARN | Blueprint Event Dispatcher: 1 | config
> | 217 - org.eclipse.jetty.util - 9.4.20.v20190813 | Weak
> cipher suite TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA enabled for
>
[jira] [Comment Edited] (CAMEL-14527) camel-jetty HTTPS consumer still fails with handshake failure
[
https://issues.apache.org/jira/browse/CAMEL-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035140#comment-17035140
]
Gerald Kallas edited comment on CAMEL-14527 at 2/12/20 11:07 AM:
-
Tx [~jondruse]. Yes, you're right. I tried this out with 2 blueprint files like
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
http://camel.apache.org/schema/blueprint;>
{code}
and
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
http://camel.apache.org/schema/blueprint;>
https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters;
/>
{code}
It gives an error
{code:java}
Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve
endpoint:
jetty://https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters
due to: No bean could be found in the registry for: sslContextParameters of
type: org.apache.camel.support.jsse.SSLContextParameters
{code}
Do I still miss something?
Tx
Gerald
was (Author: catshout):
Tx [~jondruse]. Yes, you're right. I tried this out with 2 blueprint files like
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
http://camel.apache.org/schema/blueprint;>
{code}
and
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
http://camel.apache.org/schema/blueprint;>
https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters;
/>
{code}
It gives an error
{code:java}
Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve
endpoint:
jetty://https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters
due to: No bean could be found in the registry for: sslContextParameters of
type: org.apache.camel.support.jsse.SSLContextParameters
{code}
Do I still miss something?
Tx
Gerald
> camel-jetty HTTPS consumer still fails with handshake failure
> -
>
> Key: CAMEL-14527
> URL: https://issues.apache.org/jira/browse/CAMEL-14527
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Assignee: Jiri Ondrusek
>Priority: Major
>
> After several research I did create the following Blueprint DSL route that
> still fails with a TLS handshake failure.
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0; xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> TLSv1.2
> TLSv1.1
>
>
> .*
>
>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> uri="jetty:https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters;
> />
>
>
>
>
> {code}
> This is the deployment log
> {code:java}
> 2020-02-08T20:31:49,784 | INFO | fileinstall-/opt/apache-karaf-4.2.7/deploy
> | BlueprintContainerImpl | 80 - org.apache.aries.blueprint.core -
> 1.10.2 | Blueprint bundle WEBISP001.xml/0.0.0 has been started
> 2020-02-08T20:31:49,786 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> Attempting to start CamelContext: WEBISP001
> 2020-02-08T20:31:49,789 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> Apache Camel 3.0.1 (CamelContext: WEBISP001) is starting
> 2020-02-08T20:31:49,791 | INFO | Blueprint Event Dispatcher: 1 |
> JmxManagementStrategy| 88 -
[jira] [Commented] (CAMEL-14527) camel-jetty HTTPS consumer still fails with handshake failure
[
https://issues.apache.org/jira/browse/CAMEL-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035265#comment-17035265
]
Gerald Kallas commented on CAMEL-14527:
---
[~jondruse] I need the configuration of the sslContextParametersin different
bundles / files as the blueprint XML files will be deployed independently and
so far it will be created separate bundles.
Further .. I was required to add the auto-export option like
{code:java}
{code}
These both in different files/bundles (hot deployment in /deploy folder) don't
work for me
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
http://camel.apache.org/schema/blueprint;>
{code}
and
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
http://camel.apache.org/schema/blueprint;>
https://0.0.0.0:8444/hello?sslContextParameters=#sslContextParameters;
/>
{code}
I'm still getting
{code:java}
Caused by: org.apache.camel.NoSuchBeanException: No bean could be found in the
registry for: sslContextParameters of type:
org.apache.camel.support.jsse.SSLContextParameters
{code}
P.S. For the JMS configuration the 2 separate blueprint files / bundles work
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;>
{code}
and further use of the JMS connection factory in other blueprints files /
bundles (separated).
{code:java}
...
...
{code}
> camel-jetty HTTPS consumer still fails with handshake failure
> -
>
> Key: CAMEL-14527
> URL: https://issues.apache.org/jira/browse/CAMEL-14527
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Assignee: Jiri Ondrusek
>Priority: Major
>
> After several research I did create the following Blueprint DSL route that
> still fails with a TLS handshake failure.
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0; xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> TLSv1.2
> TLSv1.1
>
>
> .*
>
>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> uri="jetty:https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters;
> />
>
>
>
>
> {code}
> This is the deployment log
> {code:java}
> 2020-02-08T20:31:49,784 | INFO | fileinstall-/opt/apache-karaf-4.2.7/deploy
> | BlueprintContainerImpl | 80 - org.apache.aries.blueprint.core -
> 1.10.2 | Blueprint bundle WEBISP001.xml/0.0.0 has been started
> 2020-02-08T20:31:49,786 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> Attempting to start CamelContext: WEBISP001
> 2020-02-08T20:31:49,789 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> Apache Camel 3.0.1 (CamelContext: WEBISP001) is starting
> 2020-02-08T20:31:49,791 | INFO | Blueprint Event Dispatcher: 1 |
> JmxManagementStrategy| 88 - org.apache.camel.camel-api - 3.0.1 |
> JMX is enabled
> 2020-02-08T20:31:49,877 | INFO | Blueprint Event Dispatcher: 1 |
> HttpComponent| 88 - org.apache.camel.camel-api - 3.0.1 |
> Created ClientConnectionManager
> org.apache.http.impl.conn.PoolingHttpClientConnectionManager@12fc7e57
> 2020-02-08T20:31:49,881 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> StreamCaching is not in use. If using streams then its recommended to enable
> stream caching. See more details at
> http://camel.apache.org/stream-caching.html
> 2020-02-08T20:31:49,896 | INFO | Blueprint Event Dispatcher: 1 |
> SSLContextParameters | 88 - org.apache.camel.camel-api - 3.0.1 |
> Available providers: SUN version 1.8.
> 2020-02-08T20:31:49,906 | INFO |
[jira] [Commented] (CAMEL-14527) camel-jetty HTTPS consumer still fails with handshake failure
[
https://issues.apache.org/jira/browse/CAMEL-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035165#comment-17035165
]
Gerald Kallas commented on CAMEL-14527:
---
[~acosentino] I tried this out but it doesn't work either. Same error ..
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
http://camel.apache.org/schema/blueprint;>
https://0.0.0.0:8444/hello?sslContextParameters=#sslContextParameters;
/>
{code}
> camel-jetty HTTPS consumer still fails with handshake failure
> -
>
> Key: CAMEL-14527
> URL: https://issues.apache.org/jira/browse/CAMEL-14527
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Assignee: Jiri Ondrusek
>Priority: Major
>
> After several research I did create the following Blueprint DSL route that
> still fails with a TLS handshake failure.
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0; xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> TLSv1.2
> TLSv1.1
>
>
> .*
>
>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> uri="jetty:https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters;
> />
>
>
>
>
> {code}
> This is the deployment log
> {code:java}
> 2020-02-08T20:31:49,784 | INFO | fileinstall-/opt/apache-karaf-4.2.7/deploy
> | BlueprintContainerImpl | 80 - org.apache.aries.blueprint.core -
> 1.10.2 | Blueprint bundle WEBISP001.xml/0.0.0 has been started
> 2020-02-08T20:31:49,786 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> Attempting to start CamelContext: WEBISP001
> 2020-02-08T20:31:49,789 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> Apache Camel 3.0.1 (CamelContext: WEBISP001) is starting
> 2020-02-08T20:31:49,791 | INFO | Blueprint Event Dispatcher: 1 |
> JmxManagementStrategy| 88 - org.apache.camel.camel-api - 3.0.1 |
> JMX is enabled
> 2020-02-08T20:31:49,877 | INFO | Blueprint Event Dispatcher: 1 |
> HttpComponent| 88 - org.apache.camel.camel-api - 3.0.1 |
> Created ClientConnectionManager
> org.apache.http.impl.conn.PoolingHttpClientConnectionManager@12fc7e57
> 2020-02-08T20:31:49,881 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> StreamCaching is not in use. If using streams then its recommended to enable
> stream caching. See more details at
> http://camel.apache.org/stream-caching.html
> 2020-02-08T20:31:49,896 | INFO | Blueprint Event Dispatcher: 1 |
> SSLContextParameters | 88 - org.apache.camel.camel-api - 3.0.1 |
> Available providers: SUN version 1.8.
> 2020-02-08T20:31:49,906 | INFO | Blueprint Event Dispatcher: 1 |
> JettyHttpComponent9 | 112 - org.apache.camel.camel-jetty - 3.0.1
> | Connector on port: 8444 is using includeCipherSuites: [.*]
> excludeCipherSuites: [] includeProtocols: [TLSv1.3, TLSv1.2, TLSv1.1]
> excludeProtocols: [SSL, SSLv2, SSLv2Hello, SSLv3]
> 2020-02-08T20:31:49,907 | INFO | Blueprint Event Dispatcher: 1 | Server
> | 217 - org.eclipse.jetty.util - 9.4.20.v20190813 |
> jetty-9.4.20.v20190813; built: 2019-08-13T21:28:18.144Z; git:
> 84700530e645e812b336747464d6fbbf370c9a20; jvm 1.8.0_242-b08
> 2020-02-08T20:31:49,908 | INFO | Blueprint Event Dispatcher: 1 |
> ContextHandler | 217 - org.eclipse.jetty.util -
> 9.4.20.v20190813 | Started
> o.e.j.s.ServletContextHandler@4d63dc0b{/,null,AVAILABLE}
> 2020-02-08T20:31:49,915 | INFO | Blueprint Event Dispatcher: 1 |
> SslContextFactory| 217 - org.eclipse.jetty.util -
> 9.4.20.v20190813 | Protocol TLSv1.3 not supported in [SSLv2Hello, SSLv3,
> TLSv1, TLSv1.1, TLSv1.2]
> 2020-02-08T20:31:49,915 | WARN | Blueprint Event Dispatcher: 1 | config
> | 217 - org.eclipse.jetty.util - 9.4.20.v20190813 | Weak
> cipher suite TLS_RSA_WITH_AES_256_CBC_SHA256 enabled for
>
[jira] [Commented] (CAMEL-14527) camel-jetty HTTPS consumer still fails with handshake failure
[
https://issues.apache.org/jira/browse/CAMEL-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035140#comment-17035140
]
Gerald Kallas commented on CAMEL-14527:
---
Tx [~jondruse]. Yes, you're right. I tried this out with 2 blueprint files like
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
http://camel.apache.org/schema/blueprint;>
{code}
and
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
http://camel.apache.org/schema/blueprint;>
https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters;
/>
{code}
It gives an error
{code:java}
Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve
endpoint:
jetty://https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters
due to: No bean could be found in the registry for: sslContextParameters of
type: org.apache.camel.support.jsse.SSLContextParameters
{code}
Do I still miss something?
Tx
Gerald
> camel-jetty HTTPS consumer still fails with handshake failure
> -
>
> Key: CAMEL-14527
> URL: https://issues.apache.org/jira/browse/CAMEL-14527
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Assignee: Jiri Ondrusek
>Priority: Major
>
> After several research I did create the following Blueprint DSL route that
> still fails with a TLS handshake failure.
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0; xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> TLSv1.2
> TLSv1.1
>
>
> .*
>
>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> uri="jetty:https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters;
> />
>
>
>
>
> {code}
> This is the deployment log
> {code:java}
> 2020-02-08T20:31:49,784 | INFO | fileinstall-/opt/apache-karaf-4.2.7/deploy
> | BlueprintContainerImpl | 80 - org.apache.aries.blueprint.core -
> 1.10.2 | Blueprint bundle WEBISP001.xml/0.0.0 has been started
> 2020-02-08T20:31:49,786 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> Attempting to start CamelContext: WEBISP001
> 2020-02-08T20:31:49,789 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> Apache Camel 3.0.1 (CamelContext: WEBISP001) is starting
> 2020-02-08T20:31:49,791 | INFO | Blueprint Event Dispatcher: 1 |
> JmxManagementStrategy| 88 - org.apache.camel.camel-api - 3.0.1 |
> JMX is enabled
> 2020-02-08T20:31:49,877 | INFO | Blueprint Event Dispatcher: 1 |
> HttpComponent| 88 - org.apache.camel.camel-api - 3.0.1 |
> Created ClientConnectionManager
> org.apache.http.impl.conn.PoolingHttpClientConnectionManager@12fc7e57
> 2020-02-08T20:31:49,881 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> StreamCaching is not in use. If using streams then its recommended to enable
> stream caching. See more details at
> http://camel.apache.org/stream-caching.html
> 2020-02-08T20:31:49,896 | INFO | Blueprint Event Dispatcher: 1 |
> SSLContextParameters | 88 - org.apache.camel.camel-api - 3.0.1 |
> Available providers: SUN version 1.8.
> 2020-02-08T20:31:49,906 | INFO | Blueprint Event Dispatcher: 1 |
> JettyHttpComponent9 | 112 - org.apache.camel.camel-jetty - 3.0.1
> | Connector on port: 8444 is using includeCipherSuites: [.*]
> excludeCipherSuites: [] includeProtocols: [TLSv1.3, TLSv1.2, TLSv1.1]
> excludeProtocols: [SSL, SSLv2, SSLv2Hello, SSLv3]
> 2020-02-08T20:31:49,907 | INFO | Blueprint Event Dispatcher: 1 | Server
> | 217 - org.eclipse.jetty.util - 9.4.20.v20190813 |
> jetty-9.4.20.v20190813; built: 2019-08-13T21:28:18.144Z; git:
>
[jira] [Comment Edited] (CAMEL-14527) camel-jetty HTTPS consumer still fails with handshake failure
[
https://issues.apache.org/jira/browse/CAMEL-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034671#comment-17034671
]
Gerald Kallas edited comment on CAMEL-14527 at 2/11/20 6:03 PM:
Tx [~jondruse] for validate and re-test. You pointed me out to an important
detail while removing the truststore from blueprint.
I've confused both, keystore and truststore, in my blueprint file. Often
checked all but overseen this detail every time. The sample is working now, the
issue can be closed.
One question so far, can I define the sslContextParameters in a separate
blueprint file an reference to it in the other ones that have HTTPS jetty
endpoints? Or, much better, in a config file in etc folder as common parameters
for camel-jetty?
Many thanks for your effort
Gerald
was (Author: catshout):
Tx [~jondruse] for validate and re-test. You pointed me out to an important
detail while removing the truststore from blueprint.
I've confused both, keystore and truststore, in my blueprint file. Often
checked all but overseen this detail every time. The sample is working now, the
issue can be closed.
One question so far, can I define the sslContextParameters in a separate
blueprint file an reference to it in the other ones that have HTTPS jetty
endpoints? Or, much better, in a config file in etc folder as common parameters
for camel-jetty?
Many thanks for your effort
- Gerald
> camel-jetty HTTPS consumer still fails with handshake failure
> -
>
> Key: CAMEL-14527
> URL: https://issues.apache.org/jira/browse/CAMEL-14527
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Assignee: Jiri Ondrusek
>Priority: Major
>
> After several research I did create the following Blueprint DSL route that
> still fails with a TLS handshake failure.
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0; xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> TLSv1.2
> TLSv1.1
>
>
> .*
>
>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> uri="jetty:https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters;
> />
>
>
>
>
> {code}
> This is the deployment log
> {code:java}
> 2020-02-08T20:31:49,784 | INFO | fileinstall-/opt/apache-karaf-4.2.7/deploy
> | BlueprintContainerImpl | 80 - org.apache.aries.blueprint.core -
> 1.10.2 | Blueprint bundle WEBISP001.xml/0.0.0 has been started
> 2020-02-08T20:31:49,786 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> Attempting to start CamelContext: WEBISP001
> 2020-02-08T20:31:49,789 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> Apache Camel 3.0.1 (CamelContext: WEBISP001) is starting
> 2020-02-08T20:31:49,791 | INFO | Blueprint Event Dispatcher: 1 |
> JmxManagementStrategy| 88 - org.apache.camel.camel-api - 3.0.1 |
> JMX is enabled
> 2020-02-08T20:31:49,877 | INFO | Blueprint Event Dispatcher: 1 |
> HttpComponent| 88 - org.apache.camel.camel-api - 3.0.1 |
> Created ClientConnectionManager
> org.apache.http.impl.conn.PoolingHttpClientConnectionManager@12fc7e57
> 2020-02-08T20:31:49,881 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> StreamCaching is not in use. If using streams then its recommended to enable
> stream caching. See more details at
> http://camel.apache.org/stream-caching.html
> 2020-02-08T20:31:49,896 | INFO | Blueprint Event Dispatcher: 1 |
> SSLContextParameters | 88 - org.apache.camel.camel-api - 3.0.1 |
> Available providers: SUN version 1.8.
> 2020-02-08T20:31:49,906 | INFO | Blueprint Event Dispatcher: 1 |
> JettyHttpComponent9 | 112 - org.apache.camel.camel-jetty - 3.0.1
> | Connector on port: 8444 is using includeCipherSuites: [.*]
> excludeCipherSuites: [] includeProtocols: [TLSv1.3, TLSv1.2, TLSv1.1]
> excludeProtocols: [SSL, SSLv2, SSLv2Hello, SSLv3]
> 2020-02-08T20:31:49,907 | INFO | Blueprint Event Dispatcher: 1 | Server
> | 217 - org.eclipse.jetty.util - 9.4.20.v20190813 |
> jetty-9.4.20.v20190813; built: 2019-08-13T21:28:18.144Z; git:
> 84700530e645e812b336747464d6fbbf370c9a20; jvm 1.8.0_242-b08
> 2020-02-08T20:31:49,908 | INFO |
[jira] [Commented] (CAMEL-14527) camel-jetty HTTPS consumer still fails with handshake failure
[
https://issues.apache.org/jira/browse/CAMEL-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17034671#comment-17034671
]
Gerald Kallas commented on CAMEL-14527:
---
Tx [~jondruse] for validate and re-test. You pointed me out to an important
detail while removing the truststore from blueprint.
I've confused both, keystore and truststore, in my blueprint file. Often
checked all but overseen this detail every time. The sample is working now, the
issue can be closed.
One question so far, can I define the sslContextParameters in a separate
blueprint file an reference to it in the other ones that have HTTPS jetty
endpoints? Or, much better, in a config file in etc folder as common parameters
for camel-jetty?
Many thanks for your effort
- Gerald
> camel-jetty HTTPS consumer still fails with handshake failure
> -
>
> Key: CAMEL-14527
> URL: https://issues.apache.org/jira/browse/CAMEL-14527
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Assignee: Jiri Ondrusek
>Priority: Major
>
> After several research I did create the following Blueprint DSL route that
> still fails with a TLS handshake failure.
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0; xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> TLSv1.2
> TLSv1.1
>
>
> .*
>
>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> uri="jetty:https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters;
> />
>
>
>
>
> {code}
> This is the deployment log
> {code:java}
> 2020-02-08T20:31:49,784 | INFO | fileinstall-/opt/apache-karaf-4.2.7/deploy
> | BlueprintContainerImpl | 80 - org.apache.aries.blueprint.core -
> 1.10.2 | Blueprint bundle WEBISP001.xml/0.0.0 has been started
> 2020-02-08T20:31:49,786 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> Attempting to start CamelContext: WEBISP001
> 2020-02-08T20:31:49,789 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> Apache Camel 3.0.1 (CamelContext: WEBISP001) is starting
> 2020-02-08T20:31:49,791 | INFO | Blueprint Event Dispatcher: 1 |
> JmxManagementStrategy| 88 - org.apache.camel.camel-api - 3.0.1 |
> JMX is enabled
> 2020-02-08T20:31:49,877 | INFO | Blueprint Event Dispatcher: 1 |
> HttpComponent| 88 - org.apache.camel.camel-api - 3.0.1 |
> Created ClientConnectionManager
> org.apache.http.impl.conn.PoolingHttpClientConnectionManager@12fc7e57
> 2020-02-08T20:31:49,881 | INFO | Blueprint Event Dispatcher: 1 |
> BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
> StreamCaching is not in use. If using streams then its recommended to enable
> stream caching. See more details at
> http://camel.apache.org/stream-caching.html
> 2020-02-08T20:31:49,896 | INFO | Blueprint Event Dispatcher: 1 |
> SSLContextParameters | 88 - org.apache.camel.camel-api - 3.0.1 |
> Available providers: SUN version 1.8.
> 2020-02-08T20:31:49,906 | INFO | Blueprint Event Dispatcher: 1 |
> JettyHttpComponent9 | 112 - org.apache.camel.camel-jetty - 3.0.1
> | Connector on port: 8444 is using includeCipherSuites: [.*]
> excludeCipherSuites: [] includeProtocols: [TLSv1.3, TLSv1.2, TLSv1.1]
> excludeProtocols: [SSL, SSLv2, SSLv2Hello, SSLv3]
> 2020-02-08T20:31:49,907 | INFO | Blueprint Event Dispatcher: 1 | Server
> | 217 - org.eclipse.jetty.util - 9.4.20.v20190813 |
> jetty-9.4.20.v20190813; built: 2019-08-13T21:28:18.144Z; git:
> 84700530e645e812b336747464d6fbbf370c9a20; jvm 1.8.0_242-b08
> 2020-02-08T20:31:49,908 | INFO | Blueprint Event Dispatcher: 1 |
> ContextHandler | 217 - org.eclipse.jetty.util -
> 9.4.20.v20190813 | Started
> o.e.j.s.ServletContextHandler@4d63dc0b{/,null,AVAILABLE}
> 2020-02-08T20:31:49,915 | INFO | Blueprint Event Dispatcher: 1 |
> SslContextFactory| 217 - org.eclipse.jetty.util -
> 9.4.20.v20190813 | Protocol TLSv1.3 not supported in [SSLv2Hello, SSLv3,
> TLSv1, TLSv1.1, TLSv1.2]
> 2020-02-08T20:31:49,915 | WARN | Blueprint Event Dispatcher: 1 | config
> | 217 - org.eclipse.jetty.util - 9.4.20.v20190813 | Weak
> cipher suite TLS_RSA_WITH_AES_256_CBC_SHA256 enabled for
>
[jira] [Updated] (CAMEL-14527) camel-jetty HTTPS consumer still fails with handshake failure
[
https://issues.apache.org/jira/browse/CAMEL-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14527:
--
Description:
After several research I did create the following Blueprint DSL route that
still fails with a TLS handshake failure.
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
http://camel.apache.org/schema/blueprint;>
TLSv1.2
TLSv1.1
.*
http://camel.apache.org/schema/blueprint;>
https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters;
/>
{code}
This is the deployment log
{code:java}
2020-02-08T20:31:49,784 | INFO | fileinstall-/opt/apache-karaf-4.2.7/deploy |
BlueprintContainerImpl | 80 - org.apache.aries.blueprint.core -
1.10.2 | Blueprint bundle WEBISP001.xml/0.0.0 has been started
2020-02-08T20:31:49,786 | INFO | Blueprint Event Dispatcher: 1 |
BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
Attempting to start CamelContext: WEBISP001
2020-02-08T20:31:49,789 | INFO | Blueprint Event Dispatcher: 1 |
BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
Apache Camel 3.0.1 (CamelContext: WEBISP001) is starting
2020-02-08T20:31:49,791 | INFO | Blueprint Event Dispatcher: 1 |
JmxManagementStrategy| 88 - org.apache.camel.camel-api - 3.0.1 |
JMX is enabled
2020-02-08T20:31:49,877 | INFO | Blueprint Event Dispatcher: 1 | HttpComponent
| 88 - org.apache.camel.camel-api - 3.0.1 | Created
ClientConnectionManager
org.apache.http.impl.conn.PoolingHttpClientConnectionManager@12fc7e57
2020-02-08T20:31:49,881 | INFO | Blueprint Event Dispatcher: 1 |
BlueprintCamelContext| 88 - org.apache.camel.camel-api - 3.0.1 |
StreamCaching is not in use. If using streams then its recommended to enable
stream caching. See more details at http://camel.apache.org/stream-caching.html
2020-02-08T20:31:49,896 | INFO | Blueprint Event Dispatcher: 1 |
SSLContextParameters | 88 - org.apache.camel.camel-api - 3.0.1 |
Available providers: SUN version 1.8.
2020-02-08T20:31:49,906 | INFO | Blueprint Event Dispatcher: 1 |
JettyHttpComponent9 | 112 - org.apache.camel.camel-jetty - 3.0.1 |
Connector on port: 8444 is using includeCipherSuites: [.*] excludeCipherSuites:
[] includeProtocols: [TLSv1.3, TLSv1.2, TLSv1.1] excludeProtocols: [SSL, SSLv2,
SSLv2Hello, SSLv3]
2020-02-08T20:31:49,907 | INFO | Blueprint Event Dispatcher: 1 | Server
| 217 - org.eclipse.jetty.util - 9.4.20.v20190813 |
jetty-9.4.20.v20190813; built: 2019-08-13T21:28:18.144Z; git:
84700530e645e812b336747464d6fbbf370c9a20; jvm 1.8.0_242-b08
2020-02-08T20:31:49,908 | INFO | Blueprint Event Dispatcher: 1 |
ContextHandler | 217 - org.eclipse.jetty.util -
9.4.20.v20190813 | Started
o.e.j.s.ServletContextHandler@4d63dc0b{/,null,AVAILABLE}
2020-02-08T20:31:49,915 | INFO | Blueprint Event Dispatcher: 1 |
SslContextFactory| 217 - org.eclipse.jetty.util -
9.4.20.v20190813 | Protocol TLSv1.3 not supported in [SSLv2Hello, SSLv3, TLSv1,
TLSv1.1, TLSv1.2]
2020-02-08T20:31:49,915 | WARN | Blueprint Event Dispatcher: 1 | config
| 217 - org.eclipse.jetty.util - 9.4.20.v20190813 | Weak
cipher suite TLS_RSA_WITH_AES_256_CBC_SHA256 enabled for
SslContextFactory@6234ffd1[provider=null,keyStore=null,trustStore=null]
2020-02-08T20:31:49,916 | WARN | Blueprint Event Dispatcher: 1 | config
| 217 - org.eclipse.jetty.util - 9.4.20.v20190813 | Weak
cipher suite TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA enabled for
SslContextFactory@6234ffd1[provider=null,keyStore=null,trustStore=null]
2020-02-08T20:31:49,916 | WARN | Blueprint Event Dispatcher: 1 | config
| 217 - org.eclipse.jetty.util - 9.4.20.v20190813 | Weak
cipher suite TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA enabled for
SslContextFactory@6234ffd1[provider=null,keyStore=null,trustStore=null]
2020-02-08T20:31:49,917 | WARN | Blueprint Event Dispatcher: 1 | config
| 217 - org.eclipse.jetty.util - 9.4.20.v20190813 | Weak
cipher suite TLS_RSA_WITH_AES_256_CBC_SHA enabled for
SslContextFactory@6234ffd1[provider=null,keyStore=null,trustStore=null]
2020-02-08T20:31:49,917 | WARN | Blueprint Event Dispatcher: 1 | config
| 217 - org.eclipse.jetty.util - 9.4.20.v20190813 | Weak
cipher suite TLS_RSA_WITH_AES_256_CBC_SHA enabled for
SslContextFactory@6234ffd1[provider=null,keyStore=null,trustStore=null]
2020-02-08T20:31:49,917 | WARN | Blueprint Event Dispatcher:
[jira] [Updated] (CAMEL-14527) camel-jetty HTTPS consumer still fails with handshake failure
[
https://issues.apache.org/jira/browse/CAMEL-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerald Kallas updated CAMEL-14527:
--
Description:
After several research I did create the following Blueprint DSL route that
still fails with a TLS handshake failure.
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
http://camel.apache.org/schema/blueprint;>
TLSv1.2
TLSv1.1
.*
http://camel.apache.org/schema/blueprint;>
https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters;
/>
{code}
The request to the endpoint still fails with
{code:java}
curl -vvv --insecure --location --request POST 'https://host:8444/hello'
--data-raw 'Hello World!'
Note: Unnecessary use of -X or --request, POST is already inferred.
* Trying 10.0.0.147...
* TCP_NODELAY set
* Connected to host (10.0.0.147) port 8444 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS alert, handshake failure (552):
* error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
* Closing connection 0
curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake
failure{code}
was:
After several research I did create the following Blueprint DSL route that
still fails with a TLS handshake failure.
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
http://camel.apache.org/schema/blueprint;>
TLSv1.2 TLSv1.1
.*
http://camel.apache.org/schema/blueprint;>
https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters;
/>
{code}
The request to the endpoint still fails with
{code:java}
curl -vvv --insecure --location --request POST 'https://host:8444/hello'
--data-raw 'Hello World!'
Note: Unnecessary use of -X or --request, POST is already inferred.
* Trying 10.0.0.147...
* TCP_NODELAY set
* Connected to host (10.0.0.147) port 8444 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS alert, handshake failure (552):
* error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
* Closing connection 0
curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake
failure{code}
> camel-jetty HTTPS consumer still fails with handshake failure
> -
>
> Key: CAMEL-14527
> URL: https://issues.apache.org/jira/browse/CAMEL-14527
> Project: Camel
> Issue Type: Bug
> Components: camel-jetty
>Affects Versions: 3.0.1
>Reporter: Gerald Kallas
>Priority: Major
>
> After several research I did create the following Blueprint DSL route that
> still fails with a TLS handshake failure.
> {code:java}
> http://www.osgi.org/xmlns/blueprint/v1.0.0; xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
> https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> TLSv1.2
> TLSv1.1
>
>
> .*
>
>
>
>
>
>
>
>
>
> xmlns="http://camel.apache.org/schema/blueprint;>
>
> uri="jetty:https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters;
> />
>
>
>
>
> {code}
> The request to the endpoint still fails with
> {code:java}
> curl -vvv --insecure --location --request POST 'https://host:8444/hello'
> --data-raw 'Hello World!'
> Note: Unnecessary use of -X or --request, POST is already inferred.
> * Trying 10.0.0.147...
> * TCP_NODELAY set
> * Connected to host (10.0.0.147) port 8444 (#0)
> * ALPN, offering h2
> * ALPN, offering http/1.1
> * successfully set certificate verify locations:
> * CAfile: /etc/pki/tls/certs/ca-bundle.crt
> CApath: none
> * TLSv1.3 (OUT), TLS handshake, Client hello (1):
> * TLSv1.3 (IN), TLS alert, handshake failure (552):
> * error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
> * Closing connection 0
> curl: (35) error:14094410:SSL
[jira] [Created] (CAMEL-14527) camel-jetty HTTPS consumer still fails with handshake failure
Gerald Kallas created CAMEL-14527:
-
Summary: camel-jetty HTTPS consumer still fails with handshake
failure
Key: CAMEL-14527
URL: https://issues.apache.org/jira/browse/CAMEL-14527
Project: Camel
Issue Type: Bug
Components: camel-jetty
Affects Versions: 3.0.1
Reporter: Gerald Kallas
After several research I did create the following Blueprint DSL route that
still fails with a TLS handshake failure.
{code:java}
http://www.osgi.org/xmlns/blueprint/v1.0.0;http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0
https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd;>
http://camel.apache.org/schema/blueprint;>
TLSv1.2 TLSv1.1
.*
http://camel.apache.org/schema/blueprint;>
https://0.0.0.0:8444/hello?sslContextParameters=sslContextParameters;
/>
{code}
The request to the endpoint still fails with
{code:java}
curl -vvv --insecure --location --request POST 'https://host:8444/hello'
--data-raw 'Hello World!'
Note: Unnecessary use of -X or --request, POST is already inferred.
* Trying 10.0.0.147...
* TCP_NODELAY set
* Connected to host (10.0.0.147) port 8444 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS alert, handshake failure (552):
* error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
* Closing connection 0
curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake
failure{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
