Feature Request - Selecting which database to open

[ouzbirki]

I think there should be a menu or an option to select which database to open in the browser addon. Browser addon already has information about which databases are connected to the KeePassXC application. This would make KeePassXC easier to use with browser integration. The main reason for this is that the way to properly store your passwords and TOTP credentials is to store them in separate databases. So it would be real 2 factor authentication. Your data won't leak if one of your database's info leak, your accounts won't be accessible without having information of both databases.

But current integration works as this: browser addon tries to open the database which is selected in the KeePassXC application. When you need to enter your TOTP code while logging in to some service, you need to open the app and select your database which holds your TOTP credentials. This adds too many steps to the process.

Expected Behavior

There should be a button or menu to select the database user wants to open.

Current Behavior

KeePassXC-Browser addon/extension tries to open currently selected database in KeePassXC application.

Possible Solution

Adding a menu or a button to select which database user wants to open to addon widget and context menu.

Debug info

KeePassXC - 2.7.6
KeePassXC-Browser - 1.8.11
Operating system: Win64
Browser: Mozilla Firefox 121.0

[varjolintu]

KeePassXC has a separate popup when you are opening a database from the extension, and it allows you to select the database to be opened. This requires the database has been opened at least once in KeePassXC so it's one of the tabs.

[droidmonkey]

But you don't see that popup if at least one database is unlocked already

[nelson-tbone]

I too need the browser to "know" on which database to look and behave accordingly to database state (unopened-locked-unlocked) without having to rely on the desktop app tab to be corrected positioned (database that will be accessed being opened and current tab) because I run several profiles on browser and every one has it's own database, and mostly they are all locked.

Expected behavior for me: site asks for credentials, extension "talks" to app, asking for "his" database(s), if database(s) associated to extension on current browser profile are locked, ask db password, check extension key, credentials return to browser.

[varjolintu]

@nelson-tbone This is covered with the new Protocol V2 changes. It's still under work though.