I think there are just some simple issues here surrounding ports (you are sending to 9443 when the STS itself is set up on 8443), and the fact that you are locating two STS instances with the same port names on a single container. If you can replicate the issue with two separate containers then I'll take another look.
Colm. On Tue, Nov 18, 2014 at 1:54 PM, Ingo <wolf.work...@gmail.com> wrote: > Here we go: > I've put together the advanced systest 'cross-domain' from CXF 3.0.2. > Please > find it here: > https://github.com/ogniflow/testcases/tree/master/test > <https://github.com/ogniflow/testcases/tree/master/test> > > I've made the following adjustments: > - STS-B is deployed on Tomcat7 and uses the STS configuration from the > advanced systest 'cross-domain' > > Result: the client fails to get the STS' WSDL via WS-Mex > > > > The STS-B complains about a missing timestamp in the Security-Header: > > > > It looks like the WS-SecurityPolicy is affective also at the WS-Mex > Endpoint, but shouldn't it be ignored when fetching the WSDL via WS-MEX ? > Any useful hints are welcome... > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Exception-when-trying-to-retrieve-process-a-WSDL-via-WS-MEX-tp5750835p5751254.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
