Java 45 electronic signature problems

Hi there
Im trying to apply for a job online and it is asking for an electronic signature. When i go through the steps to get one it checks my computer, browser and java. It failed on the java check because I had the latest version of java and it suggested that i have java hotspot(tm) 1.6.0_32 - 1.7.0_45 .
So i uninstalled my java and installed 1.7.0_45.
Now the check isnt detecting java at all. Ive been into the java control centre and played around with security settings but nothing seems to be working.
Any ideas?
I am on a windows 7 PC and using Internet Explorer (because Chrome fails the browser check for this particular job application website).

Hi,
You are correct that Adobe follows RFC 2560 when it comes to processing OCSP responses, but it's not section 2.2. that covers the issue you raise, rather section 4.2.2.2 - Authorized Responders. It's explained very clearly in section 4.2.2.2 what entity is authorized to sign the OCSP response. As you will note in this section one way to configure an application is to set up a local configuration and Acrobat being fully RFC 2560 compliant does allow you to do just that.
Your best bet is to review the Security Admin Guide which you can find at http://learn.adobe.com/wiki/download/attachments/52658564/acrobat_reader_security_9x.pdf?v ersion=1 specifically section 5.4.1.1 which has all of the setting you need to configure a local configuration.
Steve

Similar Messages

Electronic signature problems - documents are corrupting

I've been having periodic issues with people trying to electronically sign PDFs. Saving the document to a server, having the signatories open it (one person at a time!) and then trying to sign and then getting an error message "The document could not be signed". This corrupts the file in terms of signatures; once that error appears, nobody else can sign any other signature space, they get the same error message, and signatures are deemed "invalid".
Has anyone else experienced this issue, and if so, what are the possible solutions?

It's possible to automate the process. You can use a batch process (aka Action) that adds a digital signature field to each document in a collection and then signs it. The JavaScript methods you'd use include doc.addField and field.signatureSign:
http://livedocs.adobe.com/acrobat_sdk/9.1/Acrobat9_1_HTMLHelp/JS_API_AcroJS.88.435.html
http://livedocs.adobe.com/acrobat_sdk/9.1/Acrobat9_1_HTMLHelp/JS_API_AcroJS.88.758.html

Electronic signature - I am not able to sign it, it appears "cryptoghrapy problem code error 13" ?

Last week I was able to sign documents electronically. I got the version Adobe Distiller 9. My electronic signature is linked to a FIS certificate issued by Exostar. This is a corporate FIS certificate, work for Rolls Royce.
Everytime that I am going to sign it appears "cryptoghrapy problem code error 13".
I have no clue what is wrong. Any suggestion.
Thanks and regards,
Lucas

[discussion moved to Creating, Editing & Exporting PDFs forum]

Capturing electronic signature in the Webdynpro for java applicaiton.

Hi! All,
Can you please tell me the way to capture the electronic signature in my Webdynpo for Java application.?
Thanks and Regards,
M.D.Sahu

Hi,
I did it with IFrame control that generates a script (javascript) with Smart Card.
The user has a smart card with electronic id, when the user wants to sign the form the script generate a smrt card logon.
The user has to identify with finger print and the electioc signiture is added to the form (Adobe).
the main issue in this project was where to activate script (server side or client side).
enjoy,,,,
AmitY

Having problems combining PDF files with electronic signatures...

I have Adobe Pro XI and I've been trying to combine numerous PDF files. They are each 2 pages and contain electronic signatures. When I attempt to combine them it appears to be working and then suddenly Adobe just closes with no error message or anything??

Think about it: You sign a document and then someone adds some pages to it
and pretends you signed those as well. You wouldn't what that to happen,
would you? Well, with digital signatures it can be prevented.
On Mon, Dec 8, 2014 at 10:39 PM, breeberry09 <[email protected]>

Timestamp problem on electronic signatures

On time stamps for electronic signatures, it adds -05'00'.
We don't want that in the date stamp. How do we resolve this issue?
Adobe Acrobat X Pro Version 10.1.13

Do you get it in the Advanced Signature Properties dialog? What is the exact text?
Acrobat uses UTC time with the local time offset. This is what -05'00' means. It is time at the East Coast in USA.

Multiple electronic signatures in PDF portfolio

I Have a PDF portfolio that has multiple PDFs in it each requiring 1 or more electronic signatures. The problem is that after the first person signs one of the PDFs no one else is able to and they receive an error saying it's already open or they have read only access

Which Acrobat version do you have? I've heard that there is a bug in this area in Acrobat 11.0.7. I do not have personal experience with it and I do not know how soon it will be fixed.

How do I add an electronic signature to a document?

Hello and thanks in advance for your help. How do I add an electronic signature to a document?

Sergio
Glad you stepped in and elucidated my inadequate explanation.
Step by Step explanations of the problem will get Step by Step instructions, but its been a week and the O.P. hasn't elaborated on what they actually want.
You may consider it a horrible answer, what was your opinion of the question?
Peter
PS I looked hard but couldn't find a reference to Preview in my post.

How do I add an electronic signature to a pages document

how do I add an electronic signature to a pages document?

Sergio
Glad you stepped in and elucidated my inadequate explanation.
Step by Step explanations of the problem will get Step by Step instructions, but its been a week and the O.P. hasn't elaborated on what they actually want.
You may consider it a horrible answer, what was your opinion of the question?
Peter
PS I looked hard but couldn't find a reference to Preview in my post.

Error message "The document could not be saved. This file is already open" when trying to complete an electronic signature.

Running Adobe Acrobat Professional 10.1.0. I cannot upgrade to newer version because several applications were already tested on this version.
When trying to complete an electronic signature, my users receive the error message ""The document could not be saved. This file is already open". When they close and open the file again to try to sign again they find a corrupted electronic signature. Instead of a clean signature with the box colored in light blue they see their signature with the embedeed message Click Here to Verify & Sign with the box colored in grey.
We turned off antivirus in the Sharefolder where the forms are stored and nothing. We turned off the antivirus on the client and nothing. We stored the files in another server and nothing. One workaround is saving the file in the desktop, signing it, and then back to the Sharefolder. Another is saving the file with a different file name.
I've searched and the only similar thing was caused by the Windows Preview Pane. See Information Transmogrification: Adobe Acrobat saving a file does not work, displays “File may be read-only”. No luck with this one too.
Is definitively an intermittent problem. The users that experience the problem experience it intermittently.
This started to happen when we move our computers to Windows 7.
Any ideas?

Correction on Question:
This is a web application and the users need to be able to load the editable .pdf form from the website, edit it and submit it back to the website from within Internet Explorer.
Users began getting the error message:
'The document could not be saved. This file is already open.'
last Friday after having no problems prior to this. Some users can edit the editable .pdf forms on the website and save the file with the same name to the website. Some get the error mentioned in the subject.
We really need help getting this resolved.
Sandy Martin

Printing issue with Electronic Signatures

In the footer of my document, i place document properties and also use the captioning feature for tables and figures. I have saved it in native 2010 format not in a compatability mode.
When I print my document (paper or PDF) these fields print properly.
After I electronically sign the document and look at the document on the screen, the fields and caption numbers (Table 1-1: Intended Audience) appear correctly. When I print to PDF or paper, the numbers disappear (Table 1-: Intended Audience) and they
also disappear from the screen.
When I close the document and reopen it, the fields are correct. It only changes after the document prints.
Using Microsoft Office Professional Plus 2010 Version 14.0.6023.1000 (32-bit).
(--merging--)
The original document was a 2007 document opened/stored in the 2010 format.
Reproduced with new 2010 document simply by creating two properties:
Template Version - Test - Value 1.0
Template Date - Date - Value 1/25/2012
And doing the following:
Using the default Normal template with calibri as the font
Added a heading level 1 to the document
Added a 2x2 table with Insert Caption including the chapter number based on heading 1 below the table
Added the template version and template date as two lines on the page
Inserted a signature line
Created a footer with the template version, page number aligned center (via tab), template date alighted right (via tab)
Printed without signing and all data was present (Table 0-1: Test)
Signed the document and printed. The following was missing:
The template date in the footer.
The table label was Table 0-: Test
The template date was present in the middle of the document

Hi,
Is this problem only affect Word program with Electronic Signatures?
Please try to test Printing with different printer drivers.
If the Word printing problem occurs only when you print documents with a certain font or a certain type of graphics image, try to print to another printer.
If no other printer is available, contact the manufacturer to find out whether there is an updated version of the driver or a different driver that works with your printer model.
You may also follow other methods in this KB article troubleshoot print issue in word:
http://support.microsoft.com/kb/826845
Best regards.
William Zhou
TechNet Community Support

Troubleshooting Electronic Signature in Adobe X Standard

Trying to assist a coworker in setting up an electronic signature with password. When walking her through the screens, I noticed the "Add Digital ID" popup box does not show "Key Algorith" or "Use digital ID for" sections (mine does). She does not get the prompt to make up a password and enter twice. She says that she gets a box that wants her to enter a password but she has not created one. Any assistance is greatly appreciated. I am new to Adobe so I am limited in my knowledge.

Employee states this solved the password problem but now her written signature is extremely small when placed on a document.
Cheryl A. Henson
Deputy Director
Board of Review
State Capitol Complex
Building 6, Room 817-B
Charleston, WV 25305
Phone: 304-558-2019
Fax: 304-558-1992
Email: [email protected] <mailto:[email protected]>
The information contained in this electronic message is legally privileged and confidential under applicable law and is intended for the use of the individual or entity named above. If the recipient of this message is not the above-named recipient, you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited.

Implementing XAdES in Java XML Digital Signature API

Hi,
I've got some problems with implementing XAdES standard with Java XML Digital Signature API. Below is a code (SignatureTest1), that produces a digital signature with some XAdES tags placed in <ds:Object> tag. The signature is later validated with a Validator class. Everything works fine, until I set a XAdES namespace (SignatureTest1.xadesNS="http://uri.etsi.org/01903/v1.3.2#"). In this case validation of XAdES elements fails.
The reason of validation failture is a difference between arguments passed to a digest method when document is being signed and validated. When the document is being signed a log looks like this:
FINER: Pre-digested input:
2007-08-21 15:38:44 org.jcp.xml.dsig.internal.DigesterOutputStream write
FINER: <SignedProperties xmlns:ds="http://www.w3.org/2000/09/xmldsig#" Id="SignP"></SignedProperties>
2007-08-21 15:38:44 org.jcp.xml.dsig.internal.dom.DOMReference digest
FINE: Reference object uri = #SignP
2007-08-21 15:38:44 org.jcp.xml.dsig.internal.dom.DOMReference digest
FINE: Reference digesting completed,but while validating:
FINER: Pre-digested input:
2007-08-21 15:38:44 org.jcp.xml.dsig.internal.DigesterOutputStream write
FINER: <SignedProperties xmlns="http://uri.etsi.org/01903/v1.3.2#" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" Id="SignP"></SignedProperties>
2007-08-21 15:38:44 org.jcp.xml.dsig.internal.dom.DOMReference validate
FINE: Expected digest: MAQ/vctdkyVHVzoQWnOnQdeBw8g=
2007-08-21 15:38:44 org.jcp.xml.dsig.internal.dom.DOMReference validate
FINE: Actual digest: D7WajkF0U5t1GnVJqj9g1IntLQg=
2007-08-21 15:38:44 org.jcp.xml.dsig.internal.dom.DOMXMLSignature validate
FINE: Reference[#SignP] is valid: falseHow can I fix this?
Signer class:
import java.io.FileInputStream;
import java.io.FileOutputStream;
import java.io.OutputStream;
import java.security.KeyPair;
import java.security.KeyPairGenerator;
import java.util.ArrayList;
import java.util.Collections;
import java.util.Iterator;
import java.util.List;
import javax.xml.crypto.dom.DOMStructure;
import javax.xml.crypto.dsig.CanonicalizationMethod;
import javax.xml.crypto.dsig.DigestMethod;
import javax.xml.crypto.dsig.Reference;
import javax.xml.crypto.dsig.SignatureMethod;
import javax.xml.crypto.dsig.SignedInfo;
import javax.xml.crypto.dsig.Transform;
import javax.xml.crypto.dsig.XMLObject;
import javax.xml.crypto.dsig.XMLSignature;
import javax.xml.crypto.dsig.XMLSignatureFactory;
import javax.xml.crypto.dsig.dom.DOMSignContext;
import javax.xml.crypto.dsig.dom.DOMValidateContext;
import javax.xml.crypto.dsig.keyinfo.KeyInfo;
import javax.xml.crypto.dsig.keyinfo.KeyInfoFactory;
import javax.xml.crypto.dsig.keyinfo.KeyValue;
import javax.xml.crypto.dsig.spec.C14NMethodParameterSpec;
import javax.xml.crypto.dsig.spec.TransformParameterSpec;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.stream.StreamResult;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.NodeList;
import com.sun.org.apache.xml.internal.security.utils.IdResolver;
public class SignatureTest1 {
     public static String xadesNS=null;//"http://uri.etsi.org/01903/v1.3.2#";
     public static String signatureID="Sig1";
     public static String signedPropID="SignP";
     public static void main(String[] arg) {
        try{
          XMLSignatureFactory fac = XMLSignatureFactory.getInstance("DOM");
          List<Reference> refs = new ArrayList<Reference>();
          Reference ref1 = fac.newReference
              ("", fac.newDigestMethod(DigestMethod.SHA1, null),
                  Collections.singletonList
                (fac.newTransform
               (Transform.ENVELOPED, (TransformParameterSpec) null)),
               null, null);
          refs.add(ref1);
          Reference ref2 = fac.newReference("#"+signedPropID,fac.newDigestMethod(DigestMethod.SHA1,null),null,"http://uri.etsi.org/01903/v1.3.2#SignedProperties",null);
          refs.add(ref2);
          SignedInfo si = fac.newSignedInfo
              (fac.newCanonicalizationMethod
               (CanonicalizationMethod.INCLUSIVE_WITH_COMMENTS,
                (C14NMethodParameterSpec) null),
               fac.newSignatureMethod(SignatureMethod.DSA_SHA1, null),
               refs);
         KeyPairGenerator kpg = KeyPairGenerator.getInstance("DSA");
          kpg.initialize(512);
          KeyPair kp = kpg.generateKeyPair();
          KeyInfoFactory kif = fac.getKeyInfoFactory();
          KeyValue kv = kif.newKeyValue(kp.getPublic());
         KeyInfo ki = kif.newKeyInfo(Collections.singletonList(kv));
          DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
          dbf.setNamespaceAware(true);
          Document doc =
              dbf.newDocumentBuilder().parse("purchaseOrder.xml");
          DOMSignContext dsc = new DOMSignContext
              (kp.getPrivate(), doc.getDocumentElement());
          dsc.putNamespacePrefix(XMLSignature.XMLNS, "ds");
          Element QPElement = createElement(doc, "QualifyingProperties",null,xadesNS);
        QPElement.setAttributeNS(null, "Target", signatureID);
        Element SPElement = createElement(doc, "SignedProperties", null,xadesNS);
        SPElement.setAttributeNS(null, "Id", signedPropID);
        IdResolver.registerElementById(SPElement, signedPropID);
        QPElement.appendChild(SPElement);
        Element UPElement = createElement(doc, "UnsignedProperties", null,xadesNS);
        QPElement.appendChild(UPElement);
        DOMStructure qualifPropStruct = new DOMStructure(QPElement);
        List<DOMStructure> xmlObj = new ArrayList<DOMStructure>();
        xmlObj.add(qualifPropStruct);
        XMLObject object = fac.newXMLObject(xmlObj,"QualifyingInfos",null,null);
        List objects = Collections.singletonList(object);
        XMLSignature signature = fac.newXMLSignature(si, ki,objects,signatureID,null);
          signature.sign(dsc);
          OutputStream os = new FileOutputStream("signedPurchaseOrder.xml");
          TransformerFactory tf = TransformerFactory.newInstance();
          Transformer trans = tf.newTransformer();
          trans.transform(new DOMSource(doc), new StreamResult(os));
        }catch(Exception e){
             e.printStackTrace();
        try{
        Validator.main(null);
        }catch(Exception e){
             System.out.println("Validator exception");
             e.printStackTrace();
     public static Element createElement(Document doc, String tag,String prefix, String nsURI) {
          String qName = prefix == null ? tag : prefix + ":" + tag;
         return doc.createElementNS(nsURI, qName);
}Validator class:
import javax.xml.crypto.*;
import javax.xml.crypto.dsig.*;
import javax.xml.crypto.dom.*;
import javax.xml.crypto.dsig.dom.DOMValidateContext;
import javax.xml.crypto.dsig.keyinfo.*;
import java.io.FileInputStream;
import java.security.*;
import java.util.Collections;
import java.util.Iterator;
import java.util.List;
import javax.xml.parsers.DocumentBuilderFactory;
import org.w3c.dom.Document;
import org.w3c.dom.NodeList;
* This is a simple example of validating an XML
* Signature using the JSR 105 API. It assumes the key needed to
* validate the signature is contained in a KeyValue KeyInfo.
public class Validator {
    // Synopsis: java Validate [document]
    //       where "document" is the name of a file containing the XML document
    //       to be validated.
    public static void main(String[] args) throws Exception {
     // Instantiate the document to be validated
     DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
     dbf.setNamespaceAware(true);
     Document doc =
            dbf.newDocumentBuilder().parse(new FileInputStream("signedPurchaseOrder.xml"));
     // Find Signature element
     NodeList nl =
         doc.getElementsByTagNameNS(XMLSignature.XMLNS, "Signature");
     if (nl.getLength() == 0) {
         throw new Exception("Cannot find Signature element");
     // Create a DOM XMLSignatureFactory that will be used to unmarshal the
     // document containing the XMLSignature
     XMLSignatureFactory fac = XMLSignatureFactory.getInstance("DOM");
     // Create a DOMValidateContext and specify a KeyValue KeySelector
        // and document context
     DOMValidateContext valContext = new DOMValidateContext
         (new KeyValueKeySelector(), nl.item(0));
     // unmarshal the XMLSignature
     XMLSignature signature = fac.unmarshalXMLSignature(valContext);
     // Validate the XMLSignature (generated above)
     boolean coreValidity = signature.validate(valContext);
     // Check core validation status
     if (coreValidity == false) {
             System.err.println("Signature failed core validation");
         boolean sv = signature.getSignatureValue().validate(valContext);
         System.out.println("signature validation status: " + sv);
         // check the validation status of each Reference
         Iterator i = signature.getSignedInfo().getReferences().iterator();
         for (int j=0; i.hasNext(); j++) {
          boolean refValid =
              ((Reference) i.next()).validate(valContext);
          System.out.println("ref["+j+"] validity status: " + refValid);
     } else {
             System.out.println("Signature passed core validation");
     * KeySelector which retrieves the public key out of the
     * KeyValue element and returns it.
     * NOTE: If the key algorithm doesn't match signature algorithm,
     * then the public key will be ignored.
    private static class KeyValueKeySelector extends KeySelector {
     public KeySelectorResult select(KeyInfo keyInfo,
                                        KeySelector.Purpose purpose,
                                        AlgorithmMethod method,
                                        XMLCryptoContext context)
            throws KeySelectorException {
            if (keyInfo == null) {
          throw new KeySelectorException("Null KeyInfo object!");
            SignatureMethod sm = (SignatureMethod) method;
            List list = keyInfo.getContent();
            for (int i = 0; i < list.size(); i++) {
          XMLStructure xmlStructure = (XMLStructure) list.get(i);
                 if (xmlStructure instanceof KeyValue) {
                    PublicKey pk = null;
                    try {
                        pk = ((KeyValue)xmlStructure).getPublicKey();
                    } catch (KeyException ke) {
                        throw new KeySelectorException(ke);
                    // make sure algorithm is compatible with method
                    if (algEquals(sm.getAlgorithm(), pk.getAlgorithm())) {
                        return new SimpleKeySelectorResult(pk);
            throw new KeySelectorException("No KeyValue element found!");
        //@@@FIXME: this should also work for key types other than DSA/RSA
     static boolean algEquals(String algURI, String algName) {
            if (algName.equalsIgnoreCase("DSA") &&
          algURI.equalsIgnoreCase(SignatureMethod.DSA_SHA1)) {
          return true;
            } else if (algName.equalsIgnoreCase("RSA") &&
                       algURI.equalsIgnoreCase(SignatureMethod.RSA_SHA1)) {
          return true;
            } else {
          return false;
    private static class SimpleKeySelectorResult implements KeySelectorResult {
     private PublicKey pk;
     SimpleKeySelectorResult(PublicKey pk) {
         this.pk = pk;
     public Key getKey() { return pk; }
}PurchaseOrder.xml
<?xml version="1.0" encoding="UTF-8"?>
<PurchaseOrder>
<Item number="130046593231">
<Description>Video Game</Description>
<Price>10.29</Price>
</Item>
<Buyer id="8492340">
<Name>My Name</Name>
<Address>
   <Street>One Network Drive</Street>
   <Town>Burlington</Town>
   <State>MA</State>
   <Country>United States</Country>
   <PostalCode>01803</PostalCode>
</Address>
</Buyer>
</PurchaseOrder>signedPurchaseOrder.xml with XAdES namespace:
<?xml version="1.0" encoding="UTF-8" standalone="no"?><PurchaseOrder>
<Item number="130046593231">
<Description>Video Game</Description>
<Price>10.29</Price>
</Item>
<Buyer id="8492340">
<Name>My Name</Name>
<Address>
   <Street>One Network Drive</Street>
   <Town>Burlington</Town>
   <State>MA</State>
   <Country>United States</Country>
   <PostalCode>01803</PostalCode>
</Address>
</Buyer>
<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#" Id="Sig1"><ds:SignedInfo><ds:CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments"/><ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#dsa-sha1"/><ds:Reference URI=""><ds:Transforms><ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/></ds:Transforms><ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><ds:DigestValue>tVicGh6V+8cHbVYFIU91o5+L3OQ=</ds:DigestValue></ds:Reference><ds:Reference Type="http://uri.etsi.org/01903/v1.3.2#SignedProperties" URI="#SignP"><ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><ds:DigestValue>MAQ/vctdkyVHVzoQWnOnQdeBw8g=</ds:DigestValue></ds:Reference></ds:SignedInfo><ds:SignatureValue>lSgzfZCRIlgrgr6YpNOdB3XWdF9P9TEiXfkNoqUpAru/I7IiyiFWJg==</ds:SignatureValue><ds:KeyInfo><ds:KeyValue><ds:DSAKeyValue><ds:P>/KaCzo4Syrom78z3EQ5SbbB4sF7ey80etKII864WF64B81uRpH5t9jQTxeEu0ImbzRMqzVDZkVG9
xD7nN1kuFw==</ds:P><ds:Q>li7dzDacuo67Jg7mtqEm2TRuOMU=</ds:Q><ds:G>Z4Rxsnqc9E7pGknFFH2xqaryRPBaQ01khpMdLRQnG541Awtx/XPaF5Bpsy4pNWMOHCBiNU0Nogps
QW5QvnlMpA==</ds:G><ds:Y>p48gU203NGPcs9UxEQQQzQ19KBtDRGfEs3BDt0cbCRJHMh3EoySpeqOnuTeKLXuFr96nzAPq4BEU
dNAc7XpDvQ==</ds:Y></ds:DSAKeyValue></ds:KeyValue></ds:KeyInfo><ds:Object Id="QualifyingInfos"><QualifyingProperties Target="Sig1" xmlns="http://uri.etsi.org/01903/v1.3.2#"><SignedProperties Id="SignP"/><UnsignedProperties/></QualifyingProperties></ds:Object></ds:Signature></PurchaseOrder>

I believe the problem is that you are not explicitly adding the xades namespace
attribute to the SignedProperties element before generating the signature. Thus,
the namespace attribute is not visible when canonicalizing, but when you serialize the
DOM tree to an output stream, (for reasons I'm not entirely sure why), the namespace
attribute is visible and is added to the SignedProperties element, which breaks the
signature.
You must always explicitly add namespace attributes using the Element.setAttributeNS
method. Try changing the following code from:
Element SPElement = createElement(doc, "SignedProperties", null,xadesNS);
to:
Element SPElement = createElement(doc, "SignedProperties", null,xadesNS);
SPElement.setAttributeNS("http://www.w3.org/2000/xmlns/", "xmlns", xadesNS);

I cannot place an electronic signature in a document with form fields?!

I have Acrobat Pro installed on a windows 7 and windows 8.1 machine. On both I have lost the ability to place an electronic signature (Draw my signature) and only have the option for a digital signature. The problem is remedied if I print to pdf but then I lose the form fields.
I'm an idiot and so are the people that I need to send this to. I just want to easily fill the necessary fields out, draw my signature and forward it to the next guy to do the same so that it can be printed and turned in. Digital signatures are severe overkill for this (and i'm not going to be able to teach everyone how to create one) and I need to know how to re-enable the ability to electronically sign and keep the form fields.

re: "Digital signatures are severe overkill for this"
Yep, I discovered that as well.
I rolled my own "signature" for a client...I just added a 3 character "initials" field and a "Certify" button.
The initials act as the signature and once they hit the certify button, all form fields are set to read-only....via custom javascript.
The only problem is that I am unable to SAVE the document via javascript because of Acrobat trusted functions....
which I don't have.
So I just prompt the user to Save the document at that time.
It's a little ugly, but it works..

Electronic Signature Field Indicator

We are deploying an eForms application that uses the standard electronic signature field from the Designer object library. The basic process flow is: (1) Form is rendered via an XDP file from the Form Server using the Reader Extensions API to apply rights. (2) User completes the form and signs using the self-signed signature field. The field displays a check-mark indicating the form is signed correctly. (3) User hits "submit" button which invokes a processForm servlet that sends the form as a PDF file attachment within an email to an internal mailbox. Problem: when we open the PDF form in the mailbox, it shows a "?" in the signature field. As you hover over this field, you get the following message: "Signer's identify unknown, the document has been updated since signed". This message will be confusing to our users that will process the PDF form attachment.

I don't believe so. You can of course export the Crystal report to pdf but the electronic signature part would require custom programming.

Java 45 electronic signature problems

Similar Messages

Maybe you are looking for