I had been working with Werner and another individual with this issue. We did remove the milliseconds and no longer received the FailedAuthentication error. However, the service was returning a default error message. So, I'm not sure if the issue was resolved with that particular service.
However, I found out we were testing the same service so it may be the service that is causing a problem. Do you know a WS-Security enabled .NET service you can point me to? If so, I would really like to test it out. Relying on one service is not a very good scientific method for testing. --- "Dittmann, Werner" <[EMAIL PROTECTED]> wrote: > AFAIK that was solved. WSS4J supports timestamps > that use a granularity with milliseconds, .NET does > not > support this. Thus you have to setup WSS4J to not > generate Timestamps with ms resolution. > > Regards, > Werner > > > > -----Ursprüngliche Nachricht----- > > Von: Kosuru, Giri > [mailto:[EMAIL PROTECTED] > > Gesendet: Freitag, 31. März 2006 16:27 > > An: footh; [email protected] > > Betreff: RE: AW: AW: AW: Axis client to .NET - > simple question? > > > > 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-wssecu > rity-secext-1.0.xsd">code:FailedAuthentication > > > </faultcode> > > > <faultstring>The security token could not be > > > authenticated or authorized > > > </faultstring> > > > > > > > > > <faultactor>http://ws.staging.xwebservices.com/XWebEmailValida > tion/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: > === 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]
