Created attachment 165760 [details] Screenshot SUMMARY The "Digital Sign" function, present in the "Tools" menu, does not work in Okular installed via Microsoft Store, even with my token, respective drivers, and my digital certificate regularly installed on the machine. STEPS TO REPRODUCE 1. I insert my physical cryptographic key into any USB port on my computer. 2. I open any file in PDF format and Okular opens normally. 2. At the top of Okular, I select the "Tools" menu and then click on the "Digitally Sign..." function. OBSERVED RESULT Okular returns the following error message: "There are no available signing certificates. For more information, please see the section about Adding Digital Signatures in the manual.". EXPECTED RESULT That Okular recognizes the token and its respective digital certificate installed on the machine, allowing you to digitally sign documents in PDF format or any other supported format. SOFTWARE/OS VERSIONS Windows: Windows 11 23H2 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Version 5.109.0. Qt Version: Version 5.15.10 (compiled with 5.15.10). ADDITIONAL INFORMATION
Have you read the manual?
(In reply to Albert Astals Cid from comment #1) > Have you read the manual? Yes, but the opened man page only shows when a PDF document containing an embedded digital signature is opened, a function that works perfectly (https://docs.kde.org/stable5/pt_BR/okular/okular/signatures.html ).
Arg, the pt_BR version is outdated and doesn't have the additional section, please see the one in english https://docs.kde.org/stable5/en/okular/okular/signatures.html#adding_digital_signatures
(In reply to Albert Astals Cid from comment #3) > Arg, the pt_BR version is outdated and doesn't have the additional section, > please see the one in english > https://docs.kde.org/stable5/en/okular/okular/signatures. > html#adding_digital_signatures From what I understand, and I ask you to correct me if I'm wrong, the documentation indicated, in the English language, seems to be aimed at Linux distributions, since the manual mentions that Okular will look for the certificates, firstly, in the current Firefox folder (Note: I'm using Firefox from the Microsoft Store), secondly, in the system's "/etc/pki/nssdb" directory and, thirdly and finally, in the current user's "$HOME/ .pki/nssdb" folder. I tried configure Okular to look for certificates in the Firefox profile directory, but the directory shown in Firefox itself (via Microsoft Store), in the "about:profiles" tab, does not exist, not even hidden, in the "AppData\Roaming" folder (example: "C:Users\User\AppData\Roaming\Mozilla\Firefox\Profiles\profile.default-release"). Therefore, at this point, based on the manual indicated, it appears that Okular is not looking for the certificates in the directories/registries specific to Windows 11, just as it does on systems built on the Linux kernel.
We use the signatures from the firefox store, if the firefox store is inaccesible there's nothing we can do here, I'm really surprised the firefox store would be inaccessible, anyhow needs someone to spend some time with Windows, to investigate i guess. Firefox from Microsoft Store seems to be the problem here, if you want to make it work for now, use normal Firefox.