Solved Lastpass stores all subdomains as entries for the main domain
-
Since I've gotten my NGINX RP setup and a few sites behind it, I've noticed that LastPass always wants to save credentials to sites as example.com instead of cloud.example.com or unms.example.com
It's quite the PITA... anybody experiencing this or know of a solution?
-
I get this as well. The only "fix" I've found is to create each new subdomain manually in LastPass so you can enter the entire domain.
Annoyingly it always remembers the domain.com/user/signup.htm page as well. The end bits aren't the only important part of a site address!
-
I never used this before but you can try creating a URL Rule in LastPass.
Log in at lastpass.com, go to Account Settings > URL Rules and click Add.Domain or Host: example.com
Path:
Exact Host Match: Yes
Exact Port Match: No -
@black3dynamite Yes, this looks like exactly what I want. I just found this myself after googling a little. I'll check it out a little more soon.
-
@black3dynamite said in Lastpass stores all subdomains from my NGINX RP as entries for the main domain:
I never used this before but you can try creating a URL Rule in LastPass.
Log in at lastpass.com, go to Account Settings > URL Rules and click Add.Domain or Host: example.com
Path:
Exact Host Match: Yes
Exact Port Match: NoYou have to do this for every domain?
-
@travisdh1 said in Lastpass stores all subdomains from my NGINX RP as entries for the main domain:
You have to do this for every domain?
It looks like it. At least for every domain that you want to separate subdomains from.
-
So I've set this up and it at least asked if I wanted to save the site for a new subdomain that I haven't already saved (instead of updating existing unrelated sites)... but it wants to save it as example.com still :pouting_face:
EDIT: It saves the "Name" field as example.com, but it gets the "URL" field correct with the proper sub.example.com and no longer suggests the other subs that don't match. So this is definitely a way better start, still not ideal IMO, but it does work correctly
-
You know what works perfectly every time.
Keepass.
-
@dustinb3403 said in Lastpass stores all subdomains as entries for the main domain:
You know what works perfectly every time.
Keepass.
Totally does the same thing.
-
@bnrstnr said in Lastpass stores all subdomains as entries for the main domain:
So I've set this up and it at least asked if I wanted to save the site for a new subdomain that I haven't already saved (instead of updating existing unrelated sites)... but it wants to save it as example.com still :pouting_face:
EDIT: It saves the "Name" field as example.com, but it gets the "URL" field correct with the proper sub.example.com and no longer suggests the other subs that don't match. So this is definitely a way better start, still not ideal IMO, but it does work correctly
But this is your preference. I don’t want this. I have a lot of internal things on *.domain.com that have the same credentials because of LDAP/AD linked auth.
I do not want all of these to be kept separately.
