Bug 122070 - allow custom nss certificate path
Summary: allow custom nss certificate path
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected)
Hardware: All Linux (All)
: medium enhancement
Assignee: Not Assigned
Depends on:
Blocks: WebDAV
  Show dependency treegraph
Reported: 2018-12-13 09:26 UTC by rs
Modified: 2024-06-04 15:50 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description rs 2018-12-13 09:26:51 UTC
According to [#116466] uses client certificates available in Firefox. Security freaks can have their Firefox profile in a different more secure location, like for instance a secure encrypted container or partition. Client certificates are then not in their default location and LO will not be able to access links to client certificate secured content. Please provide (at least an expert) configuration for custom profile location or custom browser path.
Comment 1 Xisco Faulí 2019-01-14 16:05:01 UTC
it makes sense. Moving to NEW...
Comment 2 kolAflash 2024-05-24 15:07:04 UTC
At least since LibreOffice-7.4 there's a button that looks like it does the job. (I haven't tested it)

Options -> LibreOffice -> Security -> Certificate Path / Certificate -> Select NSS path

Can you test if this fixes your problem?
If yes, please close this bug.
Comment 3 rs 2024-06-04 15:50:25 UTC
(In reply to kolAflash from comment #2)
> Options -> LibreOffice -> Security -> Certificate Path / Certificate ->
> Select NSS path

As work around I used FF profile manager and created a custom profile pointing to the secure location. Then I changed my browser script to use the profile manager in stead of direct profile paths. This is compatible then with LO that uses FF profiles.

I tested the button and it adds another option called "manual". When I select manual in stead of my custom FF profile I can access the same certificates from the secure container. 
Button works as expected. I'll close the bug now. Thanks for notifying me.