![]() ![]() I came here wanting to suggest that equivalent domains be less of a gigantic pain to use, and found this suggestion already here, which appears to address basically the same thing. This behavior can be enabled or disabled by me on a per-domain basis.If not found, it searches one level higher in the domain name () and suggests credentials from that domain.If found, it only suggests those credentials.LastPass first searches for credentials.I have 100 credentials for apps under.Repeat steps 2-4 for unbounded number of applications (perhaps dozens).Alternatively, I create a URL Rule for.LastPass suggests 100 credentials for this application, so I have to manually search for the right one.So that I can more quickly find the credentials I need without creating URL rules for each subdomain. I would like to configure LastPass to strictly match all subdomains within a particular parent domain, In the case of, this could mean dozens of rules, which is difficult to manage. ![]() With URL Rules, you can add entries for each individual application's subdomain. These applications may have different credentials, such that you could have 100's of entries in LastPass within the domain. Each application is hosted in its own subdomain such as or . Consider the situation where you work in an organization who hosts many applications under a domain:.
0 Comments
Leave a Reply. |