Browser Plugin Search should only find logins related to the opened website

Browser Plugin Search should only find logins related to the opened website

1 vote

avatar

Browser Plugin Search should only find logins related to the opened website
or at least have a setting to define if i want to search only for a keyword or a keyword related to the website

--> Just like it was when using the Browser Plugin with RDM

All Comments (3)

avatar

Hi,

Are you currently connected to Devolutions Hub (Business/Personal) or Devolutions Server?

The current search functionality serves multiple purposes beyond just filtering entries based on the active website tab. It also supports:

  1. Finding website entries and navigating to their respective urls.
  2. Finding credit card entries to autofill payment forms.
  3. Finding contact entries to autofill registration forms.
  4. Accessing any other relevant entries as needed.


We will open a ticket to explore adding a setting that allows the search to function as a filter only.

Best regards,

Olivier Désalliers

avatar

A customers may have multiple environments we need to access and the way RDM and HUB handle a search command is very different.

You click on the Workspace plugin while being connect to the Hub Business, when
searching for Customer A you get many results, you click on the Azure Environment link.
A new Browser tabs opens; you click on the username field and that’s where it become troublesome.

Within the username field you click on the Hub logo to search, you search for Customer A and get to many results.
You then must manually search for the Azure credentials since Customer A has multiple environments besides Azure.

However, it seems that RDM is able to get better results and immediately is able to find the correct item.

A feature that does work for the HUB is to use Equivalent URL's. However, this still doesn't anwser the question that RDM and Hub handle a search result very different.

avatar

Hi,

When connected to RDM, you’re filtering for entries that specifically match the current website, rather than performing a full search.

In contrast, when connected to Hub, a comprehensive search is conducted across all entries in synced vaults. This means that if "Customer A" appears in entries not associated with the current website, Hub will still find them. RDM, however, would not, as it filters strictly based on entries matching the website of the active tab.

Best regards,

Olivier Désalliers