Ability to define "Equivalent URL" on a credential

Hello,
I'm not sure to understand you don't save you credential directly into the website and why you don't use the Equivalent Url in the web site?



Regards

I may have expressed myself unclear :)

An example.
In the shared vault I have several RDP sessions where I have defined that credentials should search user vault for "MyDomainAccount"
In my user vault, I add the credential entry "MyDomainAccount" and I can connect to my RDP sessions.
Then we get e.g. a CRM system for case management, which is a webiste, linked to my AD credentials.
This website will I not connect to through DVLS/RDM but through my normal browser.
So to "activate" that Workspace knows that this credential entry is for "crm.domain.com" I have to create a website session entry and link the website to the credentials.
I feel this is superfluous

Beeing able to add "Equivalent Url" could also solve another thing:
Office365, for instance, you use the same Entra ID credential for many webpages.
So if I have a web connection which has a deep link to a VM (Bastian web conn only) and then for Entra ID.
You will have to specify https://logon.microsoft.com and a few others, to make sure that password fill works on all the page Microsoft have to enter credentials, en all websites.
If the credential could hold "Equivalent Url" as well, you only needed to specify the "Equivalent Urls" on the credential entry, and all Web session could share it.

Regards Lars

Hello,
I now understand what you want. I will think about that and verify what we could do. I just need to find a place to avoid the confusion.

Regards

Hi

Any news about this?
I just created a Vault as "Credentials vault" thinking this should be a perfect place to consolidate my passwords - Including my website passwords...
Just to be hit in the head with:
and

Because my username/password fill application can't understand username/password entries, hence rendering the "Credentials vault" useless for credentials to websites.

Disregard my signature on this post - This is friendly bullying :) as this just frustrates me to the point where I want to give up on using Workspace, hence DVLS, as my website autofill source. If I just wasn't that stubborn.

Regards Lars

Hello,
I might have a suggestion. It's not as simple as you want, but it could be a workaround. You could create a User/Password entry and a website entry. Link the credential entry to the website entry and add the equivalent URL only in the website entry. You will be able to reuse the same username/password and have all the URLs in one website entry. What do you think?


Regards

Hi

Thank you for your response.

This doesn't solve the issue with where I would like to share/reuse the equivalent urls on two different web-entries.

If, for instance, you use your google account to login to "other" sites.

If we talk RDM, and I have a website entry for tailscale.com and etoro.com
For both connections to know to put the username and password into accounts.google.com they both need it as equivalent urls.
So instead of filling both entries with the same equivalent url, the credentials entry could have provided it for both entries.
Of cause, and maybe this was what you were telling me, I could create a third website entry for accounts.google.com and only link the credential to this entry.
But, this is exactly what I try to avoid, having shadow website entities only functioning as a relations database.
Secondly, it still doesn't enable me to use a "Credentials only" vault with Workspace.

Regards Lars