You have like 50 microsoft admin accounts.
You go to login(dot)microsoftonline(dot)com and want to find credentials to use to login.
Since (currently) bitwarden doesn’t sort entries list alphabetically you have to search for credentials, for example [email protected].
Problem: you get the list of all accounts for different domains, not just microsoft admin accounts.
If you use searching for an entry then domain patterns are ignored and bitwarden shows in whole vault.
Solution 1:
If I am on “login(dot)microsoftonline(dot)com” and use search in browser plugin, all entries shown should be compatible only with current domain. So in other words, just as bitwarden checks a domain pattern to select entries for autocompletion, same pattern and rule should be used for searching.
Solution 2:
As I mentioned in another suggestion - just add “always sort entries alphabetically” rather than by last used time, so I don’t have to use searching at all just scroll to proper entry because it’s position on the list will be easily predicted (advantages of alphabetical sorting).
Hi, to clarify, you can have one login to many different services.
For example [email protected] as login to m365 admin and others. Let’s assume that you have 30 different services and entries connected to this login.
Thing is if you are currently trying to login to M365 as an admin (you are on login(dot)microsoftonline(dot)com) and try to find a login to use then you are flooded with different unsorted logins. So you want to search for your login and you will write [email protected] in search field.
Bitwarden then won’t search all entries that are compatible with only login microsoftonline com, but totally all logins for all services. Bitwarden ignores the domain that you are currently on.
If you want a work-around, what I would suggest is to modify your search strategy, to use one of the following options. First, you can specify the account and and domain in the search:
This will bring up unrelated entries, as well, but the one you want should be on top. The following variants are abbreviated, and should float your desired entry to near the top of the list (if not at the top):
john.doe micro
company microsoft
doe@comp login.mic
(this works because the basic search inserts leading and trailing wildcards for each search term, and uses the number of search term hits to prioritize the sorting of the search results).
If you want to restrict your search results to only show the desired login item, which requires a leading > character and explicit wildcards (*). You can then use the + operator to require the presence of a search term. Thus, any of the following should work:
In general I would not use them because the app should behave in more expected way. Users shouldn’t be forced to find a workarounds if the app behaves unexpectedly. I feel that searching through all entries should be done in desktop or we app. Bitwarden plugin is a tool that works in the context and this context is the domain I am currently on because all enetries bitwarden suggests me are always and only for current context.
In my opinion it is consistent and logical that If a tool hints me with login entry for a domain that I am currently on than it’s predictable, expected and ok. If it hints me with 50 entries, because I have 50 logins for this domain that is ok, too. If I want to search through these 50 entries I do, still in current context (current domain). That is expected behaviour. Searching in current context is expected.
I am sure that everyone would agree that it’s logical and should be a default behaviour. At least it there should be an option for configuring this behaviour as default and I would use this option.
I would give browser plugin two options: 1. Search only in entries complying with current context (domain) - same behaviour as hinting entries. 2. Always sort presented entries alphabetically. (don’t use last used entry on top of the list).
As for me, these are two most important features that shoudl be implemented in the browser plugin.
These would make me totally happy because would boost productivity.
because would boost productivity.