Scott Cantor wrote:
Inconsistent c14n has caused us to have validation failures in the past,
and
I have found no decent way to finding out what exactly the canonicalizer
output looks like. I've had to use the debugger and set the "os" stream to
a
FileOutputStream in DOMReferen
> Inconsistent c14n has caused us to have validation failures in the past,
and
> I have found no decent way to finding out what exactly the canonicalizer
> output looks like. I've had to use the debugger and set the "os" stream to
a
> FileOutputStream in DOMReference.transform(Data, XMLCryptoContex
I would generalize that question to include the java implementation.
Inconsistent c14n has caused us to have validation failures in the past,
and I have found no decent way to finding out what exactly the
canonicalizer output looks like. I've had to use the debugger and set the
"os" stream to
Hi,
The Java/JSR 105 API also supports this and the underlying JCE
cryptographic support for RSA-SHA256 has been in Sun's JDK since 1.4.2.
However. you must specify the URI when generating the SignatureMethod,
as there is no String constant defined for it yet. So do the following:
XMLSignat
I'm pretty sure BouncyCastle supports it:
http://www.bouncycastle.org/java.html
Apache WSS4J uses BouncyCastle as the crypto provider, and some of the
tests use http://www.w3.org/2001/04/xmldsig-more#rsa-sha256 as the
signature algorithm.
Colm.
-Original Message-
From: Lukas Jedlicka [
Hi,
I have a question about creating xml signature usig RSAwithSHA256 algorithm.
My application receives and sends signed XMLS. My application is written in
Java 1.5 and uses Apache xmlsec_1_4_2.jar library for signing XML files. It
uses javax.xml.crypto.dsig.SignatureMethod.RSA_SHA1 algorithm for
