DO NOT REPLY [Bug 49257] DSIGTransformXSL - Stylesheet missing in XMLSignature output

https://issues.apache.org/bugzilla/show_bug.cgi?id=49257 Scott Cantor changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|

DO NOT REPLY [Bug 49257] DSIGTransformXSL - Stylesheet missing in XMLSignature output

https://issues.apache.org/bugzilla/show_bug.cgi?id=49257 hagelkr...@a-trust.at changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution

DO NOT REPLY [Bug 49257] DSIGTransformXSL - Stylesheet missing in XMLSignature output

https://issues.apache.org/bugzilla/show_bug.cgi?id=49257 Scott Cantor changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

DO NOT REPLY [Bug 49257] New: DSIGTransformXSL - Stylesheet missing in XMLSignature output

https://issues.apache.org/bugzilla/show_bug.cgi?id=49257 Summary: DSIGTransformXSL - Stylesheet missing in XMLSignature output Product: Security Version: C++ 1.5.1 Platform: PC OS/Version: Windows NT Status: NEW

Re: XmlSignature advice

Mathias Berg wrote: Hi, i need some advice how i should build my xmlSignature document. In our application we can create many orders. And each order shall be xmlSigned. After that, the xmlSigned orders is then added to a new XmlSigned document, so we signed all orders in one document again

XmlSignature advice

Hi, i need some advice how i should build my xmlSignature document. In our application we can create many orders. And each order shall be xmlSigned. After that, the xmlSigned orders is then added to a new XmlSigned document, so we signed all orders in one document again. Now how can i add

XMLSignature and output escaped problem

When i try to add a xml block into a in my XMLSignature file. All the xml block is being escaped. What is the best way to add xml block into . I use addText on ObjectContainer. I noticed DOMResult has a flag PI_DISABLE_OUTPUT_ESCAPING. How can i use that

Re: XMLSignature::getSignatureMethod() broken?

Scott Cantor wrote: Looks like a bug to me. Bugs need to be reported to issues.apache.org/bugzilla. Thanks, -- Scott Fine, I'll report it. Thomas

RE: XMLSignature::getSignatureMethod() broken?

> Looks like a bug to me. Bugs need to be reported to issues.apache.org/bugzilla. Thanks, -- Scott

XMLSignature::getSignatureMethod() broken?

With a signed xml-document in 'doc', the following code fragment for getting the signature method worked in xml-security-c 1.3.0: XSECProvider prov; DSIGSignature *sig = prov.newSignatureFromDOM(doc); sig->load(); signatureMethod meth= sig->getSignatureMethod(); Since the commit

Re: XMLSignature

So I went back and checked the source history and it appears that the XMLSignature class used to be non-final way back in 2002. There are no useful comments or bug associated with this change so it appears the rationale for this change has been lost, unless one of the previous active committers

Re: XMLSignature

17:31 Para: security-dev@xml.apache.org Asunto: Re: XMLSignature Hi Sean, Thank you for your response. I would like implement a XAdESSignature class which extends the org.apache.xml.security.signature.XMLSignature class. Regards, Julien Pasquier Sean Mullan wrote : Julien PASQUIER wrote:

DO NOT REPLY [Bug 41858] Namespace problem when initializing XMLSignature in version 1.4.0

https://issues.apache.org/bugzilla/show_bug.cgi?id=41858 coheigea changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|

DO NOT REPLY [Bug 41858] Namespace problem when initializing XMLSignature in version 1.4.0

https://issues.apache.org/bugzilla/show_bug.cgi?id=41858 --- Comment #7 from sean.mul...@sun.com 2009-07-14 07:05:39 PST --- Yes, I think it can be marked RESOLVED. It was originally marked NEEDINFO because I wanted a sample program. The current status is that I was waiting for the submitter

DO NOT REPLY [Bug 41858] Namespace problem when initializing XMLSignature in version 1.4.0

https://issues.apache.org/bugzilla/show_bug.cgi?id=41858 --- Comment #6 from coheigea 2009-07-14 06:48:48 PST --- Is there a reason this bug is marked as "NEEDINFO"? From the comments it seems like the bug is in another open source project, not XML Security. Can this be marked as "RESOLVED"

RE: XMLSignature

ginal- De: Julien PASQUIER [mailto:julienpasqu...@free.fr] Enviado el: lunes, 13 de julio de 2009 17:31 Para: security-dev@xml.apache.org Asunto: Re: XMLSignature Hi Sean, Thank you for your response. I would like implement a XAdESSignature class which extends the org.apache.xml.security.signature.XMLSig

Re: XMLSignature

XMLSignature class but it is not possible because XMLSignature class is declared as "final". Is it possible te remove the "final" declaration from the XMLSecurity class in the next release of XMLSecurity (v1.4.3) ? The XMLSignature classes (org.apache.xml.security.signat

Re: XMLSignature

Sean Mullan wrote: Julien PASQUIER wrote: Hi all, I would like to create a class which extends the XMLSignature class but it is not possible because XMLSignature class is declared as "final". Is it possible te remove the "final" declaration from the XMLSecurity class in

Re: XMLSignature

Julien PASQUIER wrote: Hi all, I would like to create a class which extends the XMLSignature class but it is not possible because XMLSignature class is declared as "final". Is it possible te remove the "final" declaration from the XMLSecurity class in the next release of

XMLSignature

Hi all, I would like to create a class which extends the XMLSignature class but it is not possible because XMLSignature class is declared as "final". Is it possible te remove the "final" declaration from the XMLSecurity class in the next release of XMLSecurity (v1.4.3)

DO NOT REPLY [Bug 47097] Reusing XMLSignature for signing and verifying fails on same thread

https://issues.apache.org/bugzilla/show_bug.cgi?id=47097 coheigea changed: What|Removed |Added CC||vmaha...@amberpoint.com --- Comment

DO NOT REPLY [Bug 47097] Reusing XMLSignature for signing and verifying fails on same thread

https://issues.apache.org/bugzilla/show_bug.cgi?id=47097 sean.mul...@sun.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

DO NOT REPLY [Bug 47097] New: Reusing XMLSignature for signing and verifying fails on same thread

https://issues.apache.org/bugzilla/show_bug.cgi?id=47097 Summary: Reusing XMLSignature for signing and verifying fails on same thread Product: Security Version: Java 1.4.2 Platform: PC URL: http://mail

RE: Reusing XMLSignature for signing and verifying

Sean Mullan wrote on 2009-03-25: > JSR 105 is consistent with your view and documents the behavior. If the > contents of the document are subsequently modified, then you need to > instantiate a new XMLSignature object. Well, in this case, nothing's being modified. What happens is yo

Re: Reusing XMLSignature for signing and verifying

ently modified, then you need to instantiate a new XMLSignature object. --Sean Scott Cantor wrote: Sean Mullan wrote on 2009-03-25: I don't think the behavior is intentional. Can you please file a bug at http://issues.apache.org/bugzilla in the security category and attach your test case?

RE: Reusing XMLSignature for signing and verifying

Sean Mullan wrote on 2009-03-25: > I don't think the behavior is intentional. Can you please file a bug at > http://issues.apache.org/bugzilla in the security category and attach > your test case? At least dating back to the 1.2 days, it was quite intentional. I found numerous issues with reusing

Re: Reusing XMLSignature for signing and verifying

re.XMLSignature. Unfortunately, if the nodes are reused, the same instance of XMLSignature is used for verifying after being used for signing. This causes an exception: org.apache.xml.security.signature.XMLSignatureException: object not initialized for verification If I run the verification

Reusing XMLSignature for signing and verifying

) keeps an association between the DOM element and the instance of org.apache.xml.security.signature.XMLSignature. Unfortunately, if the nodes are reused, the same instance of XMLSignature is used for verifying after being used for signing. This causes an

DO NOT REPLY [Bug 45475] XMLSignature::getKeyInfo method modifies document

https://issues.apache.org/bugzilla/show_bug.cgi?id=45475 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

DO NOT REPLY [Bug 45475] New: XMLSignature:: getKeyInfo method modifies document

https://issues.apache.org/bugzilla/show_bug.cgi?id=45475 Summary: XMLSignature::getKeyInfo method modifies document Product: Security Version: unspecified Platform: PC OS/Version: Windows XP Status: NEW Severity: critical

DO NOT REPLY [Bug 44999] DOMException is thrown at XMLSignature creation (1 .4.2 beta2)

r "" to the _prefixMappingsBindings Map. My fix puts "xmlns" into the map. It seemed more logical. > Or, maybe, different checks should be performed at XMLSignature:200-208 and > similar places, first getting ElementProxy.getDefaultPrefix(namespace); and > then, if

DO NOT REPLY [Bug 44999] New: DOMException is thrown at XMLSignature creation (1.4.2 beta2)

https://issues.apache.org/bugzilla/show_bug.cgi?id=44999 Summary: DOMException is thrown at XMLSignature creation (1.4.2 beta2) Product: Security Version: unspecified Platform: PC OS/Version: All Status: NEW

DO NOT REPLY [Bug 44956] Concurrent creation of a XMLSignature instance produces an ArrayIndexOutOfBoundsException

https://issues.apache.org/bugzilla/show_bug.cgi?id=44956 Raul Benito <[EMAIL PROTECTED]> changed: What|Removed |Added Status|NEW |RESOLVED

DO NOT REPLY [Bug 44956] Concurrent creation of a XMLSignature instance produces an ArrayIndexOutOfBoundsException

t.add(Unknown Source) > > at org.apache.xml.security.keys.KeyInfo.(Unknown Source) > > at org.apache.xml.security.signature.XMLSignature.(Unknown Source) > > ... > > > > The XMLSignature constructor being used is: > > public XMLSignature(Element element, String B

DO NOT REPLY [Bug 44956] Concurrent creation of a XMLSignature instance produces an ArrayIndexOutOfBoundsException

nknown Source) > ... > > The XMLSignature constructor being used is: > public XMLSignature(Element element, String BaseURI) > > Looking further at the sources I found out that: > 1. The KeyInfo constructor being invoked by the XMLSignature constructor must > be public KeyInfo(Element

DO NOT REPLY [Bug 44956] New: Concurrent creation of a XMLSignature instance produces an ArrayIndexOutOfBoundsException

https://issues.apache.org/bugzilla/show_bug.cgi?id=44956 Summary: Concurrent creation of a XMLSignature instance produces an ArrayIndexOutOfBoundsException Product: Security Version: unspecified Platform: PC OS/Version: All

DO NOT REPLY [Bug 40896] - Cannot sign-verify twice in the same thread with different XMLSignature instances

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 41858] - Namespace problem when initializing XMLSignature in version 1.4.0

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 41858] - Namespace problem when initializing XMLSignature in version 1.4.0

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 41858] - Namespace problem when initializing XMLSignature in version 1.4.0

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 41858] - Namespace problem when initializing XMLSignature in version 1.4.0

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 41858] - Namespace problem when initializing XMLSignature in version 1.4.0

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 41858] New: - Namespace problem when initializing XMLSignature in version 1.4.0

gzilla/show_bug.cgi?id=41858 Summary: Namespace problem when initializing XMLSignature in version 1.4.0 Product: Security Version: unspecified Platform: Sun OS/Version: Linux Status: NEW Severity:

Re: XMLSignature class - The signer output stream is closed before signing operation

/Imposible } - Original Message - From: "Marcin Cinik" <[EMAIL PROTECTED]> To: Sent: Wednesday, March 14, 2007 12:19 PM Subject: RE: XMLSignature class - The signer output stream is closed before signing operation There should rather be: try { so.close

RE: XMLSignature class - The signer output stream is closed befor e signing operation

To: security-dev@xml.apache.org Subject: XMLSignature class - The signer output stream is closed before signing operation Hi, In the org.apache.xml.security.signature.XMLSignature class of the java XML Security v1.4, I don't understand a piece of code in the "public void sign(Key

XMLSignature class - The signer output stream is closed before signing operation

Hi, In the org.apache.xml.security.signature.XMLSignature class of the java XML Security v1.4, I don't understand a piece of code in the "public void sign(Key signingKey)" method. - // generate digest values for all References in this SignedInfo si.generateDigestValu

Re: Cannot sign-verify twice in the same thread with different XMLSignature instances

Done. Thank you sir!. -- dims On 11/6/06, Sean Mullan <[EMAIL PROTECTED]> wrote: Davanum Srinivas wrote: > Raul, Sean, > > Looks like the prev patch from me for parseFragment does not really > help much :( As XMLCipher has a private constructor and the > parseFragment is in a private class Seri

Re: Cannot sign-verify twice in the same thread with different XMLSignature instances

Davanum Srinivas wrote: Raul, Sean, Looks like the prev patch from me for parseFragment does not really help much :( As XMLCipher has a private constructor and the parseFragment is in a private class Serializer inside that class. So we are back to square one... Can you first back out your fix

Re: Cannot sign-verify twice in the same thread with different XMLSignature instances

Hi Raul, thanks a lot for the quick fix ! Thanks, Ruchith On 11/5/06, Raul Benito <[EMAIL PROTECTED]> wrote: On 11/5/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote: > Hi Raul, > > On 11/5/06, Raul Benito <[EMAIL PROTECTED]> wrote: > > You Wss4j guy a

Re: Cannot sign-verify twice in the same thread with different XMLSignature instances

On 11/5/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote: Hi Raul, On 11/5/06, Raul Benito <[EMAIL PROTECTED]> wrote: > You Wss4j guy always using untested XMLSignature constructors!!! ;) > Just joking. You hit again another XMLSignature constructor that there > is no un

DO NOT REPLY [Bug 40896] - Cannot sign-verify twice in the same thread with different XMLSignature instances

|FIXED --- Additional Comments From [EMAIL PROTECTED] 2006-11-05 08:55 --- You Wss4j guy always using untested XMLSignature constructors!!! ;) Just joking. You hit again another XMLSignature constructor that there is no unit test for it. The problem is that for creating new Signatures(for s

Re: Cannot sign-verify twice in the same thread with different XMLSignature instances

> Can you raise a bug report in bugzilla, for proper tracking? will do. Done : http://issues.apache.org/bugzilla/show_bug.cgi?id=40896 Thanks, Ruchith -- www.ruchith.org

DO NOT REPLY [Bug 40896] - Cannot sign-verify twice in the same thread with different XMLSignature instances

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 40896] New: - Cannot sign-verify twice in the same thread with different XMLSignature instances

gzilla/show_bug.cgi?id=40896 Summary: Cannot sign-verify twice in the same thread with different XMLSignature instances Product: Security Version: unspecified Platform: Other OS/Version: Linux Status: NEW Se

Re: Cannot sign-verify twice in the same thread with different XMLSignature instances

Hi Raul, On 11/5/06, Raul Benito <[EMAIL PROTECTED]> wrote: You Wss4j guy always using untested XMLSignature constructors!!! ;) Just joking. You hit again another XMLSignature constructor that there is no unit test for it. The problem is that for creating new Signatures(for signing)

Re: Cannot sign-verify twice in the same thread with different XMLSignature instances

b the release cycle? and we can experiment a little bit on the HEAD. Raul, Any help would be immensely welcome! Thanks, dims On 11/5/06, Raul Benito <[EMAIL PROTECTED]> wrote: You Wss4j guy always using untested XMLSignature constructors!!! ;) Just joking. You hit again another X

Re: Cannot sign-verify twice in the same thread with different XMLSignature instances

You Wss4j guy always using untested XMLSignature constructors!!! ;) Just joking. You hit again another XMLSignature constructor that there is no unit test for it. The problem is that for creating new Signatures(for signing) public XMLSignature( Document doc, String BaseURI, Element

Re: Cannot sign-verify twice in the same thread with different XMLSignature instances

see > the problem. > Did the problem arise when you do something like this? > PrivateKey xk; PublicKey pk=xk.getPublickKey(); > XMLSignature s1=...; > XMLSignature s2=...; > s1.sign(xk); > s2.sign(xk); > s1.checkSignatureValue(pk); > > Or other kind of sequence? > Re

Re: Cannot sign-verify twice in the same thread with different XMLSignature instances

Key pk=xk.getPublickKey(); XMLSignature s1=...; XMLSignature s2=...; s1.sign(xk); s2.sign(xk); s1.checkSignatureValue(pk); Or other kind of sequence? Regards, On 11/3/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote: > Hi Raul, > > I'm using the SVN head (revision : 470741). > > I&#x

Re: Cannot sign-verify twice in the same thread with different XMLSignature instances

Hi Ruchith, It is not feasible for me to checkout the whole wss4j in order to see the problem. Did the problem arise when you do something like this? PrivateKey xk; PublicKey pk=xk.getPublickKey(); XMLSignature s1=...; XMLSignature s2=...; s1.sign(xk); s2.sign(xk); s1.checkSignatureValue(pk

Re: Cannot sign-verify twice in the same thread with different XMLSignature instances

itialized for verification" exception when trying to do sign and > verify *twice* in the same thread, using different XMLSignature > instances. > > I tracked this down to the use of "keysVerify" thread local tracker in > org.apache.xml.security.algorithms.SignatureAlgo

Re: Cannot sign-verify twice in the same thread with different XMLSignature instances

? Regards, Raul On 11/3/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote: Hi Devs, I ran into an "java.security.SignatureException: object not initialized for verification" exception when trying to do sign and verify *twice* in the same thread, using different XMLSignature instances.

Cannot sign-verify twice in the same thread with different XMLSignature instances

Hi Devs, I ran into an "java.security.SignatureException: object not initialized for verification" exception when trying to do sign and verify *twice* in the same thread, using different XMLSignature instances. I tracked this down to the use of "keysVerify" thr

RE: Examples for XMLSignature with private key on a Smartcard

t: Tuesday, January 24, 2006 2:02 PM To: security-dev@xml.apache.org Subject: Re: Examples for XMLSignature with private key on a Smartcard Hi Sean, Thank you for your response. It seems that my question wasn't as clear as I thought it would be. I Haven't got any problems in usi

RE: Examples for XMLSignature with private key on a Smartcard

Title: RE: Examples for XMLSignature with private key on a Smartcard Hi, Did you by any chance happen to solve this problem? Are you accessing the certificate on the smartcard using JSS? It so, the problem is in the providers that register when you initialize the jss, which causes

Re: XMLSignature constructor error : The requested algorithm does not exist

Do you have a test case? --Sean Larchier Christophe wrote: Hi all, I use xml-security-1_3_0. I execute the following code : logger.info("arg2=" + NAMESPACE_URI_DS); logger.info("arg3=" + NAMESPACE_URI_DS + algo); signature = new X

XMLSignature constructor error : The requested algorithm does not exist

Title: XMLSignature constructor error : The requested algorithm does not exist Hi all, I use xml-security-1_3_0. I execute the following code : logger.info("arg2=" + NAMESPACE_URI_DS); logger.info("arg3=" + NAMESPACE_URI_DS + algo);    signatur

Re: Examples for XMLSignature with private key on a Smartcard

Ulrich Ackermann wrote: Hi Sean, Thank you for your response. It seems that my question wasn't as clear as I thought it would be. I Haven't got any problems in using a Smartcard. I DO have got problems in getting the right hash, that has to be encrypted with the private key on the Smartcard (or

Re: Examples for XMLSignature with private key on a Smartcard

kermann wrote: > Hi, > > I've been looking quit a while without any luck for any advice or > examples for getting an XMLSignature done with the constraint, that > the private key can't be offered the XML Security framework (because > he is on a Smartcard, e.g.). All atte

Re: Examples for XMLSignature with private key on a Smartcard

any advice or examples for getting an XMLSignature done with the constraint, that the private key can't be offered the XML Security framework (because he is on a Smartcard, e.g.). All attempts getting or creating the "right" digest and encrypting it with the private key outside didn&#x

Examples for XMLSignature with private key on a Smartcard

Hi, I've been looking quit a while without any luck for any advice or examples for getting an XMLSignature done with the constraint, that the private key can't be offered the XML Security framework (because he is on a Smartcard, e.g.). All attempts getting or creating the "ri

Re: [java] XMLSignature ctor

unsubscribe  

Re: [java] XMLSignature ctor

ng Eclipse IDE. This is my call stack: ElementNode2.getAttributeNS(String, String) line: 409 SignatureAlgorithm.getURI() line: 303 SignatureAlgorithm.(Element, String) line: 124 SignedInfo.(Document, Element, Element) line: 136 XMLSignature.(Document, String, Element, Element) line: 229 TestXSEC.m

RE: [java] XMLSignature ctor

I have tried to debug, but without any luck. :( I'm using Eclipse IDE. This is my call stack: ElementNode2.getAttributeNS(String, String) line: 409 SignatureAlgorithm.getURI() line: 303 SignatureAlgorithm.(Element, String) line: 124 SignedInfo.(Document, Element, Element) line: 136 XMLSign

Re: [java] XMLSignature ctor

I'm attaching XML file I was using for testing purposes. Best regards, Milan -Original Message- From: Milan Tomic [mailto:[EMAIL PROTECTED] Sent: Friday, October 14, 2005 11:49 AM To: security-dev@xml.apache.org Subject: RE: [java] XMLSignature ctor Yes, the docSig par

RE: [java] XMLSignature ctor

[mailto:[EMAIL PROTECTED] Sent: Friday, October 14, 2005 11:49 AM To: security-dev@xml.apache.org Subject: RE: [java] XMLSignature ctor > Yes, the docSig parameter should be the > SignatureMethod element and not > the Signature element. Thank you, Sean. The error message a little confused me.

RE: [java] XMLSignature ctor

> Yes, the docSig parameter should be the > SignatureMethod element and not > the Signature element. Thank you, Sean. The error message a little confused me. I did as you suggested and now I got this exception in XMLSignature ctor: org.apache.xml.security.signature.XMLSignatureExcep

Re: [java] XMLSignature ctor

Hi Milan, Milan Tomic wrote: I'm using XMLSignature ctor like this: XMLSignature sig = new XMLSignature(doc, BaseURI, docSig, docCan); and got the following error: org.apache.xml.security.exceptions.XMLSecurityException: Cannot create a http://www.w3.org/2000/09/xm

[java] XMLSignature ctor

  I'm using XMLSignature ctor like this:   XMLSignature sig = new XMLSignature(doc, BaseURI, docSig, docCan);   and got the following error:   org.apache.xml.security.exceptions.XMLSecurityException: Cannot create a http://www.w3.org/2000/09/xmldsig#:Signature from a http://w

Re: Is the XMLSignature class blocking a file?

Rune yahoo.com> writes: > > Hi, > I had the exact same problem I looked into it and discovered that > it was due to that the FileInputStream in the ResourceResolverSpi > (ResolverLocalFilesystem) I used was never closed. > I was not able just to close the stream since it is used later on, > s

Re: Is the XMLSignature class blocking a file?

Hi, I had the exact same problem I looked into it and discovered that it was due to that the FileInputStream in the ResourceResolverSpi (ResolverLocalFilesystem) I used was never closed. I was not able just to close the stream since it is used later on, so I circumvented the problem by reading t

RE: XMLSignature with RSA_MD5 key

l.apache.org > Subject: XMLSignature with RSA_MD5 key > > > Hi all... > > I'm having problems in signing an > "org.apache.axis.message.SOAPEnvelope" > as an "org.w3c.Document". > > I'm passing a RSAPrivateKey with md5 in the > XMLSIg

XMLSignature with RSA_MD5 key

Hi all... I'm having problems in signing an "org.apache.axis.message.SOAPEnvelope" as an "org.w3c.Document". I'm passing a RSAPrivateKey with md5 in the XMLSIgnature.sign() method. # iaik.security.rsa.RSAPrivateKey priv = new aik.security.rsa.RSAPrivateKey(THE MODULUS, THE EXPONENT); xm

Is the XMLSignature class blocking a file?

Hi,   I'm using the XMLSignature class to verify the sign of a document: I'm receiving the signature file and the original file as byte arrays, so I create a temporal directory, and then write 2 files into the directory, one for the signature file and the other one for the original

Re: XMLSignature sign - avoid namespaces on every element

> > Is there any way to stop the sign method of XMLSignature adding namespace > information to every element? When I use it the argument list in my SOAP > message becomes 7 times larger because namespace information is added to > every element. For long element lists this is causing

XMLSignature sign - avoid namespaces on every element

Is there any way to stop the sign method of XMLSignature adding namespace information to every element? When I use it the argument list in my SOAP message becomes 7 times larger because namespace information is added to every element. For long element lists this is causing an OutOfMemory error

Re: Significance of 'baseURI' in XMLSignature constructor/Signing issues

Hi Peter, pacow wrote: also, I have attached a copy of my SOAP request. i add a reference in the signature to '#Body', do i then need to add an id='Body' attribute to the soap:Body tag, or elsewhere? Yes, you would need to add an attribute to the soap:Body element. Adding SOAP-SEC:id="Body" att

Significance of 'baseURI' in XMLSignature constructor/Signing issues

What is the significance of the variable 'baseURI' in the XMLSignature constructor? If I am not refefring to an external file, and there are no relative URIs in my document, can i leave baseURI blank? or is there some way to indicate that the generated document is the location of t

RE: [Java] NullPointerException with XMLSignature transformations

XMLSignature transformations Hi, We're experiencing a NullPointerException when we try to sign an XML document when the transformations are being performed. We've been able to trace the cause of the problem, and are wondering if this is a bug in the XML signature code. What happens is: W

[Java] NullPointerException with XMLSignature transformations

Hi, We're experiencing a NullPointerException when we try to sign an XML document when the transformations are being performed. We've been able to trace the cause of the problem, and are wondering if this is a bug in the XML signature code. What happens is: We use Axis with HTTP web services. Befo