Signature Validation Reverts to "Unknown" after Signing

I am having an issue with validating the signature on a form I am working on. The form is used to track maintenance and repair on shop equipment, and I'm using the signature to close the form out once it's completely filled in. The problem is that, for some reason, when I run the PDF and digitally sign the form, the signature initially shows as being validated, but then the validation status reverts to "unknown." I've run a temporary script on several of the signature field's events and found that the reversion occurs after the signing sequence is completed. All changes to the form are completed in the signature's preSign event, and no changes are reported in the signature panel--the panel indicates that the signature was never validated, even though it was validated a few fractions of a second earlier, something my script confirmed. What could cause the validation status to change like this?
Thanks for any help!

I've found the solution. I had several "page X of Y" fields in my form and had the signature block set to lock them after signature. Once I excluded those fields from being locked, the problem resolved itself.

Similar Messages

Signature validation unknown

After digital signing a document I get the remark in the top of the screen: "validation of document certification is unknown. the author could not be checked". I asked the company for my signature card and they checked my document with the signature. They told me that there the status of the signature is ok and they can give no assistance for Adobe Acrobat. 4 to 6 weeks before I had no trouble with signing using the same signature card, the same signing procedure of pdf - files with Adobe Acrobat XI, the same pc. I updated the program but I got still the above mentioned remark.
Is there somebody who had the same problem and found a solution?

You most likely do not have the root of your certificate chain trusted. The string "validation of document certification is unknown. the author could not be checked" doe not look familiar. Are you back translating it from another language
1. Check your certificate chain. Open signed PDF, right-click on the signature and select "Show Signature Properties". Then select "Show Signer's Certificate". The left-side panel of the Certificate Viewer dialog that comes up shows the chain with your certificate on the bottom and the root on the top.
2. Select the root certificate and click the "Trust" button on the top of the right panel. If this certificate is marked as not trusted then you can click on the "Add to Trusted Certificates" button to add it to Trusted Certificates. Make sure that you know who this certificate represents so that you do not open your computer to possible malicious attacks. You can check with your IT department if this is the right think to do.
3. Are you using some 3rd-party Acrobat plugin to sign with your smart card? I saw some instances when 3rd-party Acrobat plugins did not embed certificates in the chain into the signature object that they generated. In this case the Certificate Viewer will show only the signing certificate in the certificate chain and nothing else. This case is unlikely, though, as you said that the same signature validates fine on another computer. So, it is most likely that it is the lack of trust on your computer that causes this problem and the problem does not manifest on another computer where this trust is set.
4. You may have gotten the file where Acrobat keeps trusted identities somehow corrupted which started to cause this problem. To check your Trusted Certificates go to Edit->Preferences->Signatures->Identities&Trusted Certificates->More. In the left panel click on Trusted Identities and look up the list of Trusted Identities in the right panel for anything missing (you may need the help from your IT for that), If your root certificate is in Adobe's AATL program you can refresh AATL certificates by going to Edit->Preferences->Trust Manager and in the "Automatic Adobe Approved Trusted Certificates Update" click on the "Update Now" button.

Digital Signatures/Javascript After Signing?

Hello everyone,
I'm currently developing forms for my company, post processed through Adobe Acrobat 9 Standard, that require digital signatures. Working in the food industry requires compliance to specific FDA guidelines, specifically CFR 21 part 11. In order to meet the requirements I must develop an SOP (Standard Operating Procedure) that proves signatures are accurate and secure.
The process is tedious, and I have called a few meetings thus far to discuss some of the unforseen circumstances. During the discussion a question was brought up stating; What protects forms stored in the archives (3 years for compliance) from being corrupted by a disgruntled employee? Specifically, what stops an employee from clearing a digital signature? I realize we can set up file access rights to the forms to prevent such happenings, but majority of the forms are setup to hold 6 months to a year of info, thus wouldn't be archived until filled completely.
My question: Does anyone out there know of a javascript or trick to disable the "Clear Signature" function after signed? I've been searching and have turned up empty handed. Also, does anyone have any other javascripts that are used after digital signature occurs?
Thanks in advance for any help you can give me,

George,
Thanks for your response.
The issue is not if the file is deleted, the issue is if the files becomes "manipulated". I think "corrupted" was the wrong choice of words.
To explain: Any form that is completed has several digital signatures within the contents, depending on which QA Technicians complete the task (e.g. Calibrations, Metal Detector Settings, etc...). Forms are setup by days, weeks, or in some cases years, and have designated signature areas for the time period the test was conducted. So, after "John Smith" completes his portion of the form he is required to digital sign the document, after signing is complete all information is set to read only and cannot be altered unless the signature is deleted.
Digital signatures can be deleted in two ways:
1. The user who signed the document, based on active directory, has the ability to "clear signature". As and FYI: no other user is capable of deleting a signature signed by another employee. (does not apply to the form author)
2. The file creator can add a "Reset button" control, thus being able to delete any data specified.
So as I said I'm looking for a way to lock all signature functions, after sign is completed, even for the original signer. So if form "Calibration01" is currently being filled out and has signatures x,y,and z on it; I want to make sure if "x" is disgruntled they do not maliciously go and clear their signature. Also, I would like all fields associated with the signature to be locked without any way for the user to manipulate or revise data.
If anyone has any javascripts that run once signer digitally signs, it would be a great help,
Thanks,

Locking PDF but only allow further signatures & get the list of of changes made after signing

Hi,
I have looked at Adobe Acrobat 9.0 and found the Signing > locking feature which blocks any changes after the document is signed. I need to know whether using Acrobat SDK, one could implement a similar locking option via plugin in a way that it ONLY allows further blank signature fields to be created or sign existing ones and locks all other changes. If possible, any pointers to API functions would be appreciated.
If the above is not possible using Acrobat SDK 9.0 then can the SDK provides a list of all the set of changes made after the signing is performed (at the time of verification) in the form of some codes which can guide the plugin author about what change after signing was done e.g.
a blank signature field was signed
a blank signature field is created
watermark has been applied
form is filled
sticky notes/stamps/other annotations are added
Regards,
mwak

Thanks for your response. I have just performed this:
I signed a PDF ( having no prior signature or blank signature fields ) using Adobe Acrobat 9.0 and locked it. I am now not able to create more signatures on this PDF. I believe I can't add more signatures even using the Acrobat SDK and Lock means complete lock-down of the document. This is different to what you said " it restricts modifications EXCEPT for other signings" or may be I am not understanding it clearly.
I created two blank signature fields. When I clicked on the first, there is no Lock settings at the time of signing. I believe because If it is locked then the next signature can't be signed. With only a single signature field present, the lock feature is there.
So I believe I have to resort to the option of identifying the changes in a revision and then if it the change is related to say adding stamps, sticky notes prompts the user at the time of verification.
Can some one point me to the API functions set which identify list the objects which have changed after signing.
Regards,
mwak

After signing with e-signature acrobat creates an additional file starting with aa

I open a file and place a signature on the document. After placing the signature, and locking the file on save, it overwrites the existing file fine, however it creates an additional file in the folder and the files start with aa. example: aab03284 (No file extension is attached)

I have also had this issue - and it just randomly started happening, along the same time the request to do EchoSign disappeared (not sure if they are related). I'll save as over top the existing file, and it asks if I want to do that, I hit 'yes' and it then creates a temporary file instead of saving it over the existing. I have to then go back in, 'save as' again, say that I want to do that again, and then it finally saves over it correctly.

How to modify a PDF after signing

Our company has recently been upgrading from Adobe 8 to Adobe X (more specifically 10.1.10.) In Adobe 8 there is an ability to add/subtract pages after a signature has been signed, however this does not work in Adobe X with the default settings and I have not located a way to adjust this. Within the company there is a department in legal/accounting that handles the creation of PDF documents from basically start to finish. During their creation process there needs to be two signature: one for the creator of the document (this field is important enough that I cannot simply copy an ID/key so that anyone can sign anyone’s name however it is not important enough that it needs to lock a document or prevent any changes including adding/subtracting pages.) The creator will start a document sign and then pass it on where it will be modified, pages will be added/subtracted and words may be rearranged. Once it has been revised a couple to even a few time a second signature will lock the document. Is this still possible in Adobe Acrobat X Pro or Standard? Thank you in advance.

AFAIK the signature validation rules were significantly strengthen in Acrobat 9 and later. I do not remember whether adding pages was among those. BTW, by "subtracting pages"do you mean "deleting pages"? You could never delete a page in a signed document without invalidating the signature. Generally, in order to be able to modify signed PDF the original PDF, before the first signature, needs to be certified with certification permissions for specific actions, like permission to add more signature and fill form fields. You can certify the original PDF in Acrobat and its UI gives you a few certification permissions options. Adding pages is not in this list. LiveCycle has a more elaborate set of certification permissions but this is a fairly expensive solution and I do not remember whether Adding pages is in its permissions list.

Digital Signature validation

I have been using digital certificates to sign pdf documents for approximately a year. The signatures can be checked against a CRL which is provided on the internet. So far Adobe Acrobat Reader has worked fine, retreiving CRLS and validating certificates.
Today I found out that since renewing expired certificates ( the default lifetime was set to 1 year) the signatures on old signed documents are unverified . The local time of the computer was stored in the signature not a timestamp.
I found that reader defaults to using the local time of the computer to validate an old signature when a timestamp is not used, this has been rectified in 9.1 so that it uses to date that the signature was generated (why on earth would it use anything else!). I now have the signatures validated by changing this setting providing the date range of the CRL in the reader encompases the end date of the certificate.
However, when the reader updates the CRL in the cache and the new CRL date range does not include that of the original signature the reader throws up an error stating that the CRL is invalid or expired.
How can I get it to agree pass the validation without turning off revocation checking? I have the CRLs that were in force at the time of the signing but there is no way I can provide them to the reader. How can I make the reader apply the current and valid CRL to the old documents. The expiry date of the old certificates are still in there?
I always thought that not having to keep a CRL history for expired certificates was a dumb idea when I read the documents, but I didn't imagine that old signatures would become invalid when the certificate expired (mine have become invalid less thant 5 days after the documents were signed. What were the developers thinking.
This is pushing toward creating certificates with lifetimes of 100's or thousands of years so that they can always be validated.
Anybody have a working solution.

I have found a solution.to this
Using a virtual machine I set the date on the system back to a point in time when the certificates were all valid. I then create a new crl with a lifetime which makes it valid for one month from the real date (today). I then set the date back and copy the crl to the distrubution point.
Hey presto, acrobat reader loads the crl and is quite happy to accept it even though it has events recorded in it that happened after the date on which it was created!.
Problem solved, but for how long?

Bug with Overall Signature Validity Icon

I am finding that there are inconsistencies in the way Adobe Acrobat 9.0.0 and Adobe Reader 9.0.0 indicate Overall Signature Validity states for digitally signed documents. Adobe's white paper on this issue at http://www.adobe.com/devnet/reader/articles/reader_compatibility/readercomp_digitalsignat ures.pdf clearly states when/how both these applications should indicate "Unsigned changes since last valid signature", being the icon of a signature with triangle containing an exclamation mark.
I performed the following steps:
1. Open a document already containing blank digital signature fields and Extended Features / Reader Rights enabled, in Adobe Reader.
2. Sign and save the document.
3. In the signatures panel, select "Validate All".
4. The overall signature validity icon of a signature and tick (indicating all is valid) is displayed, as expected.
5. Open the "Comment and Markup" toolbar, and place either a "sticky note" or "stamp" in the document.
6. In the signatures panel, select "Validate All".
7. The overall signature validity icon of a signature with yellow triangle symbol with exclamation mark (meaning unsigned changes since last signature) is displayed, as expected.
However, if at step 5 above I place any of the OTHER options (Text Edit, Text Highlight, Callout, Text Box, Cloud, Arrow, Line or Rectangle), and again "validate all", the overall signature validity icon still shows a signature and tick (i.e. it has not recognised the changes). In such cases, the "Annotations Created" entry also does not appear under the signed revision in the signatures panel.
8. Furthermore, if I sign the document again after adding any of the "Comment and Markup" options, and then "Validate All", the overall signature validity icon of a signature with tick and blue 'i' symbol (meaning all is valid but document was updated since initial signature) is displayed, as expected.
9. Then add ANY of the "Comment and Markup" options, and then "Validate All", and the overall signature validity icon of a signature with tick and blue 'i' symbol is STILL displayed. At this point I would expect the signature with yellow triangle symbol with exclamation mark to be displayed. Again in this case the "Annotations Created" entry also does not appear under the last signed revision in the signatures panel.
Can anyone else repeat this behaviour? It appears to be the same in Adobe Acrobat and Adobe Reader. Am I missing something or is it a bug?
Thanks,
David.
Canberra, Australia.

Philip,
The PDF file I was testing with originated from a Word document, created by Acrobat Professional v9.0.0. The document was created using the 'Convert to Adobe PDF' option that is embedded within the Word menus when Acrobat Professional was installed. From there I added the digital signature fields, text fields, check box etc, then 'Extended Features in Adobe Reader', and saved the document (replacing the original file) as prompted when extending the features to Adobe Reader. I don't have the LiveCycle Designer application.
The bug I am experiencing is not effected by saving or not saving. Today I started with the document created some time ago that I describe above. It contains several blank signature fields, no certification, a blank text field and a check box, and extended features in Adobe Reader were enabled. Today I opened that document, signed the first signature field and saved as a different file name when prompted. I then added a 'text box' annotation. I then selected validate all from the signature panel, and no changes are listed under Rev 1, just the remaining unsigned signature fields are listed. The overall signature validity icon shows a signature and tick. I then saved the document, and again selected validate all. No change to either rev status or icon. I then closed Acrobat Pro and reopened the document, and selected validate all. Still no change to rev status or icon. I then checked the check box field in the document, and selected validate all. The icon now shows signature with triangle containing exclamation mark, with comments regarding unsigned changes since last signature etc. There are also two entries under Rev 1 in the signature panel, the first labelled 'Annotations' which describes the text box, and the second labelled 'Form Fields Filled In' which describes the checking of the check box. In my mind, the 'Annotation' entry should have showed up (along with an icon change to show unsigned changes since last signature) when I selected validate all after adding the text box originally.
I am happy to email the document to you if you're able to provide an address.
Regards,
David.

How to edit my document after signing?

how to edit my document after signing?

Hi fortm71591551,
Follow the below procedure for editing your document after signing it:
1. Open the File in Acrobat
2. Right Click on the signature field and choose 'Clear Signature'
3. Go to tools pane on the right side of the window then choose 'Edit' Under Forms Drop Down Menu.
4. Right Click on the signature field and choose delete.
5. Click 'Close Form editing' and then you can make necessary changes and resign your pdf (If you want to).
Hope that helps.
Please revert back for any other query or if you need any further assistance.
Regards,
Rahul

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

Make all text fields read only after signing form

Hello,
I have a live cycle form which needs to have all of the text fields set as read only after signing.
The java script has been placed in the post sign event of a digital signature field.
for(var i=0;i<this.numFields;i++) {
var cNm = this.getNthFieldName(i);
if (cNm.type = "text") this.getField(cNm).readonly = true;
After signing the form the following console error is shown:
this.getNthFieldName is not a function
Can anyone please advise how to revise the script so that when the form is signed all of the text fields become ready only?
Any assistance will be most appreciated.
Thank you.

You don't need any JavaScript to do this.
In Designer you can setup the signature field in that way, that all fields will be locked after signing.
Look here:
http://forums.adobe.com/message/3121870?tstart=2

"Lock document after signing" option is missing

Hello,
I need a signature field on a PDF form I am developing to have the Lock Document After signing functionality. My coworker (who has since left the firm) designed a similar form that automatically checks this box in the Sign Document pop-up window. This is exactly what I want, but I can't figure out how to do it. I am using Adobe Acrobat X Pro (10.1.13).
What I CURRENTLY see, missing the lock document option:
What I WANT to see, taken from another PDF form:
Thanks in advance for any help

Thanks for the reply isakten.
I am the author of the document for the 1st screenshot. I am trying to replicate what my former co-worker did in the 2nd screenshot (which is a completely separate document). My boss likes the "lock document" feature and wants each form locked when it is signed.
I've heard about seed values, but i don't know anything about them specifically. The properties of the digital signature field are the same in the two documents, there is no script in either one, yet the difference remains. Do you have any resources I could read about for modifying seed values to mandate the lock document option?

Certificate signature validation failed

Hi!
I'm getting nuts over how to get Acitve Directory to work with java.
I have a root-certificate for the domain (supposed to work for everything according to our networking expert) but when using it I get: "Certificate signature validation failed".
When looking in C:\ on the ADS I find another certificate but then my javaprogram says: "No trusted certificate found".
So, now after much searching where I seems to find everything but what I'm looking for I have to ask: What should I be looking for? Hopefully when looking for the right thing I will find the answers. :-)
Thanks you very much in advance
Roland Carlsson

Please! Anyone? How can I get a correct certificate from our ADS? The certificate-server on is on our Exchange-server. I have a certificate that is supposed to work all over the domain and I have check several other certificate that I found on our servers but I still havn't found anything that works.
I'd would really like to get some ideas about where how to find the working one.
Thanks in advance
Roland

PDF Doc is Corrupted after Signing

The document is fine until I sign it and publish to Web. Local files are not affected by this. All Calibri fonts were removed since that caused the previous error. Calibri fonts were ok for the past six months. Now Calibri will not publish correctly as embedded font.
I've removed all known Calibri font from this file.
Error is produced only after signing document.
Is it likely that Calibri font is embedded in signature? If so, how can I remove the font from signature?
Regards,
Sticky3D
Working file:
http://essn.us/ssolesbee.pdf
Damaged file: (with signature)
http://essn.us/ss.pdf

I'm uploading both files the same way with FTP Client. It is odd that adding a signature has never done this previously. The error began concerning Calibri font even before signing the document. After tinkering with the document, getting rid of the error by removing the Calibri font, I signed the document just to see if it returned. Now I'm getting an encrypted conglomeration with the http://essn.us/ss.pdf although the other file is not signed. It works fine.
Sharon Solesbee
828.524.6313
www.ITsaBS.com

Signature Validation Failed

Hi,
While performing cross domain SSO using SAML2.0 between the Oracel Identity Federation(IdP) and Novell Access Manager(SP). The connection between the both is in open mode and havent enabled SSO between the two. In the Idp end and the SP end, metadata of the other end is imported successfully.
Artifact is send from the Idp to the SP and simillarly SP sends the ArtifactResolve SAML message to the Idp. From the Idp end, the ArtifactResponse Message is also send to the SP end.
When the SP receive the Assertion in ArifactResponse message, "Signature Validation Failed" message is thrown by the SP side. Customer is signing the assertion in the Idp side. Also the signing certificate of the Idp is place in the trusted certificate store of the SP side. Also, there isnt any error message in the idp side.
Any help on this would be appreciated.
Thanks in advance,
Anisha

Please! Anyone? How can I get a correct certificate from our ADS? The certificate-server on is on our Exchange-server. I have a certificate that is supposed to work all over the domain and I have check several other certificate that I found on our servers but I still havn't found anything that works.
I'd would really like to get some ideas about where how to find the working one.
Thanks in advance
Roland

Signature Validation Reverts to "Unknown" after Signing

Similar Messages

Maybe you are looking for