Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

keepassxc-browser: Unable to connect to a second database #4215

Closed
gxfgbo opened this issue Jan 21, 2020 · 7 comments · Fixed by #4315
Closed

keepassxc-browser: Unable to connect to a second database #4215

gxfgbo opened this issue Jan 21, 2020 · 7 comments · Fixed by #4315

Comments

@gxfgbo
Copy link

gxfgbo commented Jan 21, 2020

I'm trying to connect keepassxc-browser in Firefox to two databases. I can connect to and use a single database fine. I cannot fully connect and use a second database.

Expected Behavior

A second DB connection should be connected and maintained.

Current Behavior

When I go into keepassxc-browser settings, I can connect to a second database if its tab is selected in keepassxc. Both databases are show on the DB connections page in keepassxc-browser, however refreshing that DB connections page results in the first DB connection being removed.

Possible Solution

None I could find

Steps to Reproduce

  1. Select the first DB tab in keepassxc
  2. Connect to the first DB in keepassxc-browser
  3. Select the second DB tab in keepassxc
  4. Connect to the second DB in keepassxc-browser
    5: Refresh the DB connections keepassxc-browser setting page

Context

Debug Info

KeePassXC - 2.5.3
keepassxc-browser: 1.5.4

Libraries:

  • N/A

Operating system: Windows 10
CPU architecture: Intel x64

Enabled extensions:

  • keepassxc-browser
@gxfgbo gxfgbo added the bug label Jan 21, 2020
@droidmonkey
Copy link
Member

Are you using unique names for your connections?

@varjolintu
Copy link
Member

varjolintu commented Jan 21, 2020

Is your second database a clone from the first one? You can verify this by viewing the Root group properties and check the Uuid.

EDIT: There's already issue made for this particural bug with cloned databases.

@gxfgbo
Copy link
Author

gxfgbo commented Jan 21, 2020

I am using unique names for the connections.

It is possible that the second database was originally created from a copy of the first database. The purpose of the two databases was to split all logins into two DBs (Personal vs Work).

I'll look for the bug with cloned databases.

I should add, my ultimate objective is to allow searching across both databases. In keepassxv, I have enabled "Search across all open databases, but keepassxc-browser still returns entries from only the DB whose tab is selected in keepassxc. If I'm off base how I'm trying to do this, all feedback is appreciated!

@varjolintu
Copy link
Member

Creating a new database and merging/importing credentials from your old database should do the trick.

@gxfgbo
Copy link
Author

gxfgbo commented Jan 21, 2020

Creating a new database and merging/importing credentials from your old database should do the trick.

Thanks @varjolintu. That solved it!

I created a new "second DB", merged all entries from the old instance and created a new connection key. Both DB keys remain when I refresh the keepassxc-browser options and I can now search properly across multiple DBs.

Many thanks for the help from all those that replied. Please let me know if I should do anything to add to the existing cloned-DB bug report.

@droidmonkey
Copy link
Member

We should probably add a button to the database browser settings page to "Refresh Database ID" or similar which would create a new UUID for the database.

@varjolintu
Copy link
Member

The same has been suggested in the original issue thread: keepassxreboot/keepassxc-browser#640

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants