Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Read Only form fields are still editable by the signer(s)

Community Beginner ,
Nov 10, 2024 Nov 10, 2024

Hello,

 

I'm trying to prep a simple contract to be signed by my client(s). I created a signature field (for myself) that marks all form fields as "read only" except for the signature fields for the client(s). However, when I go through the prompts for the signature requests, the fields that were "locked" show up as being able to edit by "anyone".

 

I know I can use the "prefill" text tag to assign myself, but this created an extra step in the sending process where I have to click "Start" and then "Send". I'd like to avoid this, if possible.

 

Once I sign (before requesting signature), the read only form fields shouldn't be editable by the signer(s), correct? However, they still are. Is there a way around this without using the prefill text tag?

TOPICS
Create PDFs , How to , JavaScript , PDF , PDF forms
2.4K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
1 ACCEPTED SOLUTION
Advisor ,
Jan 10, 2025 Jan 10, 2025
LATEST

Using your test contract file I could reproduced the issue.

 

And the reason for the issue is simple, Adobe Acrobat Sign (at least if used via the Acrobat "Request e-signatures" tool) flattens existing digital signatures.

 

The field locking mechanism you employ essentially adds the information to the AcroForm signature field that once it is signed, the fields with the given names shall be considered locked.

 

But the Request e-signature / Acrobat Sign workflow starts by flattening that AcroForm signature field, i.e. it keeps just the appearance and throws away everything else, in particular the field locking information.

 

You can see that your signature (except the appearance) have been removed by clicking its visualization on the page. In your original file the Signature Validation Status dialog pops up. In the file versions you retrieved back from Adobe Sign it doesn't. Also you can see on the Acrobat Signatures panel that your signature now is missing and only a certification signature from Adobe Acrobat Sign is there.

 

Thus, the fields in the form shown to the client can be freely edited.

 

So when using Adobe Acrobat Sign, make sure that the PDF only contains fields for data the client shall be able to change. Furthermore, also consider including yourself in the Acrobat Sign signers instead of signing locally - as soon as you request e-signature, your former digital signatures are removed and only their visual representation remains and a historical remark on the audit report.

View solution in original post

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advisor ,
Nov 10, 2024 Nov 10, 2024

Which kind of signing by you and your clients are you talking about exactly? Do you mean signing using locally installed X.509 certificates? Or do you mean signing using the above Acrobat Sign service? 

And how exactly did you prepare the contact PDF? 

Can you share an example before and after you sign for analysis?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 11, 2024 Nov 11, 2024

Thank you for your reply. I use Acrobat Pro. I'm using locally installed certificates for my signature. I believe Acrobat uses the Sign service when it is sent for the client(s) signature (at least that's what i see on a properly executed contract).

 

See Attached screenshots. Hopefully this helps. As you can see, when I sign, the fields become read only except for the client signature fields. But when I go to request for signatures, they show as being editable by anyone.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Nov 11, 2024 Nov 11, 2024

Did you check that they are modifiable, by modifying them?

ABAMBO | Hard- and Software Engineer | Photographer
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 13, 2024 Nov 13, 2024

Hello,

 

Following up on this. Please see my reply below.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advisor ,
Nov 11, 2024 Nov 11, 2024
quote

I'm using locally installed certificates for my signature. I believe Acrobat uses the Sign service when it is sent for the client(s) signature (at least that's what i see on a properly executed contract).

 

Well, I don't know whether a mixed signing scenario (local certificate and remote Adobe Acrobat Sign) work together that well. I used to have the impression that they did not, but the last time I actually checked, is quite some time ago.

 

quote

See Attached screenshots. Hopefully this helps.

 

Unfortunately the screen shots do not help, the actual PDFs would be needed for a real analysis.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 11, 2024 Nov 11, 2024

To answer both questions:

 

Yes, I sent the contract to a test email and I was able to edit the fields as a signer.

 

See attached.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 10, 2025 Jan 10, 2025

Hi, Have you found a solution? I'm facing the same issue.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advisor ,
Jan 10, 2025 Jan 10, 2025
LATEST

Using your test contract file I could reproduced the issue.

 

And the reason for the issue is simple, Adobe Acrobat Sign (at least if used via the Acrobat "Request e-signatures" tool) flattens existing digital signatures.

 

The field locking mechanism you employ essentially adds the information to the AcroForm signature field that once it is signed, the fields with the given names shall be considered locked.

 

But the Request e-signature / Acrobat Sign workflow starts by flattening that AcroForm signature field, i.e. it keeps just the appearance and throws away everything else, in particular the field locking information.

 

You can see that your signature (except the appearance) have been removed by clicking its visualization on the page. In your original file the Signature Validation Status dialog pops up. In the file versions you retrieved back from Adobe Sign it doesn't. Also you can see on the Acrobat Signatures panel that your signature now is missing and only a certification signature from Adobe Acrobat Sign is there.

 

Thus, the fields in the form shown to the client can be freely edited.

 

So when using Adobe Acrobat Sign, make sure that the PDF only contains fields for data the client shall be able to change. Furthermore, also consider including yourself in the Acrobat Sign signers instead of signing locally - as soon as you request e-signature, your former digital signatures are removed and only their visual representation remains and a historical remark on the audit report.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines