Digital Signature is shown as altered when nothing is modified

Hi,
I have a problem with the digital signature field. After signing the form and saving it, when I next open the form, there will be a icon (green tick + yellow !) indicating that the signature is valid but the document has been updated since signed.
Problem is that nothing has been done to the form. To test the problem, I have created a form with just a text field and a document signature field.
The problem only exists if I checked the 'lock fields after signing' option in the properties. As I need to ensure that no amendments are made after signing, I will need this option.
Can anyone help or does anyone face the same problem?
I am using Adobe Livecyle Designer and Adobe Professional 8.0.
I used Adobe Reader 8.0 to sign the form and to reopen the form again after saving, and the problem will occur.
Hope someone can assist. Thanks.
GM

Hi Daniel,
Really appreciate your help in testing. Wonder if that is a bug in Reader 8. It works fine in my Acrobat Pro 8 too.
However, as I cannot expect my users to have the Pro version, I am really stuck with the reader. Reader 9 has no 'yellow mark' problem, but I will need to manually validate the document every time it is opened.
Can anyone help please? Or at least confirm if that is really a bug. =) Thanks.
Regards

Similar Messages

  • Make printed digital signature disappear if document altered

    We have created a document and digitally signed it.  We have then altered the document.  When the document is viewed on the screen the signature shows as invalid.
    When the document is printed, however, the signature is the same.
    Is there a way of either showing the state of the signature (valid / invalid), or making it disappear on a printed document?
    Note, I did notice a similar question here, but the response was to a link that no longer works.
    Thanks for your help.

    Thanks for this - it would achieve the results, but implementing would be difficult.
    I am trying to imagine the process that a user would have to go through.  Digitally sign a document and then cut and paste a bunch of javascript into the document?  It seems like a step that would be difficult to train people on, and hard to manage.
    Is it be possible to make the check box for a valid signatures visible on print as well as screen?  Maybe that is the best result.  We want to allow printing and annotations, but we just want to prevent someone passing off an altered printed copy as true.  Any solution that accomplishes this would be helpful.

  • Can I bring digital Signatures and with a page when I extract it?

    I have a client who is adding their own digital signature to documents after reading them. Our current methodology involves extracting the page with the signature and adding said page to another adobe document for our records. However, the digital signature never follows. I am thinking this is by design, but I cannot find unequivocal confirmation. Does anyone have documentation or knowledge on this topic that will clearly state whether digital signatures cannot be copied when extracting pages, or if it can. Of course, if they can, I would also like to know how. Thank you very much.
    Eric

    You are correct that this is by design. A digital signature provides an assurance about the entire contents of the document, not just the page that it is on (e.g., the signature field is on the last page of the contract, but the signature covers the entire contract).
    Extracting just the page with signature would never leave you with a valid signature because all the other bytes of the file would be missing so the signature would not validate.
    If you want a validatable record of the signature, you will need to save the entire document. If all you really need is an informal, non-verifiable record, you could try printing the page with the signature to another PDF file which should show what the page looks like. But that is all you'd have so make sure that meets the legal requirements of your situations.

  • Digital signature prompt doesn't appear when case changes in URL

    Hi Everybody,
    I have a Java applet running from a website which is self-signed. Some users at my workplace have been complaining recently that they were no longer being prompted to accept the digital signature on the website and that a triangle with an exclamation mark would show up beside the login screen.
    I found that if those users changed the case of the URL (just one of the subfolders) they were able to get the warning message again. For example:
    If the user was accessing http://www.mycompany.com/Abc/Xyz/ and they changed that to say, http://www.mycompany.com/abc/xyz/ it would work.
    Is it possible that the certificate saved in the users profile is getting corrupt? And by changing the case of the URL it sends out a new warning screen?
    What causes the cache to become corrupt? Why is that some users can use any combination of upper and lower case letters in the URL and they will always be prompted for the digital signature (cannot be verified) and some won't be able to use the default but can use any other combination?
    I tried clearing the java cache and it started prompting me for the digital signature however I was wondering if there was another solution as this is going to become a big support problem.
    Thanks to all for your help.

    It looks to me like this has nothing to do with the digital signature prompt and everything to do with a badly formed URL. In a URL the domain name is not case sensitive but all the path information is case sensitive. Whether one should use http://www.mycompany.com/Abc/Xyz/ or http://www.mycompany.com/abc/xyz/ depends only on what the HTTP server expects. So which of these does the HTTP server expect?

  • Digital signature not showing in PDF when opened and printed with Preview

    Not being able to find anything after searching high and low, I thought I would try my luck here: when I certify a PDF file using a visible signature in Adobe Acrobat Professional that signature does not show when I open the file in Preview or print it from Preview. Preview's Inspector information also claims that I can make changes, which I instructed Adobe not to allow.
    Thanks for any feedback on this!

    Try re-uploading the PDF and then updating the course. Sometimes the conversion doesn't take and the tracking doesn't apply correctly to a PDF.

  • Digital Signatures will not show when combined in one PDF

    I have multiple PDF's with digital signatures. I'm combining them into one large PDF for distribution. The problem I'm having is the digital signatures are not showing up when I combind into one PDF. I need the digital signatures to show up because they make the document (s) official. To sent all the document out indivdual make it unmanageable and is over 300 sperate PDF's

    It is not true. Most documents have pages numbered (like "page 1 of 5"). I never sign documents that do not have this page numbering and each page initialized. This way you cannot add/remove pages in a printed document without forging initials. Electronic documents (PDF) enforce this rule automatically.

  • SOAP 1.2 web service fails when SOAP header has digital signatures

    Hi,
    When we upgraded our JAX-RPC web services from SOAP 1.1 to SOAP 1.2, they started failing with the following response.
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <env:Header>
    <env:Upgrade>
    <env:SupportedEnvelope xmlns:soap12="http://www.w3.org/2003/05/soap-envelope"
    qname="soap12:Envelope"/>
    </env:Upgrade>
    </env:Header>
    <env:Body>
    <env:Fault xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <faultcode>env:VersionMismatch</faultcode>
    <faultstring>Version Mismatch</faultstring>
    <faultactor>http://schemas.xmlsoap.org/soap/actor/next</faultactor>
    </env:Fault>
    </env:Body>
    </env:Envelope>
    The following two errors were in log.xml
    An error occurred for port: {http://xxx.xxx.xxx/xxx/1.0/ws/TestService}TestServicePort: oracle.j2ee.ws.common.soap.fault.SOAP11VersionMismatchException: Version Mismatch.
    Unable to determine operation id from SOAP Message.
    We use web service handlers to add and verify digital signatures. The request message seems to be making it to the web service but is failing before reaching the web service handler which verifies the digital signature.
    Everything works fine when we don't add the digital signatures. The SOAP message without the digital signature doesn't have the SOAP header. I've listed the SOAP message with the digital signature below.
    <env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope"
         xmlns:ns0="http://xxx.xxx.xxx/1.4/"
         xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
         <env:Header>
              <wsse:Security
                   xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
                   <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
                        <ds:SignedInfo>
                             <ds:CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"></ds:CanonicalizationMethod>
                             <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"></ds:SignatureMethod>
                             <ds:Reference URI="#Body">
                                  <ds:Transforms>
                                       <ds:Transform Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"></ds:Transform>
                                  </ds:Transforms>
                                  <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></ds:DigestMethod>
                                  <ds:DigestValue>...</ds:DigestValue>
                             </ds:Reference>
                        </ds:SignedInfo>
                        <ds:SignatureValue>
                        </ds:SignatureValue>
                        <ds:KeyInfo>
                             <ds:X509Data>
                                  <ds:X509Certificate>
                                  </ds:X509Certificate>
                             </ds:X509Data>
                             <ds:KeyValue>
                                  <ds:RSAKeyValue>
                                       <ds:Modulus>
                                       </ds:Modulus>
                                       <ds:Exponent>AQAB</ds:Exponent>
                                  </ds:RSAKeyValue>
                             </ds:KeyValue>
                        </ds:KeyInfo>
                   </ds:Signature>
              </wsse:Security>
         </env:Header>
         <env:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="Body">
              <ns0:SearchRequestMessage
                   xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:gml="http://www.opengis.net/gml"
                   xmlns:xxx="http://xxx.xxx.xxxl/1.4/"
                   xmlns:ns5="http://www.w3.org/1999/xlink"
                   >
                   <xxx:SearchCriteria itemsPerPage="10" maxTimeOut="180000" startIndex="1" startPage="1" totalResults="25">
                   </xxx:SearchCriteria>
              </ns0:SearchRequestMessage>
         </env:Body>
    </env:Envelope>
    We are using Oracle AS 10.1.3.3.0, WSDL 1.1, and SOAP 1.2. Everything works fine with WSDL 1.1 and SOAP 1.1.

    Take a look 'How to Use a Custom Serializer with Oracle Application Server Web Services' [1].
    In your case, you should be looking at BeanMultiRefSerializer (org.apache.soap.encoding.soapenc), which will serialize your data using href and providing a way to deal with cycles.
    All the best,
    Eric
    [1] http://www.oracle.com/technology/tech/webservices/htdocs/samples/serialize/index.html

  • Multiple Digital Signatures?

    Here at my work, we need to use digital signatures in order to protect our sensitive documents. However, sometimes these documents need to go up the chain of command before they are completely "done".
    Is there any possible way to have more than one digital signature on a document? When I put my digital signature on something and sends it to my boss and he signs it...it erases the original signature (mine) and his is the only one there.
    We need to be able to have both of our digital signatures on the document. Is this possible with this, or any other Adobe software?
    FYI: We run on Windows XP, and only a few select people have Adobe Acrobat 7.
    Any suggestions, EVEN if it means buying new Adobe software would be appreciated.

    It's hard for me to send any files, because most of our documents are snesitive materials, and proprietary information.
    We also mainly use things on Microsoft Office 2003 (this document in particular is made via Excel 03), but we are willing to transfer the documents to Adobe in order to get the signatures.
    The way we sign things is digitally. However it seems, in no matter WHAT format we use, we cannot make ANY changes to the document without taking the old signature off.
    These "documents" usually pertain to job orders, or request forms for new jobs. Several people have to sign off on these forms, and almost all of them need to edit/change/add their own stuff to the forms, as the forms go up the chain of command.
    But when the very last person sees it, it needs to be shown as signed by everyone who has seen it. This does not seem possible IF the document is edited in any way.

  • Livecycle & Reader 8, digital signatures problem

    Hello,
    I created a pdf document including digital signature field in livecycle. When saving and opening the document in acrobat 8 pro signing works fine, i.e. I click the signing field and it prompts for digital signature ID & password.
    But, when I click the field in Reader 8 (not pro version), nothing happens. It doesn't prompt for digital signature ID.
    I clearly set the version limit in livecycle to be reader 7 and upwards (not pro versions).

    you need to "enable usage rights in Adobe Reader.." using Acrobat 8 before Reader can sign.

  • Multiple digital signatures in one file

    I have a client who wants me to combine 4 different forms into one--then--require a digital signature by the same person after each independent form. So that would be 4 digital signatures total. And all identical. I'm using a different name per each field so there's no conflict.
    It appears to work fine until I have it submit dynamically with a PHP script via email inbox.
    When I open the PDF (having crunched the info back in from an FDF) the data is there EXCEPT the digital signatures.
    Can someone point me to a tutorial?
    Best regards,
    Mare

    Hi Mare,
    You cannot merge files and expect that the digital signatures will be preserved. When you sign a file you are signing all of the bytes in that file, and only that file. Once you combine files you are creating a new unsigned file. If someone were to sign the new file they are signing all of the bytes in the new file, not just some of the bytes. There is no "page level" signing in PDF files, only whole file signing.
    You can however put the signed files into a Portfolio file. A Portfolio keeps the files separate. Think of a Portfolio like a file cabinet in the physical world. Just because you put different files into the file cabinet drawer, they don't merge.
    Steve

  • Multiple Digital Signatures in one Form

    Hello
    I have an Interactive Forms that requires the digital signing of 6 different users. There is a control under the Web Dynpro Native named : Signature : Sign and Lock which allows multiple signatures but I am not able to use it correctly.
    I need to associate text fields in the form to a certain signature so when the user signs them they are locked BUT but I need to be able to have other text fields open so another user can sign the form. It is only when the second user signs the form that the remaining text fields are locked
    Any idea ?
    Eyal

    Hi Mare,
    You cannot merge files and expect that the digital signatures will be preserved. When you sign a file you are signing all of the bytes in that file, and only that file. Once you combine files you are creating a new unsigned file. If someone were to sign the new file they are signing all of the bytes in the new file, not just some of the bytes. There is no "page level" signing in PDF files, only whole file signing.
    You can however put the signed files into a Portfolio file. A Portfolio keeps the files separate. Think of a Portfolio like a file cabinet in the physical world. Just because you put different files into the file cabinet drawer, they don't merge.
    Steve

  • Verifying digital signatures in PDF documents

    I'm working on verifying PDFs digital signatures.
    I know that when a PDF is signed, a byterange is defined, the certificates get embedded, and from what i've read, the signed message digest and the timestamp are also stored in the PDF.
    I already can extract the certificates and validate them. Now I'm trying to validate the pdf's integrity and my problem is I don't know where the signed message digest is located.
    In this sample signed pdf (http://blogs.adobe.com/security/SampleSignedPDFDocument.pdf), I can clearly identify the digest since it is down below the embedded certificates: /DigestMethod/MD5/DigestValue/ (line 1520).
    But that PDF sample seems to be from 2009, and I suspect the message digest is stored in a different way now, because I signed a PDF with Adobe Reader and I can't find any message digest field like the previous one. Can someone tell if the digests are now stored in a different way? Where are they located?
    Anyway, for now I'm using that sample document, and trying to verify its integrity. I'm getting the document's bytes to be signed acording to the specified byterange, and digesting them with MD5 algorithm, but the digest value I get doesn't match with the one from the message digest field... Am I doing something wrong? Is the digest also signed with the signer's private key?
    I appreciate any help.

    You cannot rely on the digest to be in a certain place in PDF. If you want to manually verify the digest in a PDF signature here's what you need to do.
    1. Open PDF in a Text Editor.
    2. Find Signature Dictionary for your signature.
    3. Get the Hex String which is the value of the /Contents entry in the Signature Dictionary.
    4. Convert Hex String to binary string and discard trailing zeros. Remember that in a Hex string each byte is represented with two characters and the last one might be a zero. So, when you discard zeros make sure that what you get left has even number of bytes.
    5. Use one of the commercially available BER Viewers (you can find free BER Viewers on the Web) to convert the binary string to ANSI.1 representation.
    6. Analyze the BER-decoded PKCS#7 signature object (RFC 2315 describes it) and find the digest that you are looking for in it. It is an OCTET STRING.
    If you want to programmatically validate a signature, you need to write code that does all that. Signature validation includes much more than checking the digest. You need to build chain, validate each certificate in the chain, check revocation for each certificate in the chain, etc. RFC 5280 is the guide what to do.
    Good luck!

  • Digital Signatures in forms

    I'm trying to create a form with a space for a digital signature that can be applied when the document is opened by adobe reader.  I can sign, but everyone else I send it to gets a security message when they try to place a digital signature.  What do I need to do to enable recipients to fill out & digitally sign this form in Adobe Reader?

    I tried that & my test recipient still wasn't able to put a digital signature on it.  Don't know how it's important, but I also saved & sent my document as a standard PDF (not a form), & he was able to put a digital signature on that one.

  • Reader not allowing digital signatures

    I used Adobe9 to create a form so our volunteers/interns can fill it out, sign it and send it back to us via email. I can get everything to work so that it works in Acrobat reader, EXCEPT allow signing. No matter how I've tried, (extending the form, creating a policy to allow filling in forms and signing), when I bring the form up in reader (ver 9.3), the document properties still say signing is not allowed. I've tried other reader versions, same result. This should be so much easier, but I cannot figure for the life of me what is wrong. Any idas?
    Thanks
    Ken

    George,
    That is what I thought too. So I did extend it, and it still won't work. Here is a copy of my security properties after
    I extended it as you mentioned:  ------> 
    I can now save data in the form, but the only thing that is NOT working is this %$#@ digital signature thing. Maybe I don't understand digital signatures enough, but in Acrobat9, when designing a form, I could create a digital signature in the fly. Can't users do that when they view a document in Reader? Is it a properties issue, or can't a user create a digital signature in Acrobat Reader at all? Seems like extending a form takes away the signing property.
    Ken

  • Wrong digital signature for add-on installer

    I have created a addon and it gives error as,
    Wrong digital signature for add-on installer  
    When I tried installing this addon on another SAP server,it worked.On the problamatic server,the antivirus has expired.Is virus capable to creating this problem ? I have tried all the options for solving the problem such as,
    1.Delete the temporary files.
    2.Delete the SBO files.
    3.Create a new addon and release it.
    4.Create a new addon with different name.

    Hi Dilip,
    Refer This...........
    Link: [url] Wrong Executable Digital Signature for Add-on
    Link: [url] SAP Business One AddOn Installer
    Link: [url] Wrong digital signature for add-on installer
    Link: [url] Wrong Digital Signature...
    Thanks
    Shafi
    Edited by: shafi_sunshine on Aug 18, 2011 7:21 AM

Maybe you are looking for