Adobe LiveCycle (Archived)

Report · 7/8/09

[Thread Edited By Adobe]

/*Don’t forget to meet and greet your fellow peers virtually by telling them about yourself here.

Go ahead and to it now: https://adobe.ly/3eDnB4v */

Actual Question:

Hi all, I have a question relating to the topic above that i hope
you guys can help me with;

1) Is it possible to remove digital signatures from form? For instance
if you have a form going thru several approval steps that requires
signatures, and then one step happened to reject, it would be nice to
remove the previous signatures so that they could be re-signed.

2) And finally is there a simpler way to combine digital signatures
and rights management then what was listed in the pdf provided by
Duane (second post from the bottom of the thread)? When creating a policy there is

a checkbox for "Filling in form fields and signing". Is this forsomething else?

Thanks!
Billy

Report · 7/8/09

1) Is it possible to remove digital signatures from form?

ANSWER: A signature can only be removed ("unsigned") if the system or user has access to the "private" key used to generate the signature in the first place. For example, let's say User A signs a PDF... Only User A can unsign that PDF. If you were to use LC Digital Signatures ES to "unsign" a PDF, you would need to have all of the potential user "Credentials" and Credential passwords stored in the Trust Store so LC would have access to the private keys to be able to unsign a signature field. This is not very feasable if the number of potential signers is large.

2) Is there a simpler way to combine digital signatures and rights management

ANSWER: Combining Digital Signature and Rights Management is not complicated. You just need to be aware of the "Order of Operations" required. Always "Encrypt" first (Rights Mgt, Certificates, and Password can be used for encryption) then "Certify" (assuming you are Certifying the PDF), then add Reader Extension rights (assuming you want to extend functionality of the document for Reader)

The reason the above order is required... When you sign a document, a hash is generated based on the document, if you then encrypt that signed document, you are modifying the document which in turn causes a different hash to be generated... this breaks the signature.

As for the "Filling in form fields and signing" option in a policy, this is a "permission" that you can allow or disallow for PDF forms with a policy applied by RM. For example, A PDF has a policy applied where User A has the "Filling in form fields and signing" permission enabled andf User B does not. User A can open the form and interact with it by filling it in and or sign the form. User B would only be able to "view" the form. This permission is only relevant what using RM to protect fillable PDF forms. Also, it shouldn't be confused with the Reader Extensions permission of allowing Digital Signatures in Reader.

For example, If you wanted a "Certified" form to be filled in and signed by User A with Adobe Reader, you would need to:

Apply a policy to the PDF where User A had the "Filling in form fields and signing" permission enabled, then apply a "Certify" signature which had the "Allow Form Fill and Signing" permission enabled, then Reader Extend the PDF form that enables the "Digital Signatures" permission which activates the Digfital Signatures functionality in Reader for that particular form.

It may sound complicated, but it really isn't

Regards

Steve

View solution in original post

Report · 7/22/09

Sure thing, i've included a couple of screenshots;

Report · 7/22/09

Billy

I was actually looking for the specific permissions for "glennj"... see attached screen shot for the screen I was referring to. The user in the screen shot is the account I use to run the "RemovePolicyandClearSignature" process.

Make sure the "glennj" user has the "Modify" permission eanbled.

Thanks

Steve

Report · 7/22/09

I didn't have modify checked off, i had collaborate instead. Just wondering why you can only select one and not the other?

Either way, i changed it around and its still a no go, it stalls at the unlockPDF

Report · 7/22/09

Billy

The "collaborate" permission is a subset of the "Modifiy" permission. If "Modify" is enabled, "collaborate" will also be enabled.

I'm not sure why you are experiencing the error still. As I have stated before, everything looks ok, and I am able to get it to work in my environment.

At this point, a few things I would try are:

Test with a different\new policy and policy set

Create a new user that will be used exclusively as the "Run As" account

Recreate the "RemovePolicyAndClearSignature" process from scratch and test it with your other processes

Regards

Steve

Report · 7/22/09

Ya, i'll try and reabuild everything from scratch. Thanks again for all your help, i'll let you know how it goes

Billy

Report · 7/23/09

Hi Steve, just to give you an update, it seemed that it was the user domain that was causing the problem. I tried just using the defaultDom and there were no complaints. Not sure why it didn't like the domain tho, any ideas?

Thanks,

Billy

Report · 7/23/09

Billy

Does the user "glennj" happen to exist in both domains (DefaultDom and the one you were using previously)?

Steve

Report · 7/23/09

I believe at one point he did, but then again there were times where the user was exclusive (ie in onee group but not the other) and the issue was still there. There isn't a minimum number of characters or other domain restriction is there?

Billy

Report · 7/23/09

Billy

A user can be in multiple "groups" in that same domain, but a user should not be duplicated in multiple "domains" If a user is duplicated across domains, LiveCycle will simply find the first instance one and stop looking.

I'm not aware of any restrictions around minimum number of characters etc...

Steve

billstu · 2/22/16

hello ... im new to Adobe signature management and i have a question ... i have PDFs forms on iPads with Adobe Reader for filling and signing documents ... Field employees fill out visit forms and have them signed for acknowledgment ... after form has been signed and saved in reader's local folder ... is there a way to remove signatures from that file but leave remaining field content in place for a new signature at a later date so form can be used like a custom template ... I hope i explained this correctly ... thanks

Report · 12/28/16

1. open file in NitroPDF (U may use Acrobat, but the bookmarks will automatically be lost with Acrobat, but preserved by NitroPDF)

2. Select all pages and click Edit>Extract then select Extract selection

3. Save the resulting "Untitled" file with any name you like eg "Originalfilename"_Extracted.pdf. U have now removed the digital signature!

4. If the file contains "Form Fields" that U wish to remove then...

5. Open the resulting file in step 3 above, in Acrobat

6. Go to "Tool Sets" and select "Forms", then click "Edit Form"

7. A list will show up with something like Preflight. Right click it and select "Remove", then remove anything else that is removable

8. Save your file

9. Now your file is free of both the digital signature and the form fields!

dwightdgodwin · 6/22/17

My question is HOW

I have a document I created and signed. I want to remove the signature because I can't edit it with it signed.

I just can not figure out HOW to remove my signature. I have even done a Save As to try to create a new document, but the signature travels with it.

Hope you can help.

Adobe LiveCycle (Archived)

Removing signatures in a digital signature field

Learn

Documentation

Events

Community

Support

Resources

Adobe account

Adobe