Appending new pages to signed documents now makes Acrobat 9 and Reader 9 mark signature as invalid


hello!

have developed service appends additional pages existing pdf documents. of documents service works on happen signed. service appends pages using incremental updates, signed contents left untouched. makes acrobat 8 , reader 8 display signature state "valid subsequent changes" ok , no 1 complains about.

along come acrobat 9 , reader 9, , of sudden signature state "invalid" users complain about. telling them inspecting signature state details can see signed content still untouched , actual change recognized appended pages, doesn't either in turn forward documents customers don't accept documents if adobe reader sais signatures invalid.

know way new pages can added signed document without having new adobe program versions choke on them?

hint involves adding flag original unsigned document or signature users in question can tweak processes. due nature of workflow, though, signing unfortunately must happen before service can add new pages.

best regards, mikel.

way, signatures in question regular approval signatures, nothing fancy, not certifying signatures (which indeed can forbid changes or @ least changes form fill-ins , annotations)...



More discussions in Acrobat SDK


adobe

Comments

Popular posts from this blog

invalid use of void expresion in FlexiTimer2 library

error: a function-definition is not allowed here before '{' token

LED Strip Code