property "javax.net.ssl.keyStore" is set but "javax.net.ssl.keyStoreType"
is not set: maybe this could be the problem.
Anyway, my request is accepted by the server. I imagine this because the
server (is an internal server in trusted network) is configured to accept
all users, otherwise I would
Confirm auto key registration using javax.net.ssl.keyStore system property
is broken in REST module (mayb since cxf 3.2 / 3.3 )
чт, 13 июн. 2019 г. в 19:10, Colm O hEigeartaigh :
> Right, but when you don't specify a "params.setKeyManagers", it tries to
> get the KeyManagers from the
Right, but when you don't specify a "params.setKeyManagers", it tries to
get the KeyManagers from the "javax.net.ssl.keyStore" system property. Can
you check in your case if this is being set?
Colm.
On Thu, Jun 13, 2019 at 1:40 PM Luca Maderna wrote:
> Thanks for your answer Colm.
> I was a
Thanks for your answer Colm.
I was a little inaccurate.
I'm setting trust and keyStore via code as explained in cxf client example.
...
TLSClientParameters params = conduit.getTlsClientParameters();
params.setKeyManagers(myKeyManagers);
params.setTrustManagers(myTrustStoreKeyManagers);
...
What it means is that CXF is trying to load the keystore referenced by the
"javax.net.ssl.keyStore" system property. If you don't want to load a
keyManager for TLS then you will need to unset this property. Otherwise,
perhaps you are not also setting the "javax.net.ssl.keyStoreType" property
(to
Hi
In my cxf client I'mconnecting to a Ws soap in https setting tls properties.
All works properly.
Recently I've updated cxf libraries from a 3.0.x to 3.3.x version.
It continue to works correctly, but I've only this warning in my logs:
Jun 13, 2019 10:31:40 AM
