LastPass Vault should allow for multiple URLs to one entry The reason:
You have one account for a single service but need to log in on multiple domains or surfaces: The same login works on their homepage, on a support page (that uses a different URL) or their mobile app.
Autofill does only work with one URL today so I have to search manually in LastPass for the correct password again and again and that is very annoying.
Since this s the same account I refuse to generate multiple entries for those.
Equivalent domains stink!
We need a way to enter multiple URL on ONE card.
And we need to allow for regex there.
Example *.domain.com should work.
And we might want to be more specific on some.
Agree on multiple URLs.
It should also be fairly easy to implement and therefore already be implemented.............
I use multiple URLs for having an IP based login and a DNS based login.
That way I can use either for logging in to my devices.
@SDRyan You don't seem to understand the point here. If you have a user/pw combination that works for multiple URLs that is annoying in LastPass...
Imagine you have an account with a homepage (somecorp.com) and their respective support page (somesupport.com) - somehow they have two distinct URLs, but share one account database. If you save the account for their page (somecorp.com), then on the support page (somesupport.com) the account will not automatically be displayed, because it has a different URL.
This is annoying as hell and very easy to fix, it would seem.
Coming from Bitwarden and this is something pretty needed and basic.
When you have a password stored for a page and isn't set for the phone, you can search it, select it and Bitwarden asked you to fill with that password and at the same time if you want to add the new URI/URL
So CRAZY that I cannot SIMPLY add URLs comma separated in the URL of a record!
Bitwarden is my next destination, I am almost there. I am starting to hate Lastpass for so many aspects. (One of them being: Not possible to give edit permission or transfer ownership of a shared password is really killing my workflow. And the time it takes to receive a shared password is SO long! - stop ranting)
I agree with many of the above comments, but I came to it from the different perspective of the URL for starting the login process was different to that used for the actual login, i.e. "somecorp.com" for login window but that opened "xyzsecurity.com" for the actual entry of username and password. This situation is annoying in that one has to have a dummy password entry to "launch" into the site. The "equivalent domain" solution did work for my situation, though I wonder whether different companies might use the same "xyzsecurity.com" in future leading to another problem.
Yes, let us have multiple URL on a password entry to solve both of these problems.
Another sub0feature that would help is the option to select an existing vault entry if Lastpass pops up the "do you want to save" dialogue, to which the new URL can then be added.Plus, the possibility to merge existing entries
I like this idea very much because it would make my Vault far less crowded.
I'd also like to say that Equivalent Domains does not do everything that multiple URLs would and Equivalent Domains is much more complicated to use than multiple URLs would be.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.