Digital Signature in Document Signature field slow

The business requirement is for users to digital sign a Dynamic PDF. Digital ID's are created using Advanced - Security Settings - Digital ID - Add ID - Create a self-signed digital ID for use with Acrobat - New PKCS#12 digital ID , from Adobe Professional.
In the PDF, the user clicks in a Document Signature field to sign the document. It takes a VERY long time for this signature process to complete.
is there a trick I am missing? Is the slowness due to the way the digital ID was created?

Unfortunately, I cannot forward the form as it contains client data.
I have tested signing another PDF I've created with 2 fields using the same the digital ID's, and the process completed quickly.
Perhaps the problem lies with the size of my form which has 20 pages with 50 fields (on average) per page.
When signing the document, the signature details appear, the "saving file" temporary status bar appears and THEN the hourglass kicks in and takes 5 minutes before control is returned. Is there validation particular to the signing process I can disable? Alternatively, can I specify which pages are certified instead of the entire document?

Similar Messages

Multiple Digital Signatures (certificates) results in VERY slow PDF

I created a form in Lifecycle that typically has 8 signatures. As more signatures are added the form slows down significantly. Our director, who ultimately signs off on the document, has informed us that it took him 35+ minutes to approve 3 documents. The forms are on a network drive. I had read some old threads that mentioned this issue was being investigated and the newer versions of Acrobat should help speed up this process. We are currently running Acrobat X 10.1.4. Any suggestions as to what might be slowing things down? I know the digital signatures require validating and expect it to slow things down a bit but 11+ minutes is probably more than it should be. Thanks

Hi,
Just out of curiousity, if the form has been Reader Enabled, and, if the director could download the free Adobe Reader v11 from the Adobe web site, and he signs the file using version 11, is the signing process faster? It should be much faster in version 11 because we fixed the recursive validation issue that made dealing with multiple signatures so slow.
If you're interested in the nuts and bolts read on, but if not I'll understand...
The way signature validation use to work is Acrobat (and Reader as well because because the signature creation and validation mechanisms are the same in both) would start to validate signature number 8 right after the signature was created (it needs to do the validation so it knows whether or not to put the green check mark next to the signature). As part of the validation process it would need to re-validate each previous signature (and this is where things start to get weird). In order to validate signature 7 it has to also validate all previous signatures (6 thru 1) and every time it validates a new signature it has to do all of the previous signatures. Each signature would get validated as many times as it was part of the revision list. That is, signature 1 got validated eight times, signature 2 seven times and so on.
Begining with version 11 (or XI as it says in the product) we stopped all of the recursive validation and just do each signature once which makes the signature validation process much quicker. I'm always looking for real world examples, and if you can test it with Reader XI I'd appreciate knowing the results.
Thanks,
Steve

Java SSF for Digital Signatures and Document Encryption

Hello,
I have read in "SAP Help - Java Development Manual" that there is a Java SSF library for Digital Signatures and Document Encryption API.
http://help.sap.com/saphelp_nw04s/helpdata/en/4f/65c3b32107964996a56e4165077e24/frameset.htm
I am trying to develop an example application in NWDS using Interfaces/classes (ISsfData, SsfDataXml...), but NWDS does not find this classes in any library.
I have searched for Javadocs in NWDS plugins directory and this classes and interfaces should be in JAR com.sap.security.api.jar, but they aren't there.
Our WAS version is: NW04s WAS 7.0 SP11 and he have downloaded Java Crypto Library (IAIK) and also SAP XML Toolkit.
Does anyone know how to find or obtain this library?
Thanks in advance,
Jorge Linares

Hello Francesco,
I want to generate a digital signature (PKCS#7,XML) using SAP SSF API as explained in
http://help.sap.com/saphelp_nw04/helpdata/en/4f/65c3b32107964996a56e4165077e24/content.htm and in Amol Joshi's reply in
Digital Signatures and Document Encryption api
so my question is From which PI/XI version and its SPS this SAP SSF LIBRARY is supported ?
Kind Regards,
Kubra fatima.

Digital Signatures and Document Encryption api

Hello Expert,
From which SAP NETWEAVER 7.0 SPS Digital Signatures and Document Encryption api is supported ?
I found Javadocs for SAP NetWeaver 04 SPS15.Is this api supported from SPS 15 or prior to SPS 15 also?
Regards,
Kubra Fatima.

Hello Francesco,
I want to generate a digital signature (PKCS#7,XML) using SAP SSF API as explained in
http://help.sap.com/saphelp_nw04/helpdata/en/4f/65c3b32107964996a56e4165077e24/content.htm and in Amol Joshi's reply in
Digital Signatures and Document Encryption api
so my question is From which PI/XI version and its SPS this SAP SSF LIBRARY is supported ?
Kind Regards,
Kubra fatima.

Document Signature Field

How can I use a button to popup the Sign Document (certificate selection screen) similiar to how it is done with the Document Signature Field? Basically, do what the document signature field does but with a button instead?

I forgot to mention one other item. If for some reason it is not possible to do this with a button, is it possible to disable or set to readonly the control?

The document signature field is repeatable

Hi!
I use signature fields in dynamic forms in Acrobat 7 without problems. In Reader and Acrobat 8 signature field is not displayed and in designer there is a warning that is it problem "The document signature field is repeatable" ...
Does someone know how to workaround this "feature", please?
Thanks,
--- Jaroslav

I forgot to mention one other item. If for some reason it is not possible to do this with a button, is it possible to disable or set to readonly the control?

Digital signatures on documents

A requirement from our user community is to have legally binding signatures on documents stored as content. Looking through the online documentation, it doesn't appear that the functionality is "out of the box". Has anyone out there ever done this before? If so, how?

What does the details button reveal?

Document Signature - Validation Issue

This is the recent help i've been trying to get on this subject over at acrobatusers.com. You can read through the issue i'm having through here, answer that was given and my response.
Summary: Basically there are multiple text fields that are set to required, customer name, email...etc. All fields must be locked after being digitally signed (through the document signature field). When default validation pattern are used (blank) it generates an error (Customer field could not be validated). After trying regular expression script, it generates an error (Customer field could not be validated). So i tried a number of different combinations of picture clauses, and from what i'm gathering you have to know exactly how many characters are going to be typed to use that sort of validation. Which in a customer name field you have know idea what their name is going to be (unless you customize a document for each individual customer (not possible)).
If anyone could help on this problem would be a lifesaver. Thank you
::COPY OF HELP QUESTION SUBMITTED::
Apparently I'm not getting the field validation examples in the Help (F1) of Livecycle. I've been struggling to get all the fields in a collection to validate properly. Once I add a Document Signature field to the document and assign the fields to a collection, it doesn't seem to like the default validation settings if I assign the fields to 'User Input: Required' So for the name field I've tried multiple validation patterns all to no avail. My question is how to write a custom validation pattern that allows for an unknown ammount of characters in a name, email..etc. I've tried A A which only validates if the user enters J D for example but John Doe does not work. I've tried other combinations but nothing works. Any help would be appreciated.
Thank you
::ANSWER SUBMITTED BY COMMUNITY EXPERT::
A:There are a couple of things you need to look at. First, is the Acrobat Picture Clause Reference. You can find it and other LiveCycle references on this site
http://partners.adobe.com/public/developer/xml/index_arch.html
The other thing to look at is using a JavaScript validation script with a Regular Expression. Regular Expressions are much more flexible that the picture clause at doing validation.
Answered by Thom Parker on Fri, Jul 6, 2007
::RESPONSE FROM ME BACK::
Q:After reading through the Picture Clause Reference I'm certain there is no way to validate the customer name field without first knowing how many characters will be entered in. And I'm pretty sure there is no simple way of just making it "required" without a pattern to verify against.
The Document Signature Field acts pretty weird if the text field is 'required' and there is nothing to validate it against. Which all in all I just want to make sure it is filled out. Customer Name field (First and Last name) one text field.
So I tried the regular expression route, and added it to the 'Validate' section of the text field. Still I think the problem lies in the way the Document Signature field processes the 'required' fields.
Now I noticed that this only happens if I set the document signature field to lock the required fields after digitally signing the document. This is a mandatory feature the document needs to have, along with the document signature. And the custom stamp option is not a viable solution to this either, since in my field of work everything is questioned whether or not it was altered or forged in some manner. And Custom 'Forged' stamps would not be too difficult to recreate, so that idea is out of the window.
I'm stumped on this and any suggetions as to what route to take would be greatly appreciated. I can not release a document to the customers with validation error messages popping up even though the fields are filled out. Just wouldn't be professional, and down right annoying considering it validates about 15 fields, and everyone except the date and tim

Hey Robert,
I've been having the same issue where, once digitally signed, I end up having an issue with my mandatory fields returning an error '[mandatory field name] validate failed'. Is this the sort of errors you are getting? I'm also trying to find answers on this as I've tried a few things but it hasnt worked well. One thing I did was to change the mandatory field back to optional and coded my submit button using the if clause when the submit button is pressed to check if the this mandatory field is filled in.
if ((pgDetails.txtReqBy.rawValue != null) &&(pgDetails.txtReqBy.rawValue != ""))
event.target.submitForm({cURL:"mailto:[email address]?subject=New/Edit Supplier Detail Form&body=Please find attached the completed form.",cSubmitAs:"PDF",cCharset:"utf-8"});
else
xfa.host.messageBox("Requested by field MUST be filled. Pls enter your full name.");
This seems to work fine except for one thing. If first time around, I fill the form out leaving the mandatory field blank, it returns the message "Requested by field MUST be filled. Pls enter your full name." So now I go back and fill in the mandatory field and, without navigating to another field, I click the submit button, I get the same message "Requested by field MUST be filled. Pls enter your full name." as it has not picked up the new value of the field. Any idea if there is code to make it re-read the field?
Rgds,
Jan

Document SIgnature Status becomes invalid after resigning

Hi all,
I have a form with two Document Signature.
When i clear and resign one of the Document Signature it status is invalid.
Please suggest me a solution.
Regards,
S.V.Satish Kumar

I tested the form you posted. Here is what I found, but I am not completely clear on what all your script is supposed to be doing.
Steps
1) I filled in the first "comment line"
2) I signed the first signature field
3) Results: The signature was valid, the document status (see screen shot 1signature_docstatus.gif) reported the signature was valid. The signature staus was valid as displayed in the signature panel (see screen shot 1signature_detail.gif)
4) I added and filled in a second "comment line"
5) I signed the second signature field
6) Results: The first signature was valid, the second signature was valid, and the document status repored that ther were "unsigned changes" since the last signature was applied (see screen shot 2signature_docstatus.gif) The signature statuses were valid with subsequent changes made to the document as displayed in the signature panel (see screen shot 2signature_detail.gif)
Don't confuse the "exclamation" mark icon with "Invalid", it is only a warning to inform you that changes have been made that are not "digitally signed", I suspect your some part of your script is causing this. If you want to have Acrobat\Reader display a green check mark icon, then you cannot make any changes to the document after the final signature has been applied.
If you haven't done so, take a look at the sample I posted on your duplicate post in this forum ( http://forums.adobe.com/thread/492773?tstart=0 ).
If a signature is "invalid" it will display a red "X" icon.
Regards
Steve

? using multiple approval signatures, each locking the fields with collections

Having fun with LiveCycle to make a "signoff" sheet that will allow a customer to request a "new product" with a PDF form. Once that information is added to our EDR (Eng Design Request) form, I want the form to be forwarded to multiple departments, where each department manager adds their name, date, comments, and then signs the document and forwards it to the next manager. I have it set up with "locking" a "collection fields" with each signature, and that is cool to lock their comments to thier signature, such that someone else can't change their comments without first "clearing" their signature field... just what I wanted, cool,, taking it a step further, I wanted to have the original product data protected such that once signed by one, or more managers (Eng, Sales, President), that the data was locked unless all signatures were cleared. I tried this first by including the product definition fields in every signature's "collection of fields" (set to lock after signing). Thought that would be the ticket, pretty pumped to try it, but once I clear one signature, example the "Eng manager signature" I can go in and mess with the specs and then re-sign the document, and the other signatures are still there, thought I have to clear them, not good,,, 2nd try, I then tried to lock the preceeding "signature field" itself with the next signature (added "sig0" to "sig1" collection) and that worked once, but fell apart on the third approval, as clear one signature openned things right up, when it shouldn't have. Anyway, has anyone found a way to have an approval signoff sheet where once signed the data fields are locked unless all the signature(s) are cleared. I think the programming is not handing multiple locks on the sme field properly, ie all locks on that field must be removed for that field to become editable,, There may be a better way to tackle this..
PS, I have really learned to be cautious when saving the form out of LiveCyle, then renaming it and save out or "Pro" with read permisions enabled, then see if "Reader" can open it,,, if U R not carefull you get and error that the "document has changed and reader can't save, contact the author,,," that was scary as I had to surf through lots of old revs to find one that would work again, something salvagable without going back to MSWord,,,
Thanks for your help...

I think I found a way to get it to do what I want,,,
1) Use the first signature collection lock to lock only the fields that that person is signing-off on.
2) The next manager then signs off and locks only his comments and text boxes, as well as the signature of the preceeding manager. This way text fields are only locked by one signature collection and thus to edit anything you have to clear that manager's signature to edit the related text boxes, then to re-sign that section you must clear the other (higher level) signatures to open up the signature field for resigning,,, I think this is providing the protection I want,,, Yea,,, let's get this form back into our stupid ISO system ;)

How can I add document signatures to a dynamic table?

I have a table where I am adding rows dynamically by adding a + or - button to add or remove rows to add to the table.
Right now I have a name field and an e-sign field. The problem I am having is that the document signature cannot be repeatable/ needs to be unique and so cannot be added to a dynamic table? Is there a work around for this?
Ultimately what I want is to have a PDF form look like below:
+ -
First Name | Last Name | Signature
First Name | Last Name | Signature
When the user clicks on + from the form above, then it just adds a new row like:
+ -
First Name | Last Name | Signature
First Name | Last Name | Signature
First Name | Last Name | Signature
Problem is the e-signature is a new instance and it says it cannot be repeatable? I want these to be different signatures but on one form to be added dynamically. Does this make sense? How can I do this?

I have a table where I am adding rows dynamically by adding a + or - button to add or remove rows to add to the table.
Right now I have a name field and an e-sign field. The problem I am having is that the document signature cannot be repeatable/ needs to be unique and so cannot be added to a dynamic table? Is there a work around for this?
Ultimately what I want is to have a PDF form look like below:
+ -
First Name | Last Name | Signature
First Name | Last Name | Signature
When the user clicks on + from the form above, then it just adds a new row like:
+ -
First Name | Last Name | Signature
First Name | Last Name | Signature
First Name | Last Name | Signature
Problem is the e-signature is a new instance and it says it cannot be repeatable? I want these to be different signatures but on one form to be added dynamically. Does this make sense? How can I do this?

Placing Electronically Captured Signature on Documents

I need to identify a solution that takes a document we create in SAP and apply an electronic signature from a signature pad, like that used when you use your charge card. Each document and signature will be different u2013 this is not a static signature or a digital signature. We do not want to print a hardcopy, have the customer sign it, and scan it back into the system for storage.
The ideal solution will be only one hardcopy signed document which would be given to the customer. We would have an electronically stored copy of the document (with signature) saved internal to the company. The solution would not involve any hardcopies stored by our company and no scanning of any hardcopies.
A hypothetical example would be to store a signed copy of a grocery store order.
u2022     A customer shops at the grocery store and then proceeds to check out.
u2022     The clerk then registers the order.
u2022     The customer signs the electronic signature pad and receives a copy of their order with their signature.
u2022     The system u201Cplacesu201D the electronically captured signature on the appropriate location on the order and stores the signed order for later reference. This is all on one image u2013 the order with the signature.
Is anyone familiar with this kind of functionality working in SAP?

Hi Robert,
I'm not sure about any such feature in SAP, but, can suggest you some solution to achieve this.
If you can link the signature on the pad with automatic naming of the image file generated, (e.g. Bill No. + Date + Time Stamp) and store it in a central repository.
You can then pass this name via an RFC to SAP and call a SMARTFORM for bill storing.
The SMARTFORM can then read the image file from the central repository and print the dynamic image as required.
Regards,
Pranav.

Document Signatures and Submiting via email

Hi,
My issue involves submitting an email and populating a document signature.
Using javascript I've set the preSubmit field to have the following line of code:
Page1.SignatureField1.validate.nullTest = "error";
I've enabled in Acrobat Professional 8, Enable Usage Rights.
While testing the form, when I select Submit by Email I get the error saying that "At least one required field was empty on export. Please fill in the required fields (highlighted) before continuing."
All well and good as this is what I want to occur.
The problem is once I sign the the document (which is the field that I've set to be validated in the above code), then click submit via email again I still get the above error message.
I tested this with the other objects such as text fields etc, they all work fine. The problem only occurs while trying to use a document signature field.
What am I doing wrong?

You need to remember the password, Adobe software does not offer any back door or password recovery for the creator.
It is recommended that, when setting certain things for a PDF, you keep the "before" file carefully as well as the "after". These things include security, reader extensions and signatures - all things that can be impossible to undo.

Can I create a digital id for electronic signatures in adobe reader for ipad?

Can I create a digital id for electronic signatures in adobe reader for ipad?

No, digital signatures are not supported in Reader for iOS.

Document signature with date/time received stamp

Does anyone know if you can combine the feature of a date/time received stamp with the signature of the person who received it?
Regards,
Sean

Hi Sean,
The way a time stamp works is that it's a signature over the document signature, kind of like when a notary public signs a document. They (the notary) are not verifying the accuracy of the document, only that you signed it and when you signed it.
Generally (can you sense that this is going to get more complicated then it should be ), a time stamp is created (by a trusted third party) at signing time to prove that the signature existed a a particular point in time. If you timestamp your signature at signing time it cannot be time stamped again by the receiving party. If the receiving party wants to add a timestamp they need to sign the document themselves. An example of this is the patent office. It doesn't matter to them what time you signed the patent application, but rather when they received it. They add their own timestamp to show what time the application was received by signing the document a second time.
Now just to confuse things a bit, starting with Acrobat 9.1.0, if the signature was not time stamped at signing time, it has the ability to add a timestamp post signing. You can add the timestamp by opening the Signature Panel, right mouse click on the signature, and select Add Verification Information from the pop-up menu. You must have a timestamp server configured in the Security Settings console and the Include signature's revocation status when signing preference selected in order for this feature to be available, and the signature must be valid. You cannot add a timestamp post signing over an invalid signature.
I hope this helps,
Steve

Digital Signature in Document Signature field slow

Similar Messages

Maybe you are looking for