-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Diarmuid,
On 9/1/15 1:06 PM, dmccrthy wrote:
> I am having trouble getting Tomcat to load a truststore and
> keystore. This seems to be a basic configuration issue but I can't
> figure out what the problem is. Any insights would be gratefully
>
ate packaged in the same file as
the root certificate. If you can separate the certificates your problem should
go away.
Jeff Crump
Sent from Mail for Windows 10
From: George Stanchev
Sent: Tuesday, September 1, 2015 1:02 PM
To: Tomcat Users List
Subject: RE: Tomcat 7.0.55 Not loading tru
Hi Diarmuid,
We have run similar issue with client cert SSL. Is your 3rd party web service
hosted on Windows/IIS?
George
-Original Message-
From: dmccrthy [mailto:dmccr...@gmail.com]
Sent: Tuesday, September 01, 2015 11:07 AM
To: Tomcat Users List
Subject: Tomcat 7.0.55 Not loading
Hi Chris,
Thanks for replying. This is a different 3rd party service we're connecting
to, but again it's a weird one because other tools work. I've included
responses below prefixed with [DMC].
Regards,
Diarmuid
On 1 Sep 2015 20:57, "Christopher Schultz"
wrote:
>
me file
> as the root certificate. If you can separate the certificates your problem
> should go away.
>
> Jeff Crump
>
>
> Sent from Mail for Windows 10
>
>
>
> From: George Stanchev
> Sent: Tuesday, September 1, 2015 1:02 PM
> To: Tomcat Users List
> Subj
m my BlackBerry 10 smartphone on the
> Verizon Wireless 4G LTE network.
> Original Message
> From: dmccrthy
> Sent: Tuesday, September 1, 2015 4:12 PM
> To: Tomcat Users List
> Reply To: Tomcat Users List
> Subject: RE: Tomcat 7.0.55 Not loading truststore or keystore
>
To: Tomcat Users List
Subject: RE: Tomcat 7.0.55 Not loading truststore or keystore
Hi Jeff,
Our client keystore has one certificate, but the truststore has multiple
certs. I'll try removing everything from the truststore except the server
cert and see what happens.
Thanks,
Diarmuid
On 1 Sep 2015
Hi George,
The 3rd party service is behind IBM Datapower. Datapower is reporting that
our HTTPS client connections aren't sending the client certificate as part
of the MA handshake. I'll double-check what the actual service is running
on behind that, but according to our 3rd party application