Add equivalent URLs setting to avoid creating/maintaining duplicate passwords
Many sites redirect to another location to authenticate or use different URLs to connect to essentially the same site. LastPass has an extendable database to allow for this. For example: bing.com hotmail.com live.com microsoft.com msn.com windows.com windowsazure.com office.com skype.com azure.com. These use the same login. The ones that are well known can be provided as a default set (editable, obviously), but also allow the user to add their own as they discover them.
Bill Walton
shared this idea
-
Travers
commented
Also https://foo.example.com/ and https://foo.example.com should be considered equivalent but don't seem to be either
-
Aleff
commented
Change website detection by ignoring whether or not there is “www” before the domain. Currently if credentials are saved on https://www.example.com they are not detected on https://example.com.
This suggestion is just to eliminate the tedious manual maneuver of going for credentials by writing only the second-level domain and adding the site without “www” to the list of linked domains.
-
Todd Rossi
commented
Ugh, this one is KILLING me!
If we can't get a global URL equivalency option, at least having the option to copy "Websites" URLs to other passwords would make life significantly easier.
-
Todd Rossi
commented
I was bothered by this not being implemented like LastPass, but I did find that individual password entries can have multiple URLs. Not ideal compared to a global list of matching URLs, but it does work. Just a bit of work if you have lots of accounts, like I, and presumably other software developers do, for the same servers/applications.