Hi. I have credentials stored for a list of subdomains using the Chrome extension:
When acessing e.g. b.example.com I get credentials matching a, c, d, e, f, g, h, .., b, ... z. Sometimes it's not in the list of suggestions but I have to search for it.
It's 2021 and surely someone can invent a smarter algorithm for matching a subdomain against the subdomain in the stored credential url? It shouldn't be rocket science.
I am proposing two things:
1) Keep track of when a credential is used somewhere and attempt to prioritize it next revisit.
2) Credentials matching subdomain urls should go before those who just match sibling subdomains.
Does that make sense?
... View more
We use LastPass to login to many hosts within our company of acme.com. When I go to a host like host2.acme.com, I am presented with a very long list of possible ID's/Password's for host2.acme.com. We need a LastPass user option to only list ID's/Password's for host2.acme.com and not all of acme.com like LastPass does today. LastPass needs to start looking at the "host2" portion (subdomain) of the FQDN. Otherwise LastPass is very hard to use for a user that logs into many hosts within a site (i.e. the acme.com name space). Example: host1.acme.com has 10 different login IDs host2.acme.com has 5 different login IDs host3.acme.com has 15 different login IDs host4.acme.com has 1 different login IDs host5.acme.com has 9 different login IDs When I go to host2.acme.com, LastPass presents me with 40 different login IDs to choose from and not just 5 Login IDs.
... View more