I have a gift certificate pdf that I have created with editable fields using the prepare form tool.
I wish to use this document to email gift certifictes to customes.
I have a Value field, Name, From & Date.
How do I use this .pdf as a form with custom details entered & then send it as a a falttened pdf without editable content?
The resulting gift certificate needs to be 100% secure so no fields can be edited.
Is there also a way to limit how many times it can be printed?
I have Adobe DC, and today for the first time, the image of my signature does not appear when I choose fill and sign. In fact, nothing appears. There is just a spinning circle like something is trying to load. Is there a link or something that I need to fix?
Hello,
I have many documents each day that I have to sign, in the past i've used Nitro Pro to quicksign these with a image file of my signature - and no password.
I can't seem to make this work with acrobat.
I saved my signature in the fill and sign section, but it doesn't come up when I click there again - it either asks me to upload a file or it has the spinning wheel loading.
The times i've gotten it to work, it then won't save the file (it makes me save as a new file).
Then I tried to use digital id - but this prompted me to input a password every time I sign, which takes to long and is security overkill.
So to distill my question right down, where is Adobe Acrobat's version of the "Place Signature" button that Adobe Reader has?
Thanks!
更新する前に確認にチェックを入れ、今すぐ更新をクリックしても、証明書が更新されません。
adobeReaderを再インストールしても結果は同じです。ＯＳは、windows10です。
My laptop recently did an update to arobat reader dc and now I am unable to digitally sign forms. Can I go back to a previous version?
Hello,
The recent flash update appeared with a weird process chain in our antivirus, it shows the initial signed installer calling an unsigned install which then scrapes LSASS memory. Is this normally the process that Flash should be installing with?
The antivirus shows the execution chain as:
CMD: FlashPlayerInstaller.exe -install -iv 9 VirusTotal
CMD: "C:\WINDOWS\system32\Macromed\Temp\{ED9F96DB-0F7C-4FE6-8D3E-DC481E02E23A}\InstallFlashPla yer.exe" -install -skipARPEntry -iv 9 -au 4294967295
VirusTotal (unsigned)
Reads LSASS memory VirusTotal
Thanks!
I have a long list of ancient documents sent for signature. I want to clean out the list. How do I do that? Acrobat Pro DC, Mac 10.12.6
I have a PDF form with a few buttons (ie. Print, Clear, Submit). Whenever I use the "Fill & Sign" utility to add my signature then save the document I am no longer able to utilize the buttons. I can see the need to disable editing the document after it has been signed but I do not see the need for disabling buttons. Is there anything I can do?
Hola, Adobe no es capaz de verificar correctamente las firmas con el DNIe Español. Una firma válida la indica como "Certificado no válido para utilizarse".
Cómo hace Adobe la interpretación de la RFC 5280 para que no se muestre la firma como válida?
La tarjeta de Identificación de los españoles con capacidad de autenticación y firma digital la tienen 40 millones de Españoles y Adobe no valida correctamente las firmas.
Muchas gracias,
Juan
Hello, Adobe is not able to correctly verify the signatures with the DNIe. A valid signature indicates it as "Certificate not valid for use".
How does Adobe interpret RFC 5280 so that the signature is not shown as valid?
The Spanish ID card with authentication capacity and digital signature has 40 million Spaniards and Adobe does not correctly validate the signatures.
Thank you very much,
Juan
Hi,
Hope this is the right place to post...
I am trying to sign PDF documents with my newly issued Hong Kong Post e-Cert Digital Certificate.
This is in Acrobat Reader XI (11.0.07) on Windows.
I can sign the document OK - but when I review the "Signature pane" I see that the Signature is invalid:
Looking at the Signature properties I can see the following:
The chain of the Signature is:
- Hongkong Post Root CA 1
- Hongkong Post e-Cert CA 1 - 10
- WILSON Matthew James - my certificate
The Root and next level are trusted:
The error is "The selected certificate path has errors: Invalid policy constraint"
This certificate seems to have a policy:
Where as the Next Level and my certificate do not:
Is this the cause of the issue?
If so - is this something the issuing CA needs to sort out - i.e. Hong Kong Post or is a local configuration issue?
Many Thanks
Matthew
How do I remove a stored signature? Although I have used the stored image of my signature, most of the documents I sign for the organization I work for I just type in my name.
I removed my stored signature image from it's previously used file location on my computer. Today I signed a document and suddenly the image of my signature pops into the field. It's never automatically filled in the signature field, if I wanted to use it I had to go get it.
I have not intentionally stored the image of my signature anywhere in Adobe Acrobat, Reader or Cloud nor can I find it in any of those apps. I will no longer be working with this organization soon and don't want my signature available for anyone else to use.
Thank you,
Kelley C
We send locked pdf documents to clients for manual signing. They in turn, return a scanned version of the manually signed document to us. From there, I will need to send it to our CEO for electronic signing (therefore he would be receiving an email of a scanned PDF, not an original, for him to sign electronically). Can Adobe do this? If so, how? And while I have pro, the CEO does not - would he need pro?
i can no longer digitally sign - when i select certificate, digitally sign, signature, and input password the "Sign" button stays grayed out. Never had this probolem before; help!
When I'm signing a PDF and click on the signature field. DC returns a Black Translucent Screen and locks up DC. I must go to Task Manager to end the task
Richie
Hi,
We want our documents to be LTV-enabled, as they currently show the "Signature is not LTV enabled and will expire after ..." message.
As I understand, the requirement to have an LTV-enabled PDF is that it needs to contain all the necessary revocation information inside the signature PKCS7 itself. That means either the CRLs or the OCSP responses for all non-root certificates. For various reasons we want to embed the OCSP responses without using DSS.
To achieve that, we build the OCSP request with all the certificates in the chain except for the root, and embed the response in the PKCS7.
OCSP Request Data:
Version: 1 (0x0)
Requestor List:
Certificate ID:
Hash Algorithm: sha1
Issuer Name Hash: 1BCC2117979CDF874B9088E8A378DF36121CEBEA
Issuer Key Hash: 3A6E6518E756D2E4F32DDDA57C726DFF30E18627
Serial Number: 753007D08019634DB9
Certificate ID:
Hash Algorithm: sha1
Issuer Name Hash: BB14B271438F3E200C0D15A3D475FEEBE109EE3F
Issuer Key Hash: B76A026D2CD9B036B32B6C05AA345E06EDB2B99B
Serial Number: 8C6A45F533AA3746
Certificate ID:
Hash Algorithm: sha1
Issuer Name Hash: 0CD7FC8124202E8D338840FB507B9D3DE46DB768
Issuer Key Hash: E89BCD7E86629B7A4D8C00973985CF1C7890703A
Serial Number: 26F4AA13F0560872
Request Extensions:
OCSP Nonce:
041088AF2BC66C7E3F4FC78B11004B7A5294
And the response shows:
OCSP Response Data:
OCSP Response Status: successful (0x0)
Response Type: Basic OCSP Response
Version: 1 (0x0)
Responder Id: 67233203D98339EA9C94F22A7EA665B9B1F2A309
Produced At: Dec 11 15:09:55 2018 GMT
Responses:
Certificate ID:
Hash Algorithm: sha1
Issuer Name Hash: 1BCC2117979CDF874B9088E8A378DF36121CEBEA
Issuer Key Hash: 3A6E6518E756D2E4F32DDDA57C726DFF30E18627
Serial Number: 753007D08019634DB9
Cert Status: good
This Update: Dec 11 15:09:55 2018 GMT
Next Update: Dec 12 15:09:54 2018 GMT
Certificate ID:
Hash Algorithm: sha1
Issuer Name Hash: BB14B271438F3E200C0D15A3D475FEEBE109EE3F
Issuer Key Hash: B76A026D2CD9B036B32B6C05AA345E06EDB2B99B
Serial Number: 8C6A45F533AA3746
Cert Status: good
This Update: Dec 11 15:09:55 2018 GMT
Next Update: Dec 12 15:09:54 2018 GMT
Certificate ID:
Hash Algorithm: sha1
Issuer Name Hash: 0CD7FC8124202E8D338840FB507B9D3DE46DB768
Issuer Key Hash: E89BCD7E86629B7A4D8C00973985CF1C7890703A
Serial Number: 26F4AA13F0560872
Cert Status: good
This Update: Dec 11 15:09:55 2018 GMT
Next Update: Dec 21 15:09:54 2018 GMT
Response Extensions:
OCSP Nonce:
041088AF2BC66C7E3F4FC78B11004B7A5294
Signature Algorithm: sha256WithRSAEncryption
45:88:53:31:2d:8a:7d:32:84:14:1f:33:4e:9f:db:a2:be:7e:
2b:b3:e9:90:39:7c:24:d4:89:ea:2d:34:5c:6b:80:7e:3b:d6:
d1:0c:7a:d9:bd:55:f3:a3:a2:ba:0a:83:ad:42:fe:48:f8:8a:
77:24:9c:9b:db:ec:25:13:dc:a7:74:fe:e5:8b:8d:b0:3d:cb:
11:74:2d:6a:c0:9f:96:f5:c4:dd:b2:44:57:96:0a:ed:22:4f:
9c:53:b0:ac:96:d8:84:69:3e:65:02:1b:f8:63:11:f9:07:3c:
08:d0:e4:28:70:d5:ca:a4:8f:7c:30:6e:d1:f1:47:e0:15:1f:
44:bc:d6:1f:26:54:27:b4:b4:06:08:1f:03:66:bc:e0:e1:a1:
b0:f3:b1:6d:55:b9:c0:40:5e:83:33:65:d4:89:82:05:1b:0b:
4e:fa:2d:13:a5:c3:95:f8:db:6d:2b:cc:97:eb:7a:29:5e:60:
12:f2:42:f2:96:ce:03:96:ea:6e:5c:41:d3:28:49:e3:10:c4:
f5:47:5f:0b:b2:b8:ac:16:43:ee:27:d0:b2:a7:92:de:78:26:
7d:25:ec:93:8f:79:66:b3:09:e0:dd:71:ab:9a:f2:67:0b:c4:
b8:e8:5e:f1:ae:70:b3:29:42:dc:f1:61:bc:7b:83:e4:24:44:
28:b0:df:29
Which matches with the three levels (excluding the root) for the certificate used. When opening the signature a message appears saying "Signature is not LTV enabled and will expire after 2020/08/05 14:33:03 +01'00'".
As expected under the Revocation tab for the root certificate the message shown is "The selected certificate is either a trust anchor or is a certificate above the trust anchor in the certificate chain (...). No revocation checks are done for such certificates, they are inherently considered trustworthy.", and the certificate at 0+1 says "as verified using the Online Certificate Status Protocol (OCSP) response that was embedded in the signature". The problem seems to be with the other two certificates below that one, that are seemingly not embedded and their details show "as verified using the Online Certificate Status Protocol (OCSP) response that is contained in the local cache", which should be the reason as to why the document is not LTV enabled for Adobe.
Extracting the /Sig node shows, again, that the OCSP response containing information for the three certificates is available.
Looking at section 3.4 of the Acrobat Security Administration Guide https://www.adobe.com/content/dam/acom/en/devnet/acrobat/pdfs/acrobat_security_admin_90.pd f the procedure is to first check the signature looking for the OCSP, so using the local cache means it was not found in the signature.
Also as suggested inadd revocation info (ocsp response) in the signatures lack of the nextUpdate field could also be a reason, but it is present for the three responses.
I have uploaded a sample pdf here Dropbox - file.pdf , thank you.
Hey guys,
Can anybody tell me how to fix this?
When I'm trying to sign a PDF file all Acrobat DC is doing is show me the Adobe User Account and it won't let me sign it, I'm signed in with my Adobe ID and that page is showing me the Adobe user's info and nothing else happens after that.
I have already uninstalled and re-installed Acrobat DC, this is happening in a Mac OS X High Sierra (10.13.6)
Thanks.
I have a certification form that needs to be signed by whatever operator filled the form out. Each operator has a Digital ID file that they select and it adds the signature to the document in the signature form. For some reason all of the signatures now have the same hand drawn signature on every Digital ID regardless of the user selected one. If you click one of the digital signatures and click "Create" then select "Draw" it will allow you to draw a new one, which will then copy over to all of the individual ID's again.
Each user has their own password for their signature, and each signature is a separate file. Additionally, I tried copying them back and fourth between other PC's in different orders and now it's affecting multiple PC's.
No clue how to fix this as I've tried deleting all of the signatures, restarting Adobe Acrobat and Reader, then creating all new ones. Each time I create a new Digital ID from a blank canvas, it still pulls up an old drawn signature.
I'm using Adobe Acrobat DC and Adobe Reader DC to test this.
I'm having the following error when I try and send an Adobe Sign document through Acrobat:
Error text is forbidden- The operation cannot be completed. Please try again later.
I recently updated my login credentials.
So I have Logged out, closed software and restarted. Same.
Also Adobe Sign gives the following message: We have encountered an issue due to possible Adobe Id change. Please contact your IT administrator or Adobe support.
I have also opened a Customer support chat window and waited for an hour and a half for someone to help me. Zzzzzz.
Your case number: ADB-4946776-K4S0
I am attempting to edit a document (that I initiated) and I'm told the document is protected and I need to enter a Permissions Password to proceed.
Can you help me?
