![]() To prevent confusing our users, our default UI does not show the integrity status of a document if the certificate validation failed (that is, if the general signature status is “error”).īelow is the validation UI that is shown when the certificate is not self-signed or hasn’t expired but is not yet trusted by PSPDFKit. In this case, we are informed that the certificate is not valid because it has expired. This is not necessarily bad, but we find out about this situation with a severity level of “warning.”īelow we can see what happens if we try to validate a signature with an expired certificate. Finally, the UI lets us know that the certificate used for signing was a self-signed certificate. In this case, the document has not been modified since it was signed, which is a good sign. Following that paragraph, the integrity status of the document is displayed. This information always comes from the certificate itself, so you don’t have programmatic access to modify it. Next, the signer name and signing date is shown. In this sample case, the first paragraph informs us of the general status of the digital signature. Let’s take a look at our validation UI when the document is signed with a self-signed certificate: If coversEntireDocument returns false, it means the digital signature only covers a particular revision of the document - that is, there may be subsequent revisions covered by digital signatures that were applied later on. Additionally, the coversEntireDocument Boolean property is useful if the document has many digital signatures. Programmatically, the PDFSignatureStatus class contains a property, signatureIntegrityStatus, that can be queried to determine if the document was altered in some way after it was digitally signed. If you validate a digital signature with PSPDFKit, either programmatically or using our UI, there can be several possible statuses for the signature. This can be very useful for the topic that comes next. PSPDFSignatureValidator *validator = initWithSignatureFormElement:signatureFormElement] Let status = try validator.verifySignature(withTrustedCertificates: certificates) let validator = PDFSignatureValidator(signatureFormElement: signatureFormElement) Let us know how it goes and share your findings.// Validate the signed document. ![]() You can also refer to the Adobe article Validating digital signatures, Adobe Acrobat This identifies the owner of the digital certificate that has been used when signing the document.ĥ) Mark the certification path, click the 'Trust' tab and then 'Add to Trusted Identities'.Ħ) Answer 'OK' to any security question that follows.ħ) Check the field for 'Use this certificate as a trusted root' and click 'OK' twice to close this and the next window.Ĩ) Click 'Validate Signature' to execute the validation. You may try the following steps and see if this helps:ġ) Right-click on the ‘validity unknown’ icon and click on ‘Validate Signature’.Ģ) You will get the signature validation status window, click on ‘Signature Properties’.Ĥ) Verify that there is a certification path. Is it specific to one PDF file or with all the PDF files? Is it a Mac or Windows machine and what is the version of operating system installed? What is the dot version of Adobe Reader installed? To identify refer to Identify the product and its version for Acrobat and Reader DC Is it possible to post a screenshot of the error message you get? To share the screenshot, refer to the steps mentioned in the article Additional status details appear in the Signatures panel and in the Signature Properties dialog box. When Digital Signatures are validated, an icon appears in the document message bar to indicate the signature status. As per the description above, I can understand that you are not able to validate a signature in a PDF file, Is that correct?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |