Support for ds:Manifest about xades4j

[GoogleCodeExporter]

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

• Changed state: Accepted
• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

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

Original comment by [email protected] on 10 Dec 2012 at 2:48

[GoogleCodeExporter]

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]

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 [email protected] on 14 Dec 2012 at 3:11