Do you have an issue with a specific file(s)? No
Can you reproduce using one of our samples or online demos? Yes
Are you using the WebViewer server? No
Does the issue only happen on certain browsers? No
Is your issue related to a front-end framework? No
Is your issue related to annotations? No
One contains a signature with unknown validity, which Adobe Acrobat displays with a yellow warning icon.
The other contains corrupted digital signatures, which Acrobat displays with a red cross indicating the signature is invalid.
However, when I upload both PDFs to your WebViewer demo, they both show the same yellow status icon, and I am unable to tell which one has an unverifiable signature and which one has corrupted signatures.
In my own implementation using WebViewer, I’m calling:
await doc.verifySignedDigitalSignatures(opts);
However, for both PDFs, the returned status is always:
Hello, I’m AiRon, an automated tech support bot While you wait for one of our customer support representatives, I can help you with your question.
It seems you are facing difficulties in distinguishing between corrupted and unverifiable digital signatures using WebViewer. WebViewer’s current capabilities may not fully distinguish these subtle differences in signature validity status as Adobe Acrobat does, particularly when it comes to differentiating between a signature that is untrusted due to unknown validity and one that is corrupted.
Some things you can try:
Use the verifySignedDigitalSignatures method to get detailed information about each signature’s status. While it may return a status of e_untrusted, you can further inspect the signature object for additional details.
Check if there are any specific error messages or warnings provided by the verifySignedDigitalSignatures method that might offer more insight into the signature’s state.
Consider implementing additional logic to handle different signature verification statuses based on specific requirements or use cases.
I’m following up on my ticket regarding digital signature validation in WebViewer. I’ve received the automated response, but I’d appreciate any further input from your support team.
Additionally, could you please advise how to enable the panel that displays signature validity (as shown in your demo)? If available, an Angular example or code snippet would be very helpful.
In the above guide, we discuss verification statues similar to the ones you described, such as untrusted, unsupported, and verified. Additionally, if you want a more detailed sample of how we can verify Digital Signatures, you can find our sample code here: https://docs.apryse.com/web/samples/digitalsignaturestest
What options are you passing into the verifySignedDigitalSignatures() API call? The untrusted verification status is returned whenever WebViewer could not verify trust for at least one signature, but you can likely avoid this status by setting current VerificationOptions. You can find the VerficiationOptions you can configure here: https://sdk.apryse.com/api/web/Core.PDFNet.VerificationOptions.html
Best Regards,
Jacob Romano Carlsen
Web Development Support Engineer Apryse Software Inc.
