Okay, the WSE problem is kind of weird. When you assign "wsu:Id" to the soap body, WSE fails to verify its own signed message!, so I don't expect Java library to verify it. But if you assign only an "Id" attribute, everything works fine.

Vishal

Davanum Srinivas wrote:

Vishal,

what's the problem u are having with WSE?

thanks,
dims

On 4/13/05, Vishal Mahajan <[EMAIL PROTECTED]> wrote:


After more investigation I feel that the Java library is fine. Even
though I'm still having some WS-Security issues, they mainly seem to be
on the WSE2 side, which I'll try raising on some .NET forum.

Thanks,

Vishal

Vishal Mahajan wrote:



Yes it shows in my email also, but the actual document doesn't have
this. Anyways, I've also attached the tared document this time.

Thanks,

Vishal

Raul Benito wrote:



Hi Vishal,
 The digest method look very weird to me:
<DigestMethod Algorithm="http://www.w3.org/!
2000/09/xmldsig#sha1" />

Perhaps it something in my email, but you can take a look there.

Regards,


On Apr 11, 2005 9:12 PM, *Vishal Mahajan* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

   I've attached the soap document signed by .NET
   (interop_dotnet_sig.xml) and the certificate (apcert1.cer) to be
   used for verification. The reference validation fails for the soap
   body. Note that the 'ID Type' attribute used on the soap body is a
   wsu:Id and hence WssIdResolver (attached) needs to be registered
   with the library.

   Vishal


Raul Benito wrote:



   Hi Vishal,
   can you post the document?

   On Apr 11, 2005 11:22 AM, *Vishal Mahajan*
   <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

       I know this topic has been raised earlier on the list. I
       would like to
       know if someone has got Apache xml-security-J interoperating
       with the
       .NET (Microsoft WSE)? I've been trying to debug this for
       quite some
       while now without much success. The reference validation
       seems to be
       failing. The strange thing is that the document that .NET
       signed didn't
       even contain any white-space, even then our library seems to
       be failing
       in validating the signature, and vice versa.

       Vishal




-- http://r-bg.com







--
http://r-bg.com















Reply via email to