On Wed, Jan 24, 2018 at 6:50 PM, Al Grant wrote:
> Ok - done. Now what?
>
>
I'm not sure what you mean by "now what". It's up to you to test your
client, we can only advise on errors or provide general guidance.
Colm.
>
>
> --
> Sent from: http://cxf.547215.n5.nabble.com/cxf-user-f547216.html
Ok - done. Now what?
--
Sent from: http://cxf.547215.n5.nabble.com/cxf-user-f547216.html
Hello!
Thanx. I changed the namespace, but not helped.
The DefaultSubjectProvider cant retrieve the subject from this SAML:
[name]
But I get an error, because the subject is null
(At this point I cant change the SAML in the request)
Thanx
Cs
The problem I think is that "http://schemas.xmlsoap.org/ws/2003/06/secext";
is not a standard WS-Security namespace, and hence CXF is not processing
the message header at all. The correct WS-Security namespace for the
security header is instead "
http://docs.oasis-open.org/wss/2004/01/oasis-200401-
So is that all that is needed to use mutual TLS?
I also need to update the endpoint details in the service stubs - I don't
think this can be done with wsimport with mutual tls?
--
Sent from: http://cxf.547215.n5.nabble.com/cxf-user-f547216.html
Remove " tlsParams.setDisableCNCheck(true);", or at least remove it after
testing has finished.
Colm.
On Wed, Jan 24, 2018 at 8:28 AM, Al Grant wrote:
>
> What next?
>
>
>
> --
> Sent from: http://cxf.547215.n5.nabble.com/cxf-user-f547216.html
>
--
Colm O hEigeartaigh
Talend Community Code
Alrightly then. How about something like this:
// CXF CLIENT FOR MUTUAL TLS
// Setup TLS client params
TLSClientParameters tlsParams = new TLSClientParameters();
/* Get the JKS contents */
final char[] JKS_PASSWORD = "password".toCharArray();
final