Hi Dan, What exactly is the issue here? Is the service request working ok or is there an exception being thrown? I can't answer your questions until I see the policy of the service provider, as well as the response.
Colm. On Thu, Jun 14, 2012 at 8:29 PM, DTaylor <[email protected]> wrote: > Good day, > > More trials and tribulations while doing CXF & .NET interop. :) > > We have a method of communication now which is allowing our .NET client to > access our Java service, and the service is sending a response. > > From what we can see, it appears as though CXF is using a SAML token > reference as the encryption key but is not sending the token itself. > > From here, we have a couple of questions: > > 1) Is this what is actually happening or are we (potentially) > mis-interpreting the message back? > 2) Is there some way to have the CXF service response be encrypted with the > same key as the request? > > Thanks, > > Dan. > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/CXF-Response-Encryption-NET-interop-tp5709825.html > Sent from the cxf-user mailing list archive at Nabble.com. > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
