Unlocking a signed document

After signing with electronic signature I locked the document. How do I unlock it?

Right-click on the signature field that locked the document select "Clear Signature". This assumes you were the one who applied the signature that locked the document.

Similar Messages

Digital Signatures and editing signed documents

Situation - A medical office wants to digitally sign a document after it has been edited (to make it a legal order) but have the form remain unlocked so it can be edited again. They want to be able to accomplish this on a single instance of the form without using the server solution just a form designed in LiveCycle with Javascript powering the transactions. Is this possible?

You can edit a signed PDF document (assuming you are not using the field collection feature). This will not "Invalidate" the signature, but it will change the status of the signature.
I have attached two screen shots to illustrate... To generate these, I signed a PDF, changed some data and re-validated the signature.
ValidationStatus.gif shows the status of the actual signature.
DocStatus.gif shows a "roll-up" status (meaning it checks all signatures on a doc and displays an overview) of the signed document.
Regards
Steve

'error while signing document'

i got this error ('error while signing document') on my 1st attempt to use the service. simple 4 page PDF, no doc. security, same error both b4 & after i edited my user profile (i filled in the missing details & changed the default signature image).
cheers,

Hi,
I am also getting this error while attempting to sign a document. I have checked the first and name fields in my default signature profile for any non-English characters but I am still getting this error. I have also tested with a different signature profile with same results. Please advise if there are
other fields I need to check.
Thanks.

Links no longer work after signing document

Links no longer work after signing document - I have updated to latest version and run installation repair, is this a problem or is it supposed to do that?

Hi;
This question would be best asked in the Acrobat signatures Forums, it is related to using Adobe Acrobat/Reader and does not have anything to do with the online service, Adobe Fill & Sign. Someone should be able to answer your question here: https://forums.adobe.com/community/acrobat/security_%26_digital_signatures
Thanks,
Josh

When saving a signed document can the -signed appellation be turned off?

When you go to save a document which you have digitally signed, the program automatically appends '-signed' to the end of the file name. This is not ideal for my purposes - is there any way to turn this function off? Also it it possible to turn off the prompt that asks me if I'd like to email the signed document? I've gone through every screen in preferences but I can't seem to find anything for this. I'm using Adobe Reader XI 11.0.5.
Thank in advance!

Not that I know of. Reader and Acrobat want you to have a new copy of the signed document and an original copy of the unsigned version, hence the behavior you do not want. You can always do a save change the name of the signed document to the original name if you desire.

Not able to attach final signed document in the contract document

Dear Experts,
The upload field for final signed document in the contract document is visible only for the latest/last contract document if there are more than one contract document exist in the Master Agreement.
For the previous contract documents, not able to attach final signed document (i.e) the upload field is invisible.This scenario is occuring only in few master agreements, mostly found in Legacy agreement types.But for newly created legacy agreements this scenario is not occuring.Please help me in finding out why the upload field is visible only for the last/latest and not for the previous ones.

Hi Dinesh,
Did you find a solution to this?
Regards,
NR

Error when trying to sign documents

I started getting the following message when trying to sign documents:The Windows Cryptographic Service Provider reported an error: Key not valid for use in specified state. Error Code 2148073403 . Any help would be appreciated Thank you

ahh, here is a problem. u made changes to the JDBC_SQL.java and packed the jar file. u have to sign the jar file again.
let me know if u need futher assistance

Update 9.1.2 breaks digital signing documents in Adobe 9 Pro on Windows XP

I am able to digitally sign documents using an Aladdin eToken Pro 64k with a fresh copy of Adobe 9 Pro for Windows. However when I update to version 9.1.2 digital signing fails with an "error encountered while BER decoding". Signing still works on Vista and Adobe 9.1.2 Pro. I've checked to make sure none of the settings relating to digital signing changed during the update and none have. Anyone have any ideas on how to correct the problem?

Hi Nick,
First up, there was a small error in my previous post. I said the version of Acrobat (and whenever I say Acrobat I really mean both Acrobat and Reader, but I'm too lazy to type both) that was modified to fix the bug in SHA-1 fallback was 9.1.3, but I really meant 9.3. Sorry about that.
I saw your post from yesterday (http://forums.adobe.com/thread/563601) where you broached the BER decoding error, but in the post above you said signature creation isn't failing any more, so hopefully some update has fixed the problem.
Here's a little bit about the BER Decoding error. During the signing process Acrobat writes the entire file to disk (which is why you always get the Save As dialog as part of the signing process) in the signed state with everything but the actual signature. However, it does leave a hole in the file where the BER encoded cryptographic data will reside once it's be computed and formatted. One thing that is created before the actual signature is the signature appearance. The signature appearance in the form field isn't really the signature proper, but just a graphic representation of the actual signature. The reason that the signature appearance is written to disk before the signature is created is because it too is part of the signed data and must exist before the actual signature is created.
In a perfect world, after the file is written to disk, the cryptographic signature is created and written into the hole in the PDF file, and the signing process completes without any problem. However, if we get to the point that the file has been written out, but during the actual signature creation the process fails, that hole I mentioned isn't filled in. It's not really a hole per se, but a block of zeros that act as a placeholder for the BER encoded data. Because there was some sort of failure and Acrobat didn't get the signed data back from the hardware device what you end up with is a PDF file with a signature appearance, but no real signature in the file. When you click on the signature field Acrobat tries to validate the actual signature, it finds the block of zeros where the signed data was supposed to be, it tries to decode the zeros and gets (as you might well imagine) nothing back and displays the BER Decoding error.
Let leaves us with why didn't Acrobat get the signed data back. When using hardware devices, such as tokens or smart cards, the actual cryptographic signing (the encryption of of the digest with the users private key) takes place on the device. Acrobat (nor any other application) doesn't have access to the private key, which is what makes hardware devices more secure. It's up to the device to sign the data and send it back. If there is any kind of breakdown in that communication channel (which I mentioned in my previous post) the signature creation doesn't reach fruition and you're left with an unsigned file that looks like it was signed because there is a signature appearance.
This is a case where we are providing technically correct, and utterly useless information. It's true that we can't decode a bunch of zeros, but what we should be telling the user is there is no signature (it's kind of like the Matrix where there is no spoon ).
I hope this helps explain what you're seeing. If the the signing process breaks down again please make sure you are using the latest version of Acrobat/Reader and the token software is up-to-date. If everything is current and the problem returns please let me know.
Steve

Password protecting digitally signed documents in Adobe Acrobat X Pro

I am looking for the combination of steps to get my digitally signed documents to be password protected for secure distribution. My documents contain new "user password" information and a number of "areas" which require digital signatures to be added.
Any input as to how one would construct a document with :
one to three --> digitally signed signatures fields in one document
Password "opening" protection for the document containing the fields; both signatures and sensitive data fields
suggestions on how to make the document open to accepting more signatures without it demanding the creation of a newly saved document after being digitally signed by one signature
I have worked at this a couple of different ways but am having problems finding the right combination/sequence of steps to make it all come together.
Please assist.....
Thanks....

......meaning.......
I can't do locking of the printing or editing of the sheet after i have encrypted and signed it. Trying to do so, wipes out out signatures. Yes, it is a great fullproof to have people be unable to change something someone has signed but if there is an ammendment, can't the creator reserve that right and in an automated sense notify the signers of the rights of the author ?
Maybe I am looking for too much but, it would be great to know if that is the reality of the whole event.
Thanks,
Robert

Acrobat X crashes every time when I open a signed document.

I'm running Acrobat 10.1.13.16.
Acrobat receives a Visual C++ run time error when opening signed documents. I can open standard PDF files without errors.
Microsoft Visual C++ Runtime Library
Runtime Error!
Program: C:\Program Files\Adobe\Acrobat 10.0\Acrobat\Acrobat.exe
This application has requested the Runtime to terminate it in an unusual way.
It's always on MVC90.DLL. I removed it from one installation and installed other Visual C++, but that didn't make any difference.
I've also tried re-installing Acrobat, Visual C++ 2008 Redistributable - x86 9.0.30729 and 9.0.30729.6161.
Here is a sysInfo collected from Acrobat.
Available Physical Memory: 1828380 KB
Available Virtual Memory: 1900892 KB
BIOS Version: DELL   - 1072009
Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
    Version: 11.00.9600.16428 (winblue_gdr.131013-1700)
    Creation Date: 2014/11/12
    Creation Time: 8:12:26 AM
Default Mail: Microsoft Outlook
    mapi32.dll
    Version: 1.0.2536.0 (win7_rtm.090713-1255)
Graphics Card: Intel(R) HD Graphics 4000
    Version: 8.15.10.2639
    Check: Not Supported
Installed Acrobat: C:\Program Files\Adobe\Acrobat 10.0\Acrobat\Acrobat.exe
    Version: 10.1.13.16
    Creation Date: 2014/12/03
    Creation Time: 12:06:36 PM
Locale: English (United States)
Monitor:
    Name: Intel(R) HD Graphics 4000
    Resolution: 1366 x 768 x 60
    Bits per pixel: 32
OS Manufacturer: Microsoft Corporation
OS Name: Microsoft Windows Vista
OS Version: 6.1.7601 Service Pack 1
Page File Space: 4194303 KB
Processor: x86 Family 6 Model 58 Stepping 9 GenuineIntel ~2492 Mhz
System Name: LBE28
Temporary Directory: C:\Users\USERFOLDER\AppData\Local\Temp\
Time Zone: Central Standard Time
Total Physical Memory: 3576436 KB
Total Virtual Memory: 2097024 KB
User Name: USER
Windows Directory: C:\Windows
Installed plug-ins:
C:\Program Files\Adobe\Acrobat 10.0\Acrobat\plug_ins\Annots.api
    Version: 10.1.13.16
    Creation Date: 2014/12/03
    Creation Time: 12:07:12 PM
C:\Program Files\Adobe\Acrobat 10.0\Acrobat\plug_ins\CDSearch.api
    Version: 0, 1, 0, 9
    Creation Date: 2012/10/19
    Creation Time: 2:57:46 PM
C:\Program Files\Adobe\Acrobat 10.0\Acrobat\plug_ins\EScript.api
    Version: 10.1.13.16
    Creation Date: 2014/12/03
    Creation Time: 12:07:12 PM

Hi Luke,
You might want to check the steps mentioned in the KB: https://helpx.adobe.com/acrobat/kb/runtime-error-roaming-profile-workflows.html
Regards,
Rave

The "sign document" function is not working in Adobe Acrobat X 10.1.8?

I had an issue with Adobe Acrobat erroring with an error message relative to the Crypto file in Windows. I attempted to do the file folder renamaing to 'old', etc. to no avail. When I tried to restore everything to it's original state, the sign document window appears (see below), but when I click on the sign document buttone, nothing happens at all. I have tried this in multiple documents, through multiple siging routes, and all the same non-result. I have also reinstalled Acrobat to no avail; advice?

This is the Reader forum; the Acrobat one is here:
http://forums.adobe.com/community/acrobat

Plug_in:how to unlock a locked document use acrobat API

how to unlock a locked document use acrobat API.in acrobat plug_in

how to unlock a locked document use acrobat API.in acrobat plug_in(Which API can enter a password to unlock the locked document)

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

Hello!
I have developed a service that appends additional pages to existing PDF documents. Some of the documents the service works on happen to be signed. As the service appends the pages using incremental updates, the signed contents are left untouched. This makes Acrobat 8 and Reader 8 display the signature state as "valid with subsequent changes" which is ok and no one complains about.
Now along come Acrobat 9 and Reader 9, and all of a sudden the signature state is "invalid" which my users do complain about. Telling them that inspecting the signature state details they can see that the signed content still is untouched and the actual change is recognized to be some appended pages, doesn't help either as they in turn forward the documents to their customers who don't accept the documents if the Adobe Reader sais the signatures are invalid.
Does anyone know a way new pages can be added to a signed document without having the new Adobe program versions choke on them?
Even a hint that involves adding some flag to the original unsigned document or the signature itself would help as the users in question can tweak those processes. Due to the nature of the workflow, though, signing unfortunately must happen before my service can add the new pages.
Best regards, Mikel.
By the way, the signatures in question are regular approval signatures, nothing fancy, especially not certifying signatures (which indeed can forbid any changes or at least any changes but some form fill-ins and annotations)...

Hi Fritz,
In the interest of full disclosure, I got the answer to the problem from one of my distinguished colleagues, I'm just the messenger in this case.
The problem is that the form adds some items to the Arzneispezialität / Zusatztext combobox which are there during signing but the form doesn’t remember that it did this on the next form open.
Since this field is included in the MDP+ signature and the field has changed in the re-opened version vs. the signed version, the MDP+ signature becomes invalid.
XFA has a feature that remembers these kinds of things for you but it is turned it OFF. Please open the attached screen shot to see the control in question.
So, you can either (1) turn this feature ON (Automatically), or (2) write some script to clear the combobox items prior to signing or (3) write some script to repopulate the combobox items on the subsequent open to match the items that were there during signing.
Steve

Opening signed documents crashes Acrobat 9.4.4.

This issue happens with Actobat 9.4.3 and 9.4.4:
With one or more PDF files already open (could be a published document simply open for review), open a document that includes a digital signature.
The file with the digital signiture opens, but then so does a Data Execution Prevention dialog box like this:
Then, another message box overlays that indicating their condolences:
This happens when opening any signed document, as long as there is any other document already open (digitally signed or not). It is very annoying.
The OS is Windows XP Pro SP3.
Please let me know if you have any ideas. Thanks.
Jon

Fix the [http://browser.iyogi.com/firefox/firefox-not-opening-pdf.html '''PDF not opening in Mozilla Firefox'''] issue by reinstalling Adobe Reader. You need to uninstall Adobe Reader and re-install it to get the issue fixed. It is important to uninstall all versions of Adobe Reader that you may have in your system. Also, take care of installing the latest Adobe Reader for the browser.

How do I edit and sign documents using adobe?

How do I edit and sign documents using adobe?

To edit a document you will need Acrobat Pro.

Unlocking a signed document

Similar Messages

Maybe you are looking for