On Thu, 2005-03-10 at 06:34 -0500, Davanum Srinivas wrote: > Werner, > > there was a check-in yesterday from Sam
Actually this one happened a while ago. I was trying to be compliant to WS-I BSP section 8.3.1. I guess we may need a flag to turn this off? /Sam > -- dims > > > On Thu, 10 Mar 2005 12:30:56 +0100, Dittmann Werner > <[EMAIL PROTECTED]> wrote: > > Yves, > > > > as far as I know we didn't change WSS4J in this respect, > > at least I can't remember any JIRA issue that would have > > caused such a change. Maybe it is the new version of > > the xmlsec library? Usually dims updates the WSS4J cvs > > with the latest version of the xmlsec lib. Can you > > check this (by using an older xmlsec lib)? > > > > Regards, > > Werner > > > > > -----Urspr�ngliche Nachricht----- > > > Von: Yves Langisch [mailto:[EMAIL PROTECTED] > > > Gesendet: Donnerstag, 10. M�rz 2005 12:21 > > > An: [email protected] > > > Betreff: WSS4J interop issue > > > > > > > > > All, > > > > > > We have a .NET client which is able to consume signed > > > messages from our > > > Axis/WSS4J web service. We just put a newer version from the WSS4J > > > library to our web service and now .NET is not able anymore to consume > > > the signed messages. > > > > > > After some digging I found out that the only difference is the new > > > InclusiveNamespaces-element in each Transform-element. .NET > > > doesn't seem > > > to be able to process this additional setting for the canonicalization > > > algorithm correctly. Or WSS4J is doing something wrong here. > > > > > > Used versions: > > > > > > client: WSE 2.0 SP1/SP2/SP3 > > > server: Axis 1.2RC3, WSS4J (cvs from 20041122) > > > --> works fine > > > > > > client: WSE 2.0 SP1/SP2/SP3 > > > server: Axis 1.2RC3, WSS4J (actual cvs build) > > > --> doesn't work > > > > > > Any hints on this? > > > > > > Thanks > > > Yves > > > > > > > -- Sam Meder <[EMAIL PROTECTED]> The Globus Alliance - University of Chicago 630-252-1752
