Vytek / xades4j

Automatically exported from code.google.com/p/xades4j
GNU Lesser General Public License v3.0
0 stars 0 forks source link

Support for ds:Manifest #28

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. XAdES4J does not support the creation of a signature that references a 
ds:Manifest.  See http://www.w3.org/TR/xmldsig-core/#sec-o-Manifest. 

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
1.2.0
Windows 7

Please provide any additional information below.
This feature is not high priority.

Original issue reported on code.google.com by clementp...@gmail.com on 1 Dec 2011 at 3:12

GoogleCodeExporter commented 9 years ago

Original comment by luis.fgoncalv on 26 Dec 2011 at 6:07

GoogleCodeExporter commented 9 years ago
I'll need to add support for ds:Manifest to xades4j for my project. Any hints 
will be appreciated. Thank you.

Original comment by david.mi...@gmail.com on 10 Dec 2012 at 2:48

GoogleCodeExporter commented 9 years ago
One of the uses cases that the XML-DSIG spec states for manifests is reusing 
them across signatures. I'm not sure this is easy to fully accommodate in the 
lib.

Anyway, for signature production:

I guess SignedDataObjects could also have a withManifest(Manifest m) method. A 
Manifest would be/have a collection of DataObjectDesc. Then 
DataObjectDescsProcessor would have to take this into account to add the 
manifests to the XMLSignature and keep track of their references.

For signature verification:

Apache Santuario has an option that indicates whether it should follow 
manifests. We may need this to be exposed somewhere. Also, 
SignatureUtils.processReferences(...) needs to consider the Manifests.

Original comment by luis.fgoncalv on 10 Dec 2012 at 10:50

GoogleCodeExporter commented 9 years ago
I don't think my requirements allow for a generic solution. I must use BES 
(therefore only one ds:Object is allowed), with its dS:Object containing a 
Manifest and nothing else (we don't want any of the Qualifying properties).
Therefore, I'm looking at writing my own implementation of SignerBES.java

Original comment by david.mi...@gmail.com on 14 Dec 2012 at 3:11