Hi Dan, The CXF service would appear to be following the policy correctly, as the IssuedToken policy has an IncludeToken requirement of "AlwaysToRecipient". This means that the token must be sent from initiator to recipient, but never from the recipient back to the initiator.
Is the client not processing the response correctly or something? If this is the case, could you attach the message Response as well as any error message from the client? Colm. On Tue, Jun 19, 2012 at 8:13 PM, DTaylor <[email protected]> wrote: > Hi Colm, > > The call goes from the .NET client to the .NET STS and back perfectly fine. > The call from the .NET client to the CXF service enters, hits the method, > triggers logs, exits, and goes back to the client. The incoming message on > the .NET side is (or appears) to be encrypted using a DerivedKey but no > SAML > assertion included in the response. > > I've attached our service wsdl as well. > > http://cxf.547215.n5.nabble.com/file/n5710005/MyDemoService.wsdl > MyDemoService.wsdl > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/CXF-Response-Encryption-NET-interop-tp5709825p5710005.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
