Generated PDF using PdfEncryptionDetails does not have security other than password protected

We’re trying to set security for the PDF using the PdfEncryptionDetails. It works without issue with version 18.6, but any version after that does not work, other than password protecting, but the rest of security settings like no printing, no copying, etc do not work unless we use version 18.6. Our Aspose Words is licensed and installed.

@lnaranjo,

To ensure a timely and accurate response, please ZIP and attach the following resources here for testing:

  • Your simplified input Word document
  • Aspose.Words 19.8 generated output PDF document showing the undesired behavior
  • Your expected document showing the correct output. You can create expected document by using old version of Aspose.Words i.e. 18.6.
  • Please also create a standalone simple Console application (source code without compilation errors) that helps us to reproduce your current problem on our end and attach it here for testing. Please do not include Aspose.Words DLL files in it to reduce the file size.

As soon as you get these pieces of information ready, we will start investigation into your issue and provide you more information. Thanks for your cooperation.

AsposePDFPerm.zip (159.0 KB)
Hi, I’m attaching the different documents (we tried 18.6 and it works) as well as other versions, but included are test froms 19.8 JDK 1.6 and 1.7.
The password for all the PDF’s is admin.
Inside the TestAspose.zip file is the console app as well as the word document.
Also, we are using Acrobat Reader DC latest update available.
Let me know if you need anything else.

@lnaranjo,

We tested the scenario and have managed to reproduce the same problem on our end. For the sake of correction, we have logged this problem in our issue tracking system. The ID of this issue is WORDSNET-19141. We will further look into the details of this problem and will keep you updated on the status of correction. We apologize for your inconvenience.

1 Like

@lnaranjo,

Regarding WORDSNET-19141, we have completed the work on your issue and concluded to close this issue as ‘Not a Bug’. Please see the following analysis details:

This is expected behavior. The problem occurs because the owner password is not specified. Current code means that opening a document with user password also allows all operations. There was a bug with empty owner password which was fixed in 18.9 release. (see ‘Improved PDF encryption in Case when Owner Password is not Specified’ section of Aspose.Words for Java 18.9 Release Notes).