In order to have a single place for one’s passwords on multiple platforms, could You or would You integrate KeepassXC as a keyring provider?
Or would there be other approaches to provide a multi platform password manager?
That is essentially already possible.
While Plasma and KDE applications have traditionally accessed credentials via the KWallet system, that system itself has been modernized to use a so-called “secret service” provider for the actual storage.
Plasma comes with its own provider called ksecretd but it should also work with any other, e.g. gnome-keyringor, like in your case, KeepassXC
I haven’t tried this myself but this option in the KDE Wallet settings should, when disabled, keep ksecretd from starting and request going to whatever secret service provider you are running instead.
1 Like
I’m using keepassxc with plasma since 6.4.5, and it works reliably after session restart.
It was a bit quirky to setup, even after unchecking “User KWallet for Secret Service Interface”, it would stay running, and Keepassxc wouldn’t let me enable secrets until doing so. Finally I just killed ksecretd, which allowed me to enable keepassxc. After that it will take over the secret service, but things still were insisting on trying to talk to kwallet directly, and would hang on startup for a minute, and then grudgingly use the new socket only after forcing a ~/.config/[$application]-flags.conf with “–password-store=gnome-libsecret”.
It wasn’t until I restarted the session after changing that everything seems to work normally, so maybe the same for you.
1 Like
This is what I get when I stop ksecretd and start KeePass secret service integration.
What application to connect with the Keepass service and how?
Starting the app Tuba for the first time I get:
KeePass configuration looks like this:
And the “Exposed Entries” part (pencil icon on Manage and then on the left down to “Secret Service Integration” again) is set to “Expose entries under this group”?
Just ask because that image from the configuration is missing (Part 2 at the secret service integration enabling steps in the KeePassXC user guide).
Can you give an example?
Even applications that use KWallet should work because kwalletd is now only a proxy that forwards request to the secret service.
Doesn’t work with sea horse. sea horse sees the entry, but gets an empty password.
I give up.
It was a few months ago now, but from what I remember it was mostly electron apps that were being weird (go figure). Slack, Claude Desktop, Signal, VSCodium all did it, some worked when setting the flags file, others didn’t, but I just lived with it until I could get a sec to restart the session a few days later.
Since it’s been ok, but I’d also upgraded after that to 6.5 and now 6.6, which looks like you’ve been making some changes around kwallet anyways, so either way no complaints anymore, other than limitations of the secret provider in general.
1 Like