Managing logins - how to compare


I am logging into an account in my chrome browser. I click the bitwarden extension icon and I get a screen with multiple entries for my login. I pick the first one because they all look the same. If it fails, I pick another. And so on, the tedium ensues.

Alternatively what I could do to clean it up, its click on a link in the extension that opens my account in my browser. There I would see the same list of login entries I see in the extension popup. Each would have enough info - username, the URL, a quick show PW icon, notes, etc; enough to distinguish one from another. I could then delete the extraneous ones on carry on.

It there any way to compare logins? I’m not smart enough to remember one from the other when I have to look at each of a dozen or so individually to determine duplicates or almost duplicates; or more importantly, ones with extensive notes.

Anyone have tips?

Thanks in advance.

Why do you have so many duplicates? If this is a result of a recent import gone awry, I would suggest purging your vault and starting over after cleaning up the file that you are importing from.

Sadly too tedious. This from a lifetime of CSV, then keypassx, then lastpass, now bitwarden. I just need to be able to cleanup as I go. Life is too short to make this a priority project; too many already. :wink:

I suppose I could export into a CSV file and then slice and dice and delete, but again, that could take weeks of evening and, for some entries, too insignificant to even spend time deleting/re-organizing.

A lot of them seem to have been created with different subdomain names. Before lastpass and bitwarden I used a common keypassx file shared from my dropbox, owncloud, nextcloud setup which was used from my desktop, laptop, android phone. Again, this is a lifetime of sites, apps, accounts, ssh logins - external, internal, and on and on. Probably at least 20 years. I think I still have some compuserve / sprynet addresses in there…

Thanks for the suggestion, though.

If you have access to Microsoft Excel, it has tools for automatically deduplicating data. I believe such features are available in alternatives such as LibreOffice, as well.

Another strategy that might be a small step up from manually deleting obsolete entries (in case the CSV/Excel deduplication doesn’t work for you): Got to Settings > Auto-fill and set the “Default URI Match Detection” method to Never. This will prevent any saved login item from matching to any webpage (except for any vault items for which you have customized the URI Match detection — and those would presumably be items that are “current” and up-to-date). I’m guessing that most of your accounts will not get any matching vault items after you change the default settings; my suggestion is therefore to use the following process to “reactivate” the correct login each time you visit a site that you haven’t yet fixed:

  1. Use the search function in the browser extension to find the vault item(s) that exist for that website. Click each item in turn to view its data.

  2. Scroll down to see the Updated and Created dates, which will hopefully give you a clue about which of the available items is the most current one.

  3. Click “Close” in the upper right corner to return to the search results, and click on the next item in the list — continue until you have found the correct item.

  4. When you have found the correct vault item, click the “Edit” to open the item for editing.

  5. Click the gear icon (:gear:) next to the saved URI string, and select Base Domain from the dropdown menu, and click “Save”. Now the extension should show a single matching item that you can autofill.

Over time, this will fix all of the accounts that you actively use; any accounts that you infrequently use and have not yet been fixed are still going to be present in your vault, but they will not create any clutter in your vault item matches in the browser extension.

… I don’t know, does that sound better, or worse? :rofl:

It sounds reasonable. Thank you for your generous help.

1 Like