This post deleted (was previously a bug report, but there is no bug).
Sorry, I read an old error from the error log.

I have tested the following:

1. Lock editing, copying, etc with ownerPassword
2. Lock pdf with password
3. Sign pdf with self signed cert, pdfSign
4. Sign with pdfSign AND lock with ownerPassword
5. Sign wiht pdfSign AND lock with ownerPassword AND protect with password

Everything works in various combinations.

Great work, Jan!

edit: all tests where done via the API, i.e. I have not tried to do this from within Studio.

Great Jan!
I will try this tomorrow. I'm preparing a big update, so my dev-environment is not ready for other stuff right now.

It works great. Any chance there will be a 2.11 with this fix included before 3.0? I have the npm install in my dockerfile, so it's ok. But I'd rather use an official 2.11 for production.

Wow, that was fast!
I'm relieved that this was fixable on your side. This was the most important functionality to me between pdfSign and pdfPassword. It will be nice when the underlying pdfSign problem gets solved as well, but I won't need it for now.

I don't know which format you should supply, but if it should only be the actual base64 data you need to remove the initial properties.

Try this: yourString.replace(/^data:image\/\w+;base64,/, '');

Ok, that's a pity. It seemed to be a perfect match between the problem and the fix.

Is this a bug in the node-signpdf package? It seems like jsreport uses a really old version of this package (0.3.0). Current version is 1.3.2, in which exactly this bug seems to be fixed.

https://github.com/vbuch/node-signpdf/issues/98

N.B. This might be completely inaccurate, and I might have misunderstood something.

Update:
This seems to be an encryption problem.

If I supply either pdfPassword.password or pdfPassword.ownerPassword, I get this rubbish TOC.

I'm building TOCs in my PDFs in accordance with the playground sample. Everything works great, but I just discovered that the TOC in Chrome and Acrobat shows rubbish.

This was not the case some time ago. I don't often look at this TOC so I cannot tel when it happened. Could it be linked to the font problem I had before? This was solved by adding the following to the CSS:

.jsreport-pdf-utils-page-item {
   font-family: Helvetica
}

.jsreport-pdf-utils-page-group {
  font-family: Helvetica
}

Here is the font problem-thread
https://forum.jsreport.net/topic/1731/intermittent-in-2-10-error-while-executing-pdf-utils-operations-root-pdf-pages-i-items-seems-to-be-undefined/8