Ahmet-Kaplan / xades4j

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

Missing DataObjectFormat to conform to XAdES Baseline Profile #73

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Sign a document using XAdES4j (BES)
2. Upload the document to the XAdES Baseline Profile conformance checker tool 
or manually look at the XML.

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

The XAdES Baseline Profile expects an xadesv132:DataObjectFormat for each 
signed data object except the SignedProperties element. But there are no 
DataObjectFormat present.

What version of the product are you using?
1.3.0

Please provide any additional information below.
More details including complete report from conformance tool in the downstream 
SignServer ticket:
https://jira.primekey.se/browse/DSS-694

Original issue reported on code.google.com by markuski...@gmail.com on 13 Sep 2013 at 9:24

GoogleCodeExporter commented 9 years ago
xades4j supports adding the DataObjectFormat over each signed data object. It's 
not mandatory to reflect the XAdES spec and I don't think its presence should 
be enforced on xades4j "BES mode".

Maybe we could have a SigningProfile that includes the additional 
checks/configs for Baseline conformance..?

Original comment by luis.fgoncalv on 13 Sep 2013 at 9:33

GoogleCodeExporter commented 9 years ago
Great, I will try adding the DataObjectFormat in my application then.

I don't know enough about XAdES4j yet to have any opinion about if there should 
be an additional profile where this is checked. It could maybe be useful but is 
probably not necessary.

Thanks,

Original comment by markuski...@gmail.com on 18 Sep 2013 at 7:28

GoogleCodeExporter commented 9 years ago

Original comment by luis.fgoncalv on 18 Sep 2013 at 9:15