Disabling a digital signature in LiveCycle

I have a form that have a yes / no question with checkboxes.
In some cases there should be multiple digital signatures, in others only 1.
I want the digital signature line to be disabled if the "No" checkbox is selected.
I would also like the space where the digital singature goes to say "N/A" if the second digital signature is unnecessary.
Is that possible?
Thanks,

Which version of LiveCycle Designer are you using? Action Builder is available in latest versions of Designer and it's very easy to use.
Action Builder option should be available under Tools Menu and you can go through Designer help to learn more about it.
Attached a sample file (SigFields.pdf) might help.
--Santosh

Similar Messages

How can I disable the digital signature feature?

how can I disable the digital signature feature?

If it can be done (doubtful) there will be details in the Enterprise Deployment documentation. Enterprise Deployment (Acrobat and Reader)

Digital signatures in LiveCycle forms

Can anyone tell me what the numbers represent at the end of the date and time string in a PDF digital signature? My numbers looks like this:
Date: 2012.03.27 07:43:49 04'00' (Date = 2012.03.27 Time = 07:43:49 What is 04'00'?)
Thank you

Answered my own question. These numbers represent the time zone of the area where the digital signature was created.

How do I disable the digital signature feature in Reader and Pro XI

I am using Windows 7 and need to do it Enterprise wide

If it can be done (doubtful) there will be details in the Enterprise Deployment documentation. Enterprise Deployment (Acrobat and Reader)

Temporarily disable Digital Signature Checks to Install MS SQL Server 2008 with no Internet Access

I am attempting to install a licensed copy of MS SQL Server 2008 in a Private Enclave that does NOT have Internet access on a Win2008 R2 SP1 server (that is VM - thus I can't reboot and press F8 to select "Disable Driver Signature Enforcement"
). The installation fails with an error of the vc_red.cab file being found either corrupt or a bad digital signature. The file is good, but the signature has an expiration of 2011. I understand that a DOTNET SDK v1.1 program called setreg.exe
will enable disabling the digital signature check, but I am not permitted to use that program.
I might be permitted to use the "Signtool.exe" utility, but it is not clear what command sequences are necessary to disable and then re-enable the Digital Signature checks.
I saw a thread that recommended using the command:
bcdedit.exe /set nointegritychecks ON
However, the comments indicated that this might not have worked.
Are there Registry settings I can use with regedit to make the necessary changes to be able to install the application? I anticipate running into this problem with other software when I do not have Internet connectivity. I already tried
downloading the Microsoft CRL files; updated the lists on the Server; and rebooted. This did not solve my problem.

Hi,
As far as I know, it is not recommended to disable digital signature check.
Since we are not familair with installing MS SQL server, please also refer to SQL forums below to see if experts there have more insights regarding the matter.
https://social.technet.microsoft.com/Forums/sqlserver/en-US/home
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Disable Digital Signatures Completely

Hello,
My company is not yet on board with digital signatures, and occassionally people attempt to turn in their forms digitally (with digital signatures) when they should be turning them in on paper with hand written signatures.
I'm wondering if there is a way to disable electronic signatures when creating a document in Adobe LiveCycle. Right now the only option I have is writing text beneath the signature field saying, "Please don't use electronic signatures", and this isn't exactly ideal.
Thank you.

You can either remove the signature field from the form till it's implemented in your organization or modify the form to make the signature field as hidden/invisible.

Issue with multiple digital signatures disabling fast web view

Hello, I'm using acrobat 9.1 pro and have some questions regarding an issue using multiple signatures on a pdf.
Why am I asking the question below? My job involves preparing pdf's for submission to FDA. The FDA requires, among other things, that electronically submitted docs have fast web view enabled.
I am currently exploring ways of using digital signatures to sign pdf reports and still make sure they are FDA spec compliant. My issue involves a document that would have multiple signature fields. What I do is create at least two signature fields in the doc and then save and optimize while enabling fast web view. When I sign the first box and save, the file retains the fast web view status. Yet, when I apply and signatures past the first one, the file is subsequently set to fast web view off without any obvious way of turning it back on. I am confused as to why it gets disabled only after the second, and not right after even the first one was signed. And, of course, I would like to know if it is possible to maintain fast web view and how to do it. I'll gladly accept "tinkering under the hood" of the file suggestions if they exist as well.
Please let me know if anything is unclear or you need further information.
Thanks for your time and help.
~Vlad

Hi Vlad,
Michael actual had the correct answer. The purpose of a "Linearized" file (i.e. a file that has been Optimized for Fast Web View) is to get the first page to display as soon as possible so you can start reading without waiting for the rest of the file to download. As an aside, the designated first page doesn't necessarily have to be page 0 (PDF's use a zero based counting system for pages), but usually it is. To quote the PDF specification, "The primary focus of Linearized PDF is optimized viewing of read-only PDF documents. It is intended that the Linearized PDF be generated once and read many times. Incremental update is still permitted, but the resulting PDF is no longer linearized and subsequently is treated as ordinary PDF."
When you sign a PDF file the first time the Save process is a "full save", that is the entire document is rewritten so there are no more than two %%EOF (end-of-file) markers in it. The first EOF designates which page to show first and the second EOF designates the end of the rest of the file (so the browser knows when to stop downloading). However, when you add a second (or subsequent) signature the file is saved as an "incremental save" and all of the new data is tacked onto the the end of the original file. This is so you can do a rollback to the previous signed version and allows Acrobat/Reader to check the integrity of each signature independent of any other signatures. It's the incremental save that breaks the linearized optimization of the file.
Steve

How does the LiveCycle Digital Signatures work?

Hi,
I´m new working with liveCycle, and I would like to know how it works at technical level.
I have read documentation but I can not understand the procedure to generate the digital signature
I appreciate someone explain a bit about it or send a link to a page with detailed information.
Thank´s!

Your question is pretty broad...
What are you trying to achieve with your workflow? For example, do you want to...
Generate Digital Certificates (self-signed or otherwise)
Have end users digitally sign PDF document or forms (with Acrobat Pro or Reader)
Have the PDF document or forms digitally signed on the server side
Validate the digital signature on the client
Validate the digital signature on the server side
I have attached a document that should help as well.
Regards
Steve

I livecycle process verifies the validity of digital signatures

Hello, I have to create a process that I livecycle verify the validity of digital signatures in PDF format. can you help me?

hello thanks for the reply, I tried the process and works in part, the only problem in the variable verificationResult
process output tells me <identityStatus> UNKNOWN </ identityStatus> though I imported the certificate in to livecycle
how can I fix this?

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.

Disabling Digital Signatures

Hi,
Can anyone give me some solid evidence that disabling digital signatures on our 2003 network (for our 10 mac users) would be a good alternative? Right now we have 125 PC's and 10 Mac computers on our network using Active Directory.
I have also seen documentation regarding the issue of enabling digital signatures (if client agrees). Is there evidence or technical manuals at Microsoft's website that they agree that this is a secure alternative?
We have attempted to use AdmitMac to no avail.
-Kevin

This page on Microsoft's website should give you a fairly comprehensive overview of the policy and SMB clients.
http://support.microsoft.com/default.aspx?scid=kb;en-us;887429
If you deal with SOX or are a security conscious company then disabling this policy isn't recommended. You should look into a third party SMB solution such as "Dave" or "ADMitMac" from http://www.thursby.com or a third party AFP solution for your server such as "ExtremeZ-IP" from http://www.grouplogic.com.
Hope this helps! bill
1 GHz Powerbook G4 Mac OS X (10.4.7)

How to add the new Signature Filter to LiveCycle Digital Signatures?

I have been wrote my own plugin for Adobe Reader.
This plugin creates signatures by cryptoalgorithm "GOST R 34.10-2001" instead of RSA used in Reader and Livecycle.
As a result, I can't validate signatures created by my plugin in the LiveCycle Digital Signatures. In the log file of JBoss are written next:
"Unsupported signature filter detected: GostSignaturePlugin".
My question is how to install a support of my signature filter in to the LiveCycle Digital Signatures?
Is it possible to install my existing plugin for adobe reader into LiveSycle, or I must to write new plugin for LiveSycle?

Hello Jose,
Try making an entry in tables SMOFFILTAB and SMOFFILFLD.
This might help!
Best Regards,
Shanthala Kudva.

LiveCycle 8.0 Digital Signature shows Orange Flag ONLY IF Blank Form Has Submit or Email Button

My subject line says it all. After a lot of experimenting, including reinstalling Adobe Designer Standard 8.0, I have found that, in Adobe LiveCycle 8.0.1291.1.339988, my drag-and-dropped Document Signature Field will include a clickable orange flag ONLY IF the blank form I started with includes an E-mail button or Submit button. Strange but true. If you then delete these buttons, the orange clickable flag still appears fine.
Try it...
In Adobe Designer Standard 8.0 LiveCycle:
1. File > New.
2. Select Use a blank form, Next.
3. Next.
4. In Form Return Setup dialog box, DEselect Add an Email button and DEselect Add a print button (so that both are NOT checkmarked).
5. Click Finish.
6. Drag a Document Signature Field to the blank page.
7. Click PDF Review tab. Note that no orange clickable flag appears for the user then to be able to use for entering a digital signature.
Close the page.
Try a variation now that will work (yielding an orange clickable flag):
1. File > New.
2. Select Use a blank form, Next.
3. Next.
4. In Form Return Setup dialog box, SELECT either the Add an Email button OR the Add a print button (so that either IS checkmarked).
5. Click Finish.
6. Drag a Document Signature Field to the blank page.
7. Click PDF Review tab. Note that an orange clickable flag DOES appear this time for the user then to be able to use for entering a digital signature.
8. For further test, click the Design View tab and now DELETE the displayed button.
9. Click PDF Review. The flag is still there.
BOTTOM LINE: It at least looks like it's not just "Distribute forms" that requires that you have a button at Blank Form creation time. Also "Digital Signature" functionality requires that you display a button at Blank Form creation time -- which you can then delete.
A bug? Or do I have some major concept wrong -- maybe I'm mis-interpreting the whole Digital Signature concept and process?

Is this in the wrong forum? The problem I am having is with Acrobat's Distribution feature.
Shawn Gallagher
Program Specialist, Records Management, OSS
[email protected]
202-70(7-5595)
>>> MichaelKazlow <[email protected]> 2/18/2010 9:49 PM >>>
Please repost in the Designer forum.

Does LiveCycle Digital Signatures support unicode pkcs #12 file?

I used Adobe Acrobat and OpenSSL to generated a unicode pkcs#12 file. Import to the Windows are all correct. But when I used for LiveCycle Digital Signatures, after signed, the one use Acrobat generated pkcs12 file signed only can show ASCII character，and other one used OpenSSL pkcs12 file to signed,signature character changed to irrecognizable.

These are two unicode pkcs #12 files. one created by openssl, another one created by Acrobat.
I used this code to sign to the PDF file.
        try    {
            // This example will upload an XDP file to the LiveCycle Repository
            ServiceClientFactory myFactory = ServiceClientFactory.createInstance(LCCommonUtil.getConnectionProps());
            // Create a SignatureServiceClient object
            SignatureServiceClient signClient = new SignatureServiceClient(myFactory);
            // Specify a PDF document to sign
            FileInputStream fileInputStream = new FileInputStream(
                    "C:\\Applications\\pdfForms\\TestDigitalSign\\ConferenceReg_flatten_sf_added.pdf");
            Document credDoc = new Document(fileInputStream);
            // Specify the name of the signature field
            String fieldName = "SignatureField1";
            // Create a Credential object
            Credential myCred = Credential.getInstance("BLC_CHINA"); // LC Server: Local Credentials
             System.out.println("******"+myCred.getSpiName());
            // Specify the reason to sign the document
            String reason = "The document was reviewed";
            // Specify the location of the signer
            String location = "New York HQ";
            // Specify contact information
            String contactInfo = "Tony Blue";
            // Create a PDFSignatureAppearanceOptions object and show date information
            PDFSignatureAppearanceOptionSpec appear = new PDFSignatureAppearanceOptionSpec();
            appear.setShowDate(true);
            appear.setShowReason(true);
            // Set revocation checking to false
            java.lang.Boolean revCheck = new Boolean(false);
            // Create objects to pass to the sign method
            OCSPOptionSpec ocspSpec = new OCSPOptionSpec();
            CRLOptionSpec crlSpec = new CRLOptionSpec();
            TSPOptionSpec tspSpec = new TSPOptionSpec();
            // Sign the PDF document
            Document signedDoc = signClient.sign(
                credDoc,
                fieldName,
                myCred,
                HashAlgorithm.SHA1,
                reason,
                location,
                contactInfo,
                appear,
                revCheck,
                ocspSpec,
                crlSpec,
                tspSpec);
            // Save the signed PDF document
            File outFile = new File("C:\\ConferenceReg_flatten_signed.pdf");
            signedDoc.copyToFile(outFile);
        catch (Exception ee) {
            ee.printStackTrace();

Once a PDF is digitally signed, how to I disable the "Clear signature" option? I cannot allow appli

I need to set up digital signatures for a number of documents, but once signed, the signatures must be permenant. Currently the owner has the option (right clicking on the signature), to "clear signature" - how do I disable this?
Thanks in advance!

The point is that this is trivial to achieve for anyone, even if the file is locked after signing.
They just need to keep a copy of the unsigned file, delete the signed one, and replace it with the unsigned file. So such protection means nothing.
Repudiating signatures is a very bad thing, but it can only have real meaning if someone or some process knew about the signing. Otherwise, it's like someone signing a piece of paper, and destroying their signed copy without showing it to anyone; it's as if it never happened, and nothing was gained. If on the other hand a person has received the signed file, or a process has securely archived it, then removing a signature has no repudiating effect on the copy.
It can be hard to convert paper-based to electronic-based workflows where files can be freely duplicated, shared etc.
Clearly, though, if a person can sign a file, then others can act on that signature, and then the signer can still edit the original signed file, there is a big problem, not just of repudiation but of auditability.

Disabling a digital signature in LiveCycle

Similar Messages

Maybe you are looking for