Matching URL's to Entries

Hi,

The matching list is always sorted alphabetically. It does not prioritize entries based on the matching type. (https://docs.devolutions.net/password-manager/kb/browser-extension-knowledge-base/urls-comparing-types/)

When an entry matches, it will appear in the list in alphabetical order alongside the other matching entries matched by URLs and equivalent URLs.

From what I understand, you would like the list to be sorted by priority based on how closely the URL in the current tab matches 1:1 the URL, or equivalent URL, of an entry. Is that correct?

Best regards,

Hi,

The matching list is always sorted alphabetically. It does not prioritize entries based on the matching type. (https://docs.devolutions.net/password-manager/kb/browser-extension-knowledge-base/urls-comparing-types/)

When an entry matches, it will appear in the list in alphabetical order alongside the other matching entries matched by URLs and equivalent URLs.

From what I understand, you would like the list to be sorted by priority based on how closely the URL in the current tab matches 1:1 the URL, or equivalent URL, of an entry. Is that correct?

Best regards,

@Olivier Desalliers
That is correct, sir.

I believe that should be a user configurable option in this case. Either "alphabetical (default)" or "Best Match" for example in the main extension, and workspace.

Especially when there are URL's that have a plethora of the same 1st name. Something like {sitemame1} - Analytics may actually not be the correct credentials for {sitename1} - Stats, which is the page I am actually on.

Therefore, if something like "1:1", or "Exact" (since it's already in the software), would be very beneficial to not just me, but I'm sure hundreds of others as well, so we can go back to naming our credentials what they are for, and not having to do something like ".a-{sitename1} - ....", etc. now knowing how they are sorted.

Thanks!

Hi,

We will open a ticket to analyze possible ways to add more sorting options for the Matching list.

In the meantime, a workaround would be to configure each website using Exact only. However, this may not be possible in your case if you need to rely on other matching types.

Thank you for your suggestion.

Best regards,

Hi,

We will open a ticket to analyze possible ways to add more sorting options for the Matching list.

In the meantime, a workaround would be to configure each website using Exact only. However, this may not be possible in your case if you need to rely on other matching types.

Thank you for your suggestion.

Best regards,

@Olivier Desalliers
I *do* have them set to *exact* (as you can see in the screenshots I provided).

However, it sounds like the alphabetical order is overriding no matter what I put in there.

Hi,

What I meant is that, for example, if I have the following URL in one entry:

https://forum.devolutions.net/product/cloud

and this URL in another entry:

https://forum.devolutions.net/product/server

If my current tab is:

https://forum.devolutions.net/product/cloud

I will not see the second entry with https://forum.devolutions.net/product/server unless https://forum.devolutions.net/product/cloud is added as an equivalent URL in that second entry.

In your case, are https://{sitename1}/diags and https://{sitename2}/diags configured in the same entry as equivalent URLs?

In my own example, I would have two separate entries: one for https://{sitename1}/diags and one for https://{sitename2}/diags. However, I understand that this may not be possible in your configuration.

Best regards,

Hi,

What I meant is that, for example, if I have the following URL in one entry:

https://forum.devolutions.net/product/cloud

and this URL in another entry:

https://forum.devolutions.net/product/server

If my current tab is:

https://forum.devolutions.net/product/cloud

I will not see the second entry with https://forum.devolutions.net/product/server unless https://forum.devolutions.net/product/cloud is added as an equivalent URL in that second entry.

In your case, are https://{sitename1}/diags and https://{sitename2}/diags configured in the same entry as equivalent URLs?

In my own example, I would have two separate entries: one for https://{sitename1}/diags and one for https://{sitename2}/diags. However, I understand that this may not be possible in your configuration.

Best regards,

@Olivier Desalliers
I can do separate entries, that's not a problem. I just had them combined since they use the same username and password across both those domains.

I will go ahead and create separate entries and mark it *exact*. It would be nice, after y'all get done with the ticket, if the new update doesn't show anything not matching "exact" for that specific URL, that would be fabulous! Then if multiple stuff need to be shown, the default action, other than "exact", can be used.