When we use the "Web Login" for a internal website.
If shows us al the passwords for "ouddomain.local" instead of only the password from which the URL is present in the entry.
It would be nice if it shows the best match on top, and the additional credentials in a list below the top match.
The reason why you have multiple suggestions is because the matching is compared with the base domain.
Let’s say for example you have two entries, one with the url “https://sitea.ouddomain.local” and the other one with the url “https://siteb.ouddomain.local”.
When you will navigate to “https://sitea.ouddomain.local”, you will also get https://siteb.ouddomain.local” because both sites have “ouddomain.local” as their base domain.
We have in our roadmap to be able to choose the matching detection for the URLs in a website entry in DPS.
This way you will be able to set for the url https://siteb.ouddomain.local to match only when the host (in this case: siteb.ouddomain.local) is matching the URL.
I raised this issue 2 weeks ago, and I was answered:
Since this request has been added to the todo list of our engineering department, I will close our current ticket [...]
I see that this is a long term issue.
Would the engineering department be in trouble, here is basically what we need as a general option in Devolutions Web Login.
Default URI Match Detection
- Base domain (the only choice now!)
- Host (fqdn)
- Starts with
- Regular expression
Alternately provide instructions on how to get licensed with Devolutions Web Launcher while Web Login is unusable for the purpose DPM was purchased.
We will bump up the priority for the match detection selection in websites entries in DPS.
You said that you would also like an option in the local DWL settings for the match detection.
Do you also want a local DWL settings in the DPS section to have a global default match detection?
there's room for improvements in both flexibility and usability .
Usability: we need asap a way to set default match to host / fqdn. Whatever in DWL or DPS, the quicker the better.
Flexibility: as seen in my personal credential manager:
In web filler, have an option to set default URI match. This should be Host by default, with aforementioned choices (Default URI Match Detection)
In password database, have an option at URI setting with choices: Default match detection + aforementioned choices (Default URI Match Detection)
So user is in generally in control with exception of those URI needing another choice. Here the entry editor is in control for specific matching requirements.
Should we raise the bar, a web login entry would have a list of URI, each with match detection choice.