It's an issue in CXF: https://issues.apache.org/jira/browse/CXF-4166
I'll merge a fix shortly. Colm. On Tue, Mar 6, 2012 at 3:13 PM, COURTAULT Francois <francois.courta...@gemalto.com> wrote: > Hello Glen, > > The two issues (WSIT-1490 and WSIT-1590) you mention seem not related to the > issue I have got :-( > I am not using STS (WS-Trust) at all: > - WSIT-1490: no SAML used in the KeyIdentifier with a #uuid in the > SOAP request. > - WSIT-1590: no encoded email in the SOAP request. > > Best Regards. > > -----Original Message----- > From: Glen Mazza [mailto:gma...@talend.com] > Sent: mardi 6 mars 2012 15:20 > To: users@cxf.apache.org > Subject: Re: Aware of compatibility issue between CXF and Metro/Weblogic ? > > There's a couple of problems that seem to be on Metro's side > (http://java.net/jira/browse/WSIT-1490, > http://java.net/jira/browse/WSIT-1590) affecting interoperability between the > two stacks. It would be great if these were fixed, as both Metro and CXF are > better off the more interoperable they are with each other. Feel free to > vote for these two issues. :) > > Glen > > On 03/06/2012 07:03 AM, COURTAULT Francois wrote: >> Hello, >> >> I have tried to write a CXF client which talks to a WSS protected >> (X509Token) webservice hosted in Weblogic (Metro based) but unfortunately I >> got a Soap fault error. >> >> If I compare a soap request which works and the one generated by CXF, the >> only difference I have seen is that in the<dsig:KeyInfo> >> <wsse:SecurityTokenReference> section, I have a<wsse:KeyIdentifier> >> section in the one which succeeded whereas I haven't this section in the CXF >> one. >> >> Any advice ? Any idea ? >> >> Best Regards. >> > > > -- > Glen Mazza > Talend Community Coders - coders.talend.com > blog: www.jroller.com/gmazza > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
