How do I tell KeePassXC to use the same database for both browser passwords and keyring?

[Martmists-GH]

KeePassXC works fine for passwords, but as soon as an application (such as Nextcloud Desktop) wants to remember a login, it prompts me to create a separate database for them.

[michaelk83]

https://keepassxc.org/docs/KeePassXC_UserGuide#_secret_service_integration

[Martmists-GH]

Yes, I have this configured already, but it keeps asking for a new database instead of the existing one.

[michaelk83]

If it's set up correctly and still asks to create a new DB, that's most likely a bug. AFAIK Nextcloud uses QtKeychain to talk to the secret storage. On KDE, QtKeychain normally defaults to using KWallet, which can then pass the requests to KeePassXC if configured correctly. KWallet has several bugs that would cause this exact behavior (incorrectly asking to create a new DB).

You can tell QtKeychain to talk to KeePassXC directly (bypassing KWallet) by setting the QTKEYCHAIN_BACKEND environment variable to libsecret. I think that was added in QtKeychain 0.16.

Though given that you're asking how to set things up, I guess you probably don't have that complex KWallet setup. In that case, the bug may be elsewhere. It's unfortunately not very easy to diagnose. You'd have to sift through the DBus communication to see what's going on exactly.

[Martmists-GH]

KWallet's secrets service was explicitly disabled in KDE Settings so everything could use KeePassXC, and that part should be fine because it does at least prompt me in KeePassXC to create the database.