Permissions with problem when encrypting pdf with certificate

Question

I am using the following javascript code to encrypt a pdf using a certificate:
                    var thePermissions = {
                         allowAll: false,
                         allowAccessibility: false,
                         allowContentExtraction: false,
                         allowChanges: "none",
                         allowPrinting: "none"
                     var theCertificate = security.importFromFile(
                         "Certificate",
                         "/c/user.cer"
                     var theUserEntity = {
                         firstName: "The",
                         lastName: "User",
                         fullName: "The User",
                         certificates: theCertificate,
                         defaultEncryptCert: theCertificate
                     var theGroup = { userEntities: [ theUserEntity ], permissions: thePermissions };
                     encryptForRecipients( { oGroups: [ theGroup ] } );
                    saveAs("encrypted.pdf");
The file "encrypted.pdf" resulting is in fact encrypted, but the permissions doesn't seem to be correct. For instance, the Document Properties show that there are no document restrictions (DocumentProperties.PNG), but when the details are shown, it seems that the correct restrictions apply (DocumentSecurity.PNG). As can be seen in the permissions variable, there should be no permissions to the pdf generated. Can someone possibly help me with this?
Additional info: there should have no human interaction in the process, the certificate is not fixed (preventing using encryptUsingPolicy), and will be selected based on the file name of the original pdf.

Answer 1

Hi Leonard,
I see the same thing executing the script from the JavaScript console. There is a slight wrinkle in the steps to reproduce. Even if everything worked as it's supposed to, you would still need to close and then reopen the file in order to get the perm restrictions to take effect. This is because when you initially encrypt the file you are still the document owner, and thus none of the perms have yet taken effect. However, once you do close and then reopen the file (thus forcing an authentication), the file should open with the perms being enforced, but alas, they are not.
Interestingly, if you go into the Document Properties and then select the Security tab (or just click the Permissions Details button in the DMB) you see that the Restriction Summary shows that everything is allowed, but when you click the Show Details button, which just displays the restrictions applicable to the encryption handler, it shows the correct settings. Of course the real bug isn't that the restriction summary is incorrect, but rather that it is correct and all of the supposedly restricted operations are allowable.
I'll enter this as a bug against 10 along with the ER to add the encryption algorithm as an option to the encryptForRecipients JS function.
Steve