Odt sign bug

Aspose.Words Product Family
1

Hello,
When I set OdtSaveOptions.DigitalSignatureDetails = New Words.Saving.DigitalSignatureDetails(crtHolder, sgnOptions)

my DigitalSignatures.SignOptions is
.XmlDsigLevel = XAdEsEpes or XmlDSig will not make a difference in odt files?
.ApplicationVersion = “16.0”
.WindowsVersion = “10.0”
.OfficeVersion = “16.0”
.HorizontalResolution = 1920
.VerticalResolution = 1080
.ColorDepth = 32

and open the saved .oft file LibreOffice I see this error, please advise.

1127×774 42.8 KB

2

@australian.dev.nerds
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): WORDSNET-29370

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

1 Like
3

Thanks for the case ID.

4

@australian.dev.nerds I looked through the code and it looks like the property is applicable only for OOXML format. I created a task (WORDSNET-29373) to clearly describe this in the documentation to avoid confusion on the future.

1 Like
5

Thanks, currently no way to save as ODF v1.2? If no, will this add an odt version property to odtsaveoptions?

6

@australian.dev.nerds As I can see ODT produced by Aspose.Words already have 1.2 version:

<office:document-meta office:version="1.2" xmlns:office="urn:oasis:names:tc:opendocument:xmlns:office:1.0" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:ooo="http://openoffice.org/2004/office" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:meta="urn:oasis:names:tc:opendocument:xmlns:meta:1.0">

But we will consider adding a property to explicitly specify version in save options. We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): WORDSNET-29376

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

7

Thanks, so maybe the error says that signature is in v1.1 format :slightly_smiling_face:

8

@australian.dev.nerds Thank you for your hint. We will investigate the problems and keep you updated.