Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of willem.jiang@gmail.com
 designates 209.85.213.171 as permitted sender)
Date: Mon, 6 Apr 2015 14:35:55 +0800
From: Willem Jiang <willem.jiang@gmail.com>
To: users@camel.apache.org
Message-ID: <etPan.5522294e.6b8b4567.116@localhost>
In-Reply-To: <1428092154889-5765296.post@n5.nabble.com>
References: <1428092154889-5765296.post@n5.nabble.com>
Subject: Re: Jetty HTTPS 2way
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

It looks like some thing is wrong when doing the TLSv1.2 Handshake.=C2=A0=

Can you try to use camel-http or camel-http4 to do the same thing=3F

-- =20
Willem Jiang

Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang =20
Weibo: =E5=A7=9C=E5=AE=81willem


On April 4, 2015 at 4:17:21 AM, garethahealy (garethahealy=40gmail.com) w=
rote:
> I am trying to make a rest call, via HTTPS and have 2way auth. I origin=
ally
> tried to do this with CX=46=5B1=5D, but due to an issue with the condui=
t not
> attaching, have moved to a jetty endpoint.
> =20
> I have the below config for the jetty endpoint:
> =20
> > class=3D=22org.apache.camel.util.jsse.KeyStoreParameters=22>
> > value=3D=22=24=7Bhttp.certs.location=7D/client-keystore.jks=22/>
> =20
> =20
> =20
> > class=3D=22org.apache.camel.util.jsse.KeyStoreParameters=22>
> > value=3D=22=24=7Bhttp.certs.location=7D/client-truststore.jks=22/>
> =20
> =20
> =20
> > class=3D=22org.apache.camel.util.jsse.TrustManagersParameters=22>
> =20
> =20
> =20
> > class=3D=22org.apache.camel.util.jsse.KeyManagersParameters=22>
> =20
> =20
> =20
> =20
> > class=3D=22org.apache.camel.util.jsse.SSLContextParameters=22>
> =20
> =20
> =20
> =20
> > class=3D=22org.apache.camel.component.jetty.JettyHttpComponent=22>
> =20
> =20
> =20
> And make the call as per:
> =20
> =20
> =20
> > uri=3D=22jetty://=7B=7Bfuse.rest.transport=7D=7D://=7B=7Bfuse.rest.ho=
st=7D=7D:=7B=7Bfuse.rest.port=7D=7D/rest/fuse=22/> =20
> =20
> But i still get cert issues. I know the certs are correct and that i am=

> pointing to the correct stores as i have a simple java class that prove=
s
> this works. I've put SSL in debug=5B2=5D, but am not sure what a lot of=
 it
> means. The main thing that sticks out is:
> =20
> CamelJettyClient(0x73d8db54)-4716, WRITE: TLSv1.2 Handshake, length =3D=
 48
> CamelJettyClient(0x73d8db54)-4712, called closeInbound()
> CamelJettyClient(0x73d8db54)-4712, fatal error: 80: Inbound closed befo=
re
> receiving peer's close=5Fnotify: possible truncation attack=3F
> javax.net.ssl.SSLException: Inbound closed before receiving peer's
> close=5Fnotify: possible truncation attack=3F
> %% Invalidated: =5BSession-35, TLS=5FECDHE=5FRSA=5FWITH=5F3DES=5FEDE=5F=
CBC=5FSHA=5D
> =20
> This is for camel 2.12.
> =20
> Have i missed something on the config side=3F
> =20
> =5B1=5D
> http://cxf.547215.n5.nabble.com/Camel-CX=46-HTTPS-http-tlsClientParamet=
ers-not-attaching-td5755601.html =20
> =5B2=5D https://gist.github.com/garethahealy/0144444fcfe6d59eb53b
> =20
> =20
> =20
> --
> View this message in context: http://camel.465427.n5.nabble.com/Jetty-H=
TTPS-2way-tp5765296.html =20
> Sent from the Camel - Users mailing list archive at Nabble.com.
> =20