I’ve installed Okular on my windows 10 and wanted to sign it digitally. Okular could not detect my installed certificate, so I tried to point the path manually. Microsoft website suggests that it is at %SystemRoot%\System32\Certlog with an extension of .edb but there was no folder named certlog.
From what I understand Okular uses Poppler library to sign pdfs but from my regular search it seems that windows is not officially supported. Does Okular use unofficial build of Poppler for windows or it just doesn’t support it at all ?
I’m also trying to sign a pdf on windows, can’t seem to figure it out. I tried exporting the certificates from Firefox and puting them in a folder and setting Okular backend to point to the folder, but it doesn’t detect them.
I don’t have possibility to put links, so quote my post from another thread:
I found next way to use Okular for Windows to sign pdfs:
You need to have certificate in *.pfx format. Depending on your specific situation (need to convert existing certificate or create a new one via PowerShell), the easiest way is to ask AI for detailed “how-to” guide. I used perplexity for guidance of creation self-signed certificate using PowerShell.
Okular reads certificates from an NSS database (used by Firefox or Thunderbird), not directly from PFX files or Windows certificate stores. It expects certificates to be imported into the NSS database prior you can see them in Okular. I was unsuccessful to connect Okular to Firefox NSS certificates database, but successful with Thunderbird. You can also ask AI how to create NSS database if you don’t use Thunderbird.
After steps 1 and 2 you point Okular to your NSS-database and you see available certificates. You can place digital signature into pdf. The big con is that there are NO any possibility to change visual appearance of signature, just use it as is. I tried to use background picture for digital signature (like in Acrobat or any other advanced pdf editors), but it disappears exactly after finishing signature. As this behavior is same in three different builds for Windows (which I tested), we can only be content with what we have - a poor text signature without any way to change it.