Hello,
We are using Aspose Words engine to render docx files into images and displaying them on a web site. With many of the documents we use, the following happens:
When there is a digital signature in the document, it is shown as if the signature is invalid while the signature is valid. You know that the signature is valid by opening the word document and looking at the signature as Aspose to the image that is rendered by aspose.
The first image displays a word document with a signature when opened in word
The second document is a jpeg file rendered with aspose
Thanks for your inquiry. Could you please attach your input Word document here for testing? I will investigate the issue on my side and provide you more information.
Thank you for your quick reply.
I have attached the docx file as you requested.
After some more investigation, we found out that the aspose API returns with “signature is invalid” despite the fact that when you open it in word or use our own API for validation (CoSign SAPI) we get that the signature is in fact valid
I have attached the output Jpeg image file here for your reference. I used Aspose.Words for .NET 13.10.0 to generate this image file over a 64-bit Windows 7 machine on my side and DigitalSignature appears to be rendering correctly. However, I managed to capture following warnings i.e. related to importing signature during loading your Docx in Aspose.Words’ DOM.
UnexpectedContentCategory: Import of element ‘SignatureMethod’ is not supported by Aspose.Words. UnexpectedContentCategory: Import of element ‘SignatureValue’ is not supported by Aspose.Words. UnexpectedContentCategory: Import of element ‘SignatureProviderId’ is not supported by Aspose.Words. UnexpectedContentCategory: Import of element ‘SignatureProviderUrl’ is not supported by Aspose.Words. UnexpectedContentCategory: Import of element ‘SignatureProviderDetails’ is not supported by Aspose.Words.
I have logged this issue in our bug tracking system. The ID of this issue is WORDSNET-9274 and your request has also been linked to it. Our development team will further look into the details of this problem and we will keep you updated on the status of correction. We apologize for any inconvenience.
Thank you for being patient. The latest version of Aspose.Words renders attached “Miller In1.docx” exactly as Microsoft Word does. Moreover, the Document.DigitalSignatures property indicates that the signature is valid. Could you please confirm if you attached the correct input document as the attached screenshots are not correspond to attached DOCX file? Please provide the correct document and source code to investigate this issue further. Thanks for your cooperation.
Thanks for your inquiry. I tested the scenario and have managed to reproduce the same problem on my side during rendering this document to PDF or image formats. For the sake of correction, I have logged this problem in our issue tracking system as WORDSNET-9427. Our development team will further look into the details of this problem and we will keep you updated on the status of correction. We apologize for your inconvenience.