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,

Similar Messages

Trigger a Signature Date when Digital Signature Field is Signed

I'm looking for a way to have a date field populate when a digital signature field is signed on my Adobe Designer Form. The signature technology I'm using does not work seamlessly with Adobe LiveCycle Designer and is unable to add the date when the document is signed. So I was thinking I could call a function to add the date to the date field when the signature field is signed. I just dont know how to do it.
Please help!
Thanks!

Here is some code that will allow you to check the signature field:
// check to see if Claimant signature field is signed.
var oSOM = claimsign.somExpression; // Returns the full SOM expression i.e. xfa[0].form[0].form1[0]...
var truncSOM = oSOM.substring(15); // Truncating 'xfa[0].form[0]' from SOM to get acroforms name of the field.
var oState = event.target.getField(truncSOM).signatureValidate(); // Get the current field's signed state
In this case the signature field is called claimsign. After running this code the variable oState will conatin a value ....if it is 0 then the field is not signed. So you can add code like this:
if (oState == 0 ) {
     // signature field is not signed
     app.alert("You must sign the form before submitting")
} else {
     //The signature field is signed
     go through your submission process code
Hope that helps
Paul

Digital Signature invalid when sign a PDF with instances

Hi,
I created a XDP document with LiveCycle Designer ES2.
This document contains:
- Some required fields (text fields, data fields ecc...)
- A Subform that user can add more instance pressing a button, contains some fields
- A Digital Signature (With a simple fields collection contains only the signature field)
I render the XDP for get a PDF (using ReaderExtensions component) by LiveCycle Workbench ES3.
Then I open the PDF with Adobe Reader X.
I compile the form and don't press on button increase the instances of Subform.
Sign the document and the signature is valid.
Now, instead, if I make the same but increase the instance of Subform, then sign, the signature is invalid...
Can the problem is the different versions of Designer and Workbench?
In past I got some problems, and sometime I resolved creating a new document and copying all the object of old form in new one... It's an ugly solution but it worked.
But in this case don't resolve nothing.
Any help?
Thank You!

Hi,
I created a XDP document with LiveCycle Designer ES2.
This document contains:
- Some required fields (text fields, data fields ecc...)
- A Subform that user can add more instance pressing a button, contains some fields
- A Digital Signature (With a simple fields collection contains only the signature field)
I render the XDP for get a PDF (using ReaderExtensions component) by LiveCycle Workbench ES3.
Then I open the PDF with Adobe Reader X.
I compile the form and don't press on button increase the instances of Subform.
Sign the document and the signature is valid.
Now, instead, if I make the same but increase the instance of Subform, then sign, the signature is invalid...
Can the problem is the different versions of Designer and Workbench?
In past I got some problems, and sometime I resolved creating a new document and copying all the object of old form in new one... It's an ugly solution but it worked.
But in this case don't resolve nothing.
Any help?
Thank You!

Digital Signature update after new documents created on customizing

Hello,
Is there any standard report to update old document with signature after new changes on SIPT_NUMBR_SD_V which added new document types?
I mean, if we move to live system today 2 new number ranges for billing types, the new invoices created will be on digital signature, but what about the old document created before the transpor of customizing?
Regards,

Hi dude,
I appreciate that your sharing your experience and solution here. And, I would report it through our internal channel. Thanks again.
Tony Chen
TechNet Community Support

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

Signature error after signing into securedoc

i tried to restore my thinkpad t61 to the way i received when i bought it using the thinkvantage tool. after the computer rebooted and i got past securedoc I receive a message that reads, "There has been a signature failure." Is there any way to get my computer up and running again? i'm not tech savvy but i have a hunch that the securedoc software is the problem. my other hunch is that i have to install a new harddrive and operating system.

Maybe the "Remote XUL Manager" add-on mentioned in these threads will help?
[http://support.mozilla.com/en-US/questions/798338 Since I upgraded to Firefox 4, my Lotus Domino Web access program is not working and I can't load emails. | Firefox Support Forum | Firefox Help]
[https://support.mozilla.com/en-US/questions/814413 The Webmail version of Lotus knows keep giving the following error message: A problem has occurred which may have caused the current operation to fail. How do I fix this? | Firefox Support Forum | Firefox Help]

Digital signature: How to sign a file ( algorithm SHA1withRSA )

Hi
I need create and sign a File. I need some example how to do that.
I Found this functions:
ssfSign ( to sign )
ssfEnvelop ( to encrypt )
Thanks a lot!
Mariano

check program SSF01
regards
Prabhu

Using iText to generate a digital signature that can be signed in Adobe Reader

I am able to create a digital signature in a pdf using iText. Adobe Reader does not allow that digital signature to be signed. Everything I have been reading suggests that I need to enabe Reader Usage Rights, but that requires using Adobe Pro. I was hoping that I would only need Adobe Reader inorder to digitally sign the pdf, is that possible?

Not without the required rights...

Script to detect when a radio button is clicked/ digital signature signed

Good afternoon,
What is the syntax to detect if a radio button is clicked or a digital signature field is signed?
What I want to do is populate a field if a radiobox is clicked and a the user digitially signs the form.
My radio boxes follow the scheme
Group name: Group 1
Choice name: A,B, C, D
Digital signater field name: boss
Proposed script
if ( group1.A==True and this.getField("boss').signed){
     this.getField("x").value = thisgetField("y").value
I know the syntax is way off but I am trying to fufil a task like thie one described above.

Try67
Thanks
That works. Follow on question:
When I digitally sign, I am trying to get that digital signature to permeate to other digital signature blocks. I am trying to modify your code to do this once the document is digitally signed but it is giving me a syntax error:
if ( this.getField("MainCheckbox").value=="Choice1" && this.getField("Signature155").value!="" {
     this.getField("Signature15").value! = this.getField("Signature155").value!;
    }else this.GetField("Signature15").value = "";
How to I fix that?
Also, I am trying to d othe same with radio boxes; however, radio boxes do not have an option to run a script once they are checked.

Digital signatures and combining PDFs in Acrobat X

I hope that one of you Acrobat gurus can help me out with one or more of these questions:
Is it possible to maintain digital signatures when inserting signed PDFs into another PDF?
Is it possible to remove a digital signature after a signature has been deleted from the page?
Is it possible to change the format of the date and time on a digital signature?

In the simplest sense a digital signature is a special checksum of all the bytes in the bytes in the PDF combined with all the bytes in the digital signature. If the document is changed in any way the checksum changes, so the signature becomes invalid. A valid signature ensures that the document hasn't changed since the signature was applied. That stuff that's shown on the signature field is irrelevant. It's just a pretty picture. The real stuff is going on inside the PDF where you can't see it.
Obviously it gets a lot more complext then this. The signature can be selectively applied so that the certain types of changes are allowed. A signature does not add real protection to a PDF, but Acrobat plays along with this scheme by trying to not allow changes that would invalidate the signature, and logging all modifications to the PDF.
1) There are ways to maintain the visual appearance of the signature on the page. If the permissions have been set to allow it the PDF can be flattened, which also partially removes much of the stuff that's going on internally. But this isn't always possible. I had to solve this problem once for a client, so I wrote a plug-in that strips the signature permissions from the PDF (I'll post this to www.pdfscripting.com sometime soon), after which the the PDF can be flattened, keeping the appearance. But of course, after this point the document has to be considered invalid. For example, if the document was a contract, the flattened version would be good for use in an analysis of say all contracts for a particular year, or for copying legal language to another contract, but it couldn't be used as the basis of a legal dispute.
2) I don't understand this one. Do you mean you're deleting the signature field and some of the internal digital signature stuff is still hanging around causing problems? If you own the signature (or the permissions allow), then a standard form reset will "Un-Sign" the PDF. Inserting PDF pages into another PDF will strip out all this info as well.
3) The stamp appearance is set at the time the stamp is applied, it cannot be changed after this point. It's a lot like a PDF stamp.
Thom Parker
The source for PDF Scripting Info
pdfscripting.com
The Acrobat JavaScript Reference, Use it Early and Often
http://www.adobe.com/devnet/acrobat/javascript.html
Then most important JavaScript Development tool in Acrobat
The Console Window (Video tutorial)
The Console Window(article)

Digital Signatures- either disable reader abilities or any other work around

I am fairly new to acrobat
I have designed a form that uses a JavaScript that looks at individual fields to verify if the information is good. I also require two signatures along with these correctly entered fields before I consider the form "good to go"
(If the form is missing something, my form validation JavaScript will population the value of a text box with the list of which fields are bad. The warning goes away when everything is good)
I can’t find the correct property in JavaScript that reference if the digital signature field is signed or not, so I put in the signed event JavaScript that locks the field when signed.
In my form validation script, I check to see if that digital signature field is locked- if so- then they must have signed it.
Here is where I am running into trouble:
After rights are extended to reader (my users will use reader to fill out this pdf)
It’s possible for the user to sign it, (locking the field) and then clear the digital signature (but the locked field tells my validation script its “okay”)
Locking the field does not stop someone from clearing it, which is not good.
Also, someone using reader can add a digital signature on top of where I want them to sign it- and my validation script doesn’t know about this, so it won’t remove the warning if they add their own signature.
How do I:
((Find the javascript property to know if a particular digital signature field is signed.)
OR
(Find a way to not allow the user to clear their signed signature))
AND
(Stop the user from adding their own digital signature field to the form?)
Thank you.

One last try.
You help would really be welcome in finding out the root cause of the difference in behaviour between reader 8 and 9 in this matter (bug or change).
I have no idea what documentation to read (since i've read the launch documentation and change list documentation) about reader 9, i've contacted Adobe 3 days ago (and the answer is silence, like usuall) and have no clear thought about what to say (without taking a huge risk by giving a uninformed answer) about this issue.
Thanks.

Digital Signature Field == null

I created a button that will only execute if the digital signature field has been signed. However even when the signature field is signed use of the button after the signature still pops up with the scripted message "This document has not been signed yet.".
I have the button excluded from locking after signature.
Here is how I wrote the checking script.
//checks if form has been signed
if (form1.Page1.SignatureData.CASignature.rawValue == null)
                 xfa.host.messageBox("This document has not been signed yet.");
else
{ /// some code that excutes fine without the if statement above}
Any ideas on what I could do to check if this digital signature field is signed? Thanks.

George,
I can't get the first line to fire in LiveCycle Designer ES 2.0
I created a new file with only three items. 1. Text field named "signedFlag" made "User Entered - Required" in the Object + Value tab.
2. A signature field named "SignatureField1" that doesn't lock anything after signature. 3. A button with the script:
form1.Button1::click - (JavaScript, client)
var oState = event.target.getField("form1.SignatureField1").signatureValidate();
if (oState != 0)
{      signedFlag.mandatory = "disabled";
xfa.host.messageBox("Congratulations your button worked.","Winner! Winner! Chicken Dinner!",3,2);
else
{      signedFlag.mandatory = "error";
       xfa.host.messageBox("This required box in red above is not completed.","Warning",3,2);
I created the xfa.host.messageBox for either case being succesful, "disabled" or "error" so I could see if the script was firing after signing the document and then clicking the button. With or without these messageBoxes the var oState doesn't seem to be working. Any ideas?
I changed the names in my scirpinting so I know, names are not the problem as you mentioned previously. Thank you for your time.

Want insertion of Digital Signature not to require a save

I have an issue that I would appreciate someone's help on. I have been with Adobe Tech Support via their portal. Yet I have not been able to establish whether what I want to accomplish is doable.
What I have is a document that actually consists of several documents, which in aggregate comprises our application for persons wanting to drive for us. For the sake of this scenario please understand that the document is not to be broken up into multiple files. It is created as a single document to facilitate the management of the numerous applicants by in-house staff.
Anyway - this form has multiple digital signatures. The department head insists on this as each section of this document has information to be attested to as original and accurate. However, we find that only the first digital signature is used to certify the document, and any additional serve only in a "confirming" capacity.
So we have this document with multiple digital signatures, the first of which certifies the document and the remaining as "confirmation". And all of these digital signature fields are set as "required" in their properties. The form is developed and presented for testing. So we enter just one of the several digital signatures and attempt to save the file. What we expected to happen was the pop-up of a dialogue to point out that all of the required digital signature fields were not completed. But no such warning arises, and this circumstance "raises an eyebrow" or two within the firm, who expect this edit to appear.
Based on recommendations from Adobe support I go out to the developers site and research scripting. After several hours I come away with a script that will indeed spawn a message when any digital signature is missing. However, another problem arises. After closing out the dialogue box and inserting the first of several missing digital signatures I am immediately required to save the file. The save works and here we have the form with several digital signatures still not signed. This allows the user to forward on the form to us, at which time the file will be reviewed and returned to the user for further completion. And in the event that only one of several missing signatures is entered, and the file again saved and forwarded, this scenario has the potential of being repeated several times.
Is there any way through scripting for the insertion of the digital signature not to spawn a save of the document? Thanks!

Is there any isight as to how this is done?
I am currently opening a file from Teamcenter engineering, however if I try to save the file it complains there is another copy open elsewhere (which isn't true). I have to export the file first, save it and then check it back in. It seems to be the only area that behaves like this, as I am able to markup the document add pages,etc and save the document just fine.
If I could remove the save as function and just use "Save" I think that this would help.
Appreciate any/all replies!
Regards,
Sean.

Digital Signature Validation process goes into unending state

Hi all
I am working Adobe Digital Signatures in Web Dynpro Java applications. I have been using [this|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/com.sap.km.cm.docs/media/streamingmedia/developer-areas/user-interface-technology/interactive-forms/securing%20online%20interactive%20forms%20by%20adobe%20(Session%208)/index.html?slide=] webinar to follow steps to configure SSL and validation of Digital Signatures.
After doing all necessary configurations, I am able to run my web dynpro applications containing interactive forms in secure mode.
But when I sign with digital signature and try to validate the form, the application keeps on processing and shows no result.
I tried debugging my application but control does not reach my button action code. I am clueless.
I would be thankful to receive any hints or pointers from you.
Thanks in advance.
Kapil

Following blog discusses solution to this prob
/people/kapil.kamble/blog/2009/07/08/experimenting-with-digital-signatures-in-sap-interactive-forms-by-adobe
Kapil

DMS & Workflow - Handling Digital Signatures

Hello,
I have set up a DMS status network, and I'm controlling this network using workflow.
My workflow listens to "DRAW" for changes, and when a particular status is seen,
workflow starts.
This workflow sends out work items to several users, prompting them to review.
At this point, users can go into the DIR from their Inbox, and either select Approve or Reject Status.
Both Approve and Reject status are set up to require a Digital Signature. Workflow controls moving the status back to a "ready" state for the next reviewer. It also keeps track of the number of reviewers, in order to know when all reviews are done.
When everyone behaves in timely manner, this works great. Workflow has no issue with setting DMS statuses - in most cases.
However, I also have deadline monitoring set up on my workflow. After 3 days pass with no action, I want to "auto-reject". System id WF-BATCH is what I use to set statuses through workflow, and this works fine in most cases. However since the status "Approve" and "Reject" are set to require digital signatures, this system initiated status change FAILS. The system does not provide a digital signature for itself.
My question is - is this possible through configuration - to set it up in some way that a system ID can promote to a status and either pass a password or simply not require a digital signature?
My network is kind of stuck at this point because one of the 2 statuses MUST be selected for it to proceed.
Edited by: Bill Bessette on Jul 24, 2008 9:40 PM

Hello Niranjan,
That's an interesting suggestion... I'll investigate. Any additional detail you can provide on how to implement this User/Pwd hard coding in WF would be appreciated.
In the meantime, here is some additional info.
Imagine a status network as follows:
Draft
Initiate Workflow
In Review - Reject/Approve
Active
Document starts in draft. The author selects a status of (Initiate Workflow) at which point the workflow starts.
Workflow moves the status from (Initiate Workflow) to (In Review)
and puts a work item in the reviewers mailbox. Reviewers can change the status to (Reject) or (Approve) and each requires a digital signature. After each reject/approve, Workflow moves the status back to (In Review) so that the next person may act. When everyone has reviewed and approved, workflow moves the status to (Active). If anyone has rejected, workflow moves the status back to (Draft.)
This is a simplification, but that's the scenario. WF-BATCH is our workflow ID that has SAP-ALL authorization. Problem occurs when deadline monitoring is in effect. If a reviewer doesn't act within the designated deadline, the monitor fires and the work item is flagged as obsolete. Due to the status network, the only valid path is to either move to (Approve) or (Reject). But since both of those statuses have been set up to require digital signature, they fail. We end up stuck in (In Review) with no way out.
If hard coding the userid WF-BATCH and the password in some table will solve this problem, then we'd be thrilled.
Bill
Edited by: Bill Bessette on Jul 25, 2008 6:00 PM

Digital Signatures/Javascript After Signing?

Similar Messages

Maybe you are looking for