[xmlsec] RE: Implementing WS-Security using XMLSec...

Venky Madireddi venky at arvasoft.com
Wed Jun 4 00:53:34 PDT 2003


I have downloaded xss4j from IBM to get the exc c14n output, I will compare
it with the one from xmlsec. Unfortunately, I don't have any control on what
type of c14n method Websphere uses. The interoperability with Websphere
would be one of our requirements.

Thanks,

-Venky
  -----Original Message-----
  From: Aleksey Sanin [mailto:aleksey at aleksey.com]
  Sent: Wednesday, June 04, 2003 12:10 AM
  To: venky at arvasoft.com
  Cc: xmlsec at aleksey.com
  Subject: Re: [xmlsec] RE: Implementing WS-Security using XMLSec...




    Thanks for the reply, I am sorry about not using the mailing list, will
make sure to use it in the future.
  It would be great if you also subscribe to the list since you have to be
subscribed
  in order to post :)

    I don't have a DTD, I am using the xmlAddID function to inform LibXML2
about all the ID's.
  Does not matter. xmlAddID() should work too.


     Also, I am capturing the response directly from Websphere and storing
it to a file in binary mode.

    Since there is no way I could get to the code of Websphere, do you have
any other suggestions on how to solve this issue?


  I looked at your files first time with "--print-all" option I told you
about.
  xmlsec output seems perfectly valid to me. However, the c14n might
  depend on the DTD/schema. If you have any kind of DTD/schema on the
  Websphere side then it might screw up the digest. I don't have a WebSphere
  to try it out myself so you are on your own here. And you don't need the
code,
  you just need a dump of pre-digested data. If there is a exc c14n function
when
  you might try to execute it by yourself. Also I would suggest to try c14n
instead of
   exc c14n just to see if it will work on not.

  Aleksey


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.aleksey.com/pipermail/xmlsec/attachments/20030604/254fdc61/attachment.htm


More information about the xmlsec mailing list