Finally I did get this running based on the Camel examples.
Configuration XML ..
http://www.osgi.org/xmlns/blueprint/v1.0.0;>
.. and REST API ..
http://www.osgi.org/xmlns/blueprint/v1.0.0;>
I tried the servlet way .. but also no success. Not sure if this (see below) is
missing something ..
http://www.osgi.org/xmlns/blueprint/v1.0.0;>
http://camel.apache.org/schema/blueprint; streamCache="true">
Oh, sorry, the example was in spring, not blueprint.
Let me check in the component how to inject the configuration.
Regards
JB
On 03/02/2020 13:43, Gerald Kallas wrote:
> Tx JB.
>
> So I tried this (see below) but getting
>
> Blueprint bundle isp.route.RST.xml/0.0.0 is waiting for namespace
Tx JB.
So I tried this (see below) but getting
Blueprint bundle isp.route.RST.xml/0.0.0 is waiting for namespace handlers
[http://camel.apache.org/schema/spring]
As Claus mentioned earlier one must not mix Blueprint with Spring. Without the
Spring namespace the keyword "sslContextParameters"
You have a example here:
https://access.redhat.com/documentation/en-us/red_hat_jboss_fuse/6.2/html/security_guide/cameljetty
On 03/02/2020 11:52, Gerald Kallas wrote:
> I tried this setting
>
> org.ops4j.pax.web.ssl.protocols.included = TLSv1.2
>
> in
>
> org.ops4j.pax.web.cfg.
>
> But this
Hi,
By default, camel-jetty create a new connector: it doesn't use the one
provided by pax-web. If you want to "plug" into the pax-web jetty
connector, you have to use camel-servlet.
camel-jetty fully creates a new jetty connector, so the TLS
configuration has to be set on camel-jetty.
Regards
I tried this setting
org.ops4j.pax.web.ssl.protocols.included = TLSv1.2
in
org.ops4j.pax.web.cfg.
But this doesn't have any effect.
Still the same, I'm getting in the log
2020-02-03T02:00:35,872 | INFO | Blueprint Event Dispatcher: 1 |
JettyHttpComponent9 | 105 -
Tested with cURL
curl --insecure -v https://host:8443/say/hello
* Trying 10.0.0.147...
* TCP_NODELAY set
* Connected to host (10.0.0.147) port 8443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
Thanks JB,
I did not install bouncycastle.
I did install camel-jetty only as Karaf feature. The underpinning Jetty for the
Karaf web console is working fine with HTTPS. So far I wonder what I'm still
missing that camel-jetty could work also with HTTPS.
Best
- Gerald
> Jean-Baptiste Onofré
Hi,
do you have bouncycastle installed ?
Regards
JB
On 03/02/2020 00:29, Gerald Kallas wrote:
> Dear community,
>
> I'm going to access some camel-jetty driven consumer endpoints and getting a
>
> SSL_ERROR_NO_CYPHER_OVERLAP
>
> error. The web console nevertheless is working well.
>
> Any
Dear community,
I'm going to access some camel-jetty driven consumer endpoints and getting a
SSL_ERROR_NO_CYPHER_OVERLAP
error. The web console nevertheless is working well.
Any hints are appreciated.
That's the jetty.xml section
https
11 matches
Mail list logo