Can you post the template that you are using and the keypair (assuming
they are test keys) to me or the list? Keypair not so necessary - I can
use my own, but the template would help.
You could try putting a bit of dummy text as the signature value - it
will get overwritten, but the loader for the Signature expects text
children in certain places and throws an exception if it doesn't find them.
Cheers,
Berin
Paul Cameron wrote:
Berin Lautenbach <berin <at> wingsofhermes.org> writes:
Paul Cameron wrote:
BTW, if the API binaries on nagoya.apache.org were accessible, it would
make
my life a lot easier. Do you know what's wrong with this site?
Nagoya is no longer available. I'll remove that link from the site
until I can figure out another place I can generate the API docs.
Cheers,
Berin
I have since downloaded the source for Xalan and Xerces, and have successfully
compiled the xml-security package using the GNU C and C++ compilers.
I was going through the set of tools that come with the package, and
discovered that the "templatesign" tool will do mostly what I wanted to do.
Unfortunately, I'm having some trouble with this. I ran it using our X509
certificate and a real XML message with the digests and signature values
removed. It returned the following message:
An error occured during signing operation
Message: Expected TEXT child of <SignatureValue>
Can you tell me what this means?
Thanks,
Paul
