LastPass and alts - local domains, hosts and subdomains. Help!

[paulca]

Stop using 'paletted' 12 char passwords Paul, they said.  Stop generating predictable variants of your password, they said.  Use a password manager and 16 character random blobs instead Paul... they said.

So, when I moved to "Brave" browser I disabled it's password auto-complete and installed lastpass.

Out on the web it works fine.  It's how it behaves locally and "in the lab" which is rather upsetting.  Upsetting because it is getting some very simple, but very serious things completely wrong.

It seems incapable of identifying anything short of a 2nd level domain.  It will 100% match domain.com, but when it comes to hosts host1.domain.com and host2.domain.com it's accuracy drops and it gets confused and presents both options randomly.

When I log into a new dev node, say "k8sn2.lan.mydomain.com" lastpass asks if I want to up date the password for pve.lan.mydomain.com and even when I edit the hostname to be correct and save the password, the next time I open that node it will offer me the password for a different user from another host again.

I briefly googled this and it disappeared rapidly into enterprise config of last pass premium with registered secure DNS integrations and stuff.

Is there any middle ground?   Are there any "good" password managers which will handle more complex hosts/user/password combos.  Like as a developer I might need to remember 2 or 3 different accounts for a machine with a dynamic IP and or port number!  I think I have sent LastPass raving insane in a matter of weeks.

[Shonky]

Bitwarden can do things url "starts with", "exact", "contains" and a couple of others. You can have more than entry, it just defaults to the last used.

Does Lastpass not offer similar options?

[paulca]

Hmm.  I found something.  "Domain rules".  It seems you can apply "match exact host", "match exact port" to domains.

Thats a start I suppose. 

I can see why they don't do that by default.  It's a common issue when the website signup form comes from www2.domain.com but the sign in page comes from auth5.domain.com a lot of password managers just go "what password?  That 16 character one I just generated for you?  No.  Not seen it mate."

[Shonky]

Looks like this is what you want:
https://support.lastpass.com/s/document-item?language=en_US&bundleId=lastpass&topicId=LastPass/Manage_Your_URL_Rules.html&_LANG=enus

Bitwarden which I use does seem a bit more flexible:
https://bitwarden.com/help/uri-match-detection/

I do still have a couple of URLs that occasionally "clash" but really it's so rare I've not bothered to put too much time into trying to fix it.