This doesn't seem to be very user friendly. My final naming convention for connections is. If I don't include the database name, I get two duplicated entries returned in the browser for every matching entry in the databases.
After that I learned that I also need to include the database name. I started with a naming convention that included the user name, machine name, and browser name.
Because all of the connections are stored in a single list in the database keyed by this name and shared across multiple users, machines, and browsers, the names need to be unique for all combination of user, machine, and browser. When these connections are initiated, KeepassXC prompts me to name it. This process must be repeated for each database in each browser with the extension. To connect to multiple databases, I have to select each database, and then return to the browser and use the Connect button to establish a connection to that specific database. I'm trying to understand what's required to connect the KeepassXC-Browser extension in all of these browsers to both databases for every team member.Īs far as I can tell the Connect button in the extension only connects to the database that's on the active tab of the KeepassXC interface. The work database would be synced with the other members of my team who also have multiple systems with multiple browsers. Both databases would be synced on three of my systems running Linux, MacOS, and Windows, and each of them run multiple browsers.
For example I'd like to have Home and Work databases open at the same time. My team is trying to switch to KeepassXC, so we can use multiple password databases simultaneously.
0 kommentar(er)
