Does anyone knows if it is possible to use the Adobe Acrobat Digital Signature Handler while avoiding the SAVE AS step, by overwritting the file directly?
Similar to what Topaz Digital Signature pad software does, by accepting the digital signature and saving the document inline directly without confirmation?
We have PDFs documents in a Sharepoint Document Library which are part of some business workflows. Everytime managers/supervisors open documents and electronically sign, adobe opens up a "SAVE AS" window allowing to change name or overwrite exiting file. This creates two problems: 1) Allowing end-users to change name of files inadvertinly, and 2) Field Columns properties of the document in the library loose their contents, since the library detects this as a new document.
How to use Adobe Digital ID handlers and save inline the document that was just signed without asking to SAVE AS or overwrite the document?
Any advice is welcome,
thank you,
Digital Signature avoiding SAVE AS (overwritting document)
2011-03-22 20:10:28
My Product Information:
Acrobat Pro 8.1.4, Windows
Acrobat Pro 8.1.4, Windows
2011-05-03 13:33:30
#1
I would also appreciate any insight on this issue.
2011-05-05 15:15:35
#2
I too have a similar problem.
Long ago I made a proposed revision form for our office manual using Adobe Pro 7.0.5. I had 7 digital signature blocks. The individual would select the block with their name and digitally sign the document. A window would open giving you several signature choices: "Sign and Save as" and "Sign and Save" Using the Sign and Save feature allowed the document to be signed within the document itself. The document would then be emailed to next person for signature.
Years later (now) we updated to 9.3.1. Now the document no longer works the same. The signature window opens giving you only one choice: "Sign" Selecting "Sign" brings up the "Save as" window. You then have two choices: Rename the document and save or keep the same name of the document and save. Either choice allows for saving the document anywhere. If you don't change the name or location you then are prompted to replace the document after selecting save. In other words overwriting the previously opened document.
Why/what happened to the original feature to just sign and save the document within the document itself? Is it possible to activate this feature again? Or are we stuck with this "new and improved method?"
We use an XP platform
Thanks
Long ago I made a proposed revision form for our office manual using Adobe Pro 7.0.5. I had 7 digital signature blocks. The individual would select the block with their name and digitally sign the document. A window would open giving you several signature choices: "Sign and Save as" and "Sign and Save" Using the Sign and Save feature allowed the document to be signed within the document itself. The document would then be emailed to next person for signature.
Years later (now) we updated to 9.3.1. Now the document no longer works the same. The signature window opens giving you only one choice: "Sign" Selecting "Sign" brings up the "Save as" window. You then have two choices: Rename the document and save or keep the same name of the document and save. Either choice allows for saving the document anywhere. If you don't change the name or location you then are prompted to replace the document after selecting save. In other words overwriting the previously opened document.
Why/what happened to the original feature to just sign and save the document within the document itself? Is it possible to activate this feature again? Or are we stuck with this "new and improved method?"
We use an XP platform
Thanks
2011-05-17 22:56:41
#3
Tron,
There is no difference between the old Save option and the current Save As option where you don't supply a new name (or location). In both cases you overwrite the current open file and the new revision will contain the digital signature. Before, if you wanted to a Save operation (overwriting the existing file) You had to click the Save button from the option dialog. All we did was eliminate the option dialog. Now, if you want to Save just click the Save button in the Save As dialog. It's the same number of mouse clicks as before. In essence the Save As dialog has become the old options dialog.
Ysegura,
It a two edged sword in that if we just did a Save operation without allowing the user the option to Save to a different file, or even cancel out of the operation a lot of users would be upset that we eliminated the control they used to have. I've tested with biometric signature devices that commit the signature without allow the user to Save As and I always regret not having made a copy of the file first in case I want to change something and resign. I appreciate that you are trying to simplify the workflow, but alas, one person's simplicity is another's sense of loss of control.
If you are wondering why the Save has to occur at signing time, it's because the signature has to be computed over the bytes on disk as opposed to the bytes in memory. We could do the signature over the bytes in memory, but it leaves a security vulnerability in that someone (the bad guy in this case) could modify the bytes before the signature is committed to disk. It's much safer doing the signature over the bytes written to disk because it much harder for a hacker to manipulate the bytes on disk as opposed to those in memory. Because a signature can be a legally binding it imperative that we take the most prudent options.
Steve
There is no difference between the old Save option and the current Save As option where you don't supply a new name (or location). In both cases you overwrite the current open file and the new revision will contain the digital signature. Before, if you wanted to a Save operation (overwriting the existing file) You had to click the Save button from the option dialog. All we did was eliminate the option dialog. Now, if you want to Save just click the Save button in the Save As dialog. It's the same number of mouse clicks as before. In essence the Save As dialog has become the old options dialog.
Ysegura,
It a two edged sword in that if we just did a Save operation without allowing the user the option to Save to a different file, or even cancel out of the operation a lot of users would be upset that we eliminated the control they used to have. I've tested with biometric signature devices that commit the signature without allow the user to Save As and I always regret not having made a copy of the file first in case I want to change something and resign. I appreciate that you are trying to simplify the workflow, but alas, one person's simplicity is another's sense of loss of control.
If you are wondering why the Save has to occur at signing time, it's because the signature has to be computed over the bytes on disk as opposed to the bytes in memory. We could do the signature over the bytes in memory, but it leaves a security vulnerability in that someone (the bad guy in this case) could modify the bytes before the signature is committed to disk. It's much safer doing the signature over the bytes written to disk because it much harder for a hacker to manipulate the bytes on disk as opposed to those in memory. Because a signature can be a legally binding it imperative that we take the most prudent options.
Steve