New Forum | Previous | Next | (P-PDF) Developers
Topic: activePDF & signatures
Conf: (P-PDF) Developers, Msg: 121949
Date: 11/11/2004 09:04 PM
I have a few activePDF/Acrobat Signatures questions that hopefully someone might shed some light on. I haven't worked with the activePDF toolkit for too long so forgive any misunderstandings I might have ;)
1) I have a PDF template that I receive in binary format using InputByteStream and which I O/P using the OutputByteStream property. If there is an Acrobat Signature field (field type '/Sig', I think) on the template, will this be O/P correctly? In other words, when the O/P binary stream is rendered into a .PDF, can I then digitally sign the PDF or will the Signature field be corrupt?
2) Is there anyway of handling PDFs that have been digitally signed using Acrobat Signature? By handle, I mean adding a blank page, flattening all the fields, etc. I suspect no as the signature field is there to prevent any changes to the PDF and by adding a blank page, etc.....
3) If I have a signed PDF, can I simply accept the relevant binary stream and create a binary output stream while retaining a valid/non-corrupt digital signature field? I tried this and the Signature field was then displayed in Acrobat as being corrupt...
4) An easy one! Can I add a field to the PDF via activePDF at runtime? I need to add a dynamically produced URL using activePDF so that a client side app can pick it up for further processing. We were hoping to add an invisible field. Can't see anything in the activePDF doco that suggests this is possible. The only ways I can see are (a) to use the CustomDocInfo property (not sure if the client side app will be able to access this) or (b) to add the field to the template PDF at design time and then to flatten it with the URL and a relevant SetFormFieldData flag to make invisible.
Apologies for the length of the post!