Hi Dan, > <entry key="ws-security.saml2.validator" value-ref="validator"/>
This only applies to a SAML 2.0 Token. As you are receiving a SAML 1.1 Token you should have: > <entry key="ws-security.saml1.validator" value-ref="validator"/> Colm. On Tue, Jan 22, 2013 at 10:36 PM, DTaylor <[email protected]> wrote: > I have attached the service configuration again (I'm pretty sure I've got > too > much in there relating to this issue, as I put in both possible FTTL > modifiying properties, however I've tried it with each individually and it > didn't work either). > > I have also attached the incoming saml1:Assertion object. I'm unsure if > this is the request you were request Colm or not.. if it is not, is there a > specific bit of logging I need to turn on in order to get this for you? > > Thanks, > > Dan. > > samlAssertion.txt > <http://cxf.547215.n5.nabble.com/file/n5722033/samlAssertion.txt> > TestServiceOne.xml > <http://cxf.547215.n5.nabble.com/file/n5722033/TestServiceOne.xml> > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/futureTimeToLive-on-Service-Endpoints-tp5712429p5722033.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
