Hi JR/Werner, With reference to the following mail thread, is it justified to say that, WSS4J still has some issues to be addressed before fully compatible with .NET web services?
Please advice. Thanks Kosuru -----Original Message----- From: footh [mailto:[EMAIL PROTECTED] Sent: Thursday, March 16, 2006 4:13 PM To: [email protected] Subject: Re: AW: AW: AW: Axis client to .NET - simple question? What tests are you referring too? I did test a .NET service with the latest SVN and still had the same problem. Unfortunately, I don't have a .NET environment set up. I've been relying on a service and credentials given to me by a Web Service provider my company is associated with. I did ask him about his configuration and he said they are using Microsoft's WSE 2.0 library and doing nothing special with it. If you (or anyone) have a .NET service that you can play around with, you can test it dynamically at this URL which is using WSS4J (the latest 1.1.0 download, NOT the SVN) and Axis: http://www.esigma.com/telos/analysis/testservice.html This is basically what I'm trying to build out. It uses the code that I detailed in an earlier message. Regards, JF --- "Dittmann, Werner" <[EMAIL PROTECTED]> wrote: > I would like to do it but I don't have the > environment to run the tests. > Anybody around that can perform this tests, probably > with the latest > version of the SVN? > > BTW, can somebody list the configuration that > triggers the error? > Which software and versions of the software is used, > the configuration > setup, config files etc so that we can see if we can > setup the same > configuration to reproduce the problem. > > Regards, > Werner > > > ________________________________ > > Von: Soactive Inc [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 16. März 2006 06:53 > An: footh > Cc: [email protected] > Betreff: Re: AW: AW: Axis client to .NET - simple > question? > > > Can someone from the WSS4J dev team please look > into this and possibly resolve this soon. Seems like > this is a blocking interop issue between WSS4J and > .NET UsernameToken. > > Thanks much! > > > On 3/15/06, footh <[EMAIL PROTECTED]> wrote: > > A FailedAuthentication SOAP fault: > > <soapenv:Fault > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> > <faultcode > xmlns:code=" > http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";>code:FailedAuthentication > </faultcode> > <faultstring>The security token could not be > authenticated or authorized > </faultstring> > > <faultactor>http://ws.staging.xwebservices.com/XWebEmailValidation/V2/EmailValidation.asmx > </faultactor> > </soapenv:Fault> > > > > > --- Tech Rams <[EMAIL PROTECTED]> wrote: > > > Just curious....what does the error log on .NET > say? > > Does it give any clue as to why it is not able > to > > authenticate this token? > > > > --rams > > > > --- footh <[EMAIL PROTECTED]> wrote: > > > > > OK, I found the SVN, downloaded it, ran it as > is, > > > and > > > then modified the code so the wsu:Id would > match > > > exactly the one from the .NET client call. In > > both > > > cases the authentication failed with the same > > error > > > as > > > before. > > > > > > I can only conclude that the digest algorithm > must > > > be > > > incompatible with .NET. Any ideas for further > > > steps? > > > > > > FYI, here is the location that gives > instructions > > > for > > > accessing various source repositories for > apache > > web > > > service projects: > > > > > > http://ws.apache.org/cvs.html > > > > > > --- Soactive Inc <[EMAIL PROTECTED]> wrote: > > > > > > > Hi, > > > > > > > > I am facing the exact same issue. Does > someone > > > have > > > > a resolution for this > > > > yet? Also, if you can send me the exact > location > > > for > > > > the SVN head that would > > > > help too. > > > > > > > > Thanks. > > > > > > > > On 3/13/06, footh <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Thanks for the help Werner. > > > > > > > > > > What is the SVN Head and where do I get > it? > > > > > > > > > > --- "Dittmann, Werner" > > > > < [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > > > > > > wrote: > > > > > > > > > > > Very strange. > > > > > > > > > > > > Maybe you can use the SVN Head an > generate a > > > > WSS4J > > > > > > jar > > > > > > and use this. The deployment parameters > etc > > > are > > > > the > > > > > > same, nothing changed here. > > > > > > > > > > > > The SVN head uses some internal > > enhancements. > > > > One of > > > > > > this > > > > > > enhancement is to always add an Id to > > > > UsernameToken > > > > > > and other > > > > > > elements. > > > > > > > > > > > > Regards, > > > > > > Werner > > > > > > > > > > > > > -----Urspr�ngliche Nachricht----- > > > > > > > Von: footh [mailto:[EMAIL PROTECTED] > > > > > > > Gesendet: Donnerstag, 9. M�rz 2006 > 20:16 > > > > > > > An: [email protected] > > > > > > > Betreff: Re: AW: Axis client to .NET - > > > simple > > > > > > question? > > > > > > > > > > > > > > No problem. The SOAP requests sent by > > each > > > > > > platform > > > > > > > appear below. Also, in case the > > formatting > > > is > > > > > > bad, > > > > > > > I've attached a file with the same > > messages > > > > (had > > > > > > to > > > > > > > archive it or it wouldn't attache for > some > > > > > > reason). > > > > > > > > > > > > > > > > > > > > > <!-- Request sent by Axis: > authentication > > > > fails > > > > > > --> > > > > > > > <soapenv:Envelope > > > > > > > > > > > > > > > > > > > > > > > > > > > > xmlns:soapenv=" > http://schemas.xmlsoap.org/soap/envelope/ > <http://schemas.xmlsoap.org/soap/envelope/> " > > > > > > > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > > > > > > > > > > > > > > > > > > > > > > > > > > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > > > > > <soapenv:Header> > > > > > > > <wsse:Security > === message truncated === __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
