Ok the problem here is that the security policy of the STS for the port you are using *also* requires an IssuedToken. So the STSClient call is in turn calling the STSClient of the request and hence the error.
What is the behaviour you are expecting here? Are you sure that you are calling the correct STS port? Colm. On Mon, Jun 23, 2014 at 11:35 AM, roband915 <[email protected]> wrote: > Stacktrace.txt < > http://cxf.547215.n5.nabble.com/file/n5745474/Stacktrace.txt> > > The stacktrace is available in the uploaded file above. > > The exception occurs after the ws-mex response but during the parsing of it > I would say...? > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Issue-with-WS-Trust-using-security-tokens-SAML-assertions-tp5744142p5745474.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
