[ 
https://issues.apache.org/jira/browse/PDFBOX-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17229872#comment-17229872
 ] 

Maruan Sahyoun commented on PDFBOX-5012:
----------------------------------------

adding flags would allow finer control but on the other hand that also assumes 
that the user understands where the issue is coming from. Although PDFBox is 
somewhat low level many of our users don't have in depth knowledge about the 
internals and expect that it just works. RemoveXfaForSigning would only work 
for static XFA forms not for dynamic ones, something that would need to be 
documented ...

You are correct about the usage rights signature. Now, as we can't keep it when 
removing the XFA (as you correctly stated it will be invalidated anyway) this 
might also change some of the capabilities. I'm not so concerned about form 
filling (as current Reader versions do support local saving for AcroForm field 
content which hasn't been the case in earlier versions) but we also loose 
capabilities such as web service requests etc. if the form has been enabled for 
that. So after signing the PDF may no longer work to the users expectation 
without a clear understanding why that happened.

Maybe the best is to not go down that route but throw an exception ...

The new {{PDDocumentFixup}} capability when retrieving an AcroForm could offer 
an approach. We could provide a RemoveXFA fixup so that one can decide if he'd 
like to apply that.

> Signature Field Not Recognize
> -----------------------------
>
>                 Key: PDFBOX-5012
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-5012
>             Project: PDFBox
>          Issue Type: Bug
>          Components: Signing
>    Affects Versions: 2.0.21
>            Reporter: Marco Monacelli
>            Priority: Major
>              Labels: XFA
>         Attachments: PDF_orig_anon.pdf
>
>
> We have a document with a signature field prepared. 
> We can locate the signature field and add the signature to it, but the result 
> is still an unsigned document.
> CosWriter not identifies the field as a signature field.
> The document has been made anonymous but the result is the same as the 
> original.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to