[
https://issues.apache.org/jira/browse/FOP-3299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18067970#comment-18067970
]
DaveLaw commented on FOP-3299:
------------------------------
In short, NO !!
But nearly: you will need to provide a Helvetica font. ;)
(and modify one line in my [^Fop3299_Example.java][^pom.xml]source to specify
its location on your box)
Here's a start-to-finish working example, which will generate the Keystore &
the PDF all inline.
It's JDK 17 (sorry, writing Java 8 is just too painful).
There are a few dependencies, so the pom.xml is also attached.
If you run the resulting PDF through the pdfForge validator, it fails (press
"Detail" to show the detail)
Change...
{code:java}
org.apache.fop.pdf.PDFSignature{code}
...to not write out the DigestMethod & it will pass the test.
> PDF/A-3u with Digital Signature fails pdfForge Validator
> --------------------------------------------------------
>
> Key: FOP-3299
> URL: https://issues.apache.org/jira/browse/FOP-3299
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
> Affects Versions: 2.11
> Environment: Windows 10, Eclipse 2026-03, JDK 17
> Reporter: DaveLaw
> Priority: Major
> Fix For: main
>
> Attachments: Fop3299_Example.java, pom.xml
>
>
> I tried validating a with-fop digitally signed "PDF/A-3u" using the pdfForge
> Validator.
> [https://www.pdfforge.org/online/en/validate-pdfa]
> It complained about the following:
> *ISO 19005-3:2012 §6.1.12*
> _"If DocMDP is present, then the Signature References dictionary (ISO
> 32000-1:2008, 12.8.1, Table 253) shall not contain the keys DigestLocation,
> DigestMethod, and DigestValue."_
> I made a change to org.apache.fop.pdf.PDFSignature, commenting out the
> following line:
> put("DigestMethod", new PDFName("SHA1"));
> pdfForge, thereafter, was happy with the generated PDF.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
