What I did was look at the TransportBindingTest in the STS basic systests: https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=blob;f=services/sts/systests/basic/src/test/java/org/apache/cxf/systest/sts/transport/TransportBindingTest.java;h=1e6cebdceef33c016d38ee803e0c0da8e4407b37;hb=HEAD
There is a test called "testSAML2Dispatch" in here which uses the Dispatch API to make a service request. The TLS configuration is at the bottom of this file: https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=blob;f=services/sts/systests/basic/src/test/resources/org/apache/cxf/systest/sts/transport/cxf-client.xml;h=44795974144782dc9b80db65ca6437f83395a6b5;hb=HEAD If you comment it out the test fails at the STSClient stage, meaning that the client must have correctly picked up the TLS configuration before. Colm. On Tue, Aug 18, 2015 at 5:52 PM, Stefan Müller <[email protected]> wrote: > Colm, > > could you please post your working spring + dispatch example, as our config > does not work. We think that in our config the conduit is not picked up > correctly (maybe a naming problem) as it does not even load the keystore. > > Greets, > Stefan > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Mutual-authentication-with-Dispatch-API-tp5760231p5760262.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
