How to change URI match detection in bulk using the CLI

[cksapp (Kent)]

@ddt3

• server1.shop.nl server2.shop.nl and server3.shop.nl.
• I have seperate passwords for server1.home.lan server2.home.lan server3.home.lan
  Because of default match detection all 3 passwords show up for all three servers.

Based on the base domain match detection rules this should not be the case, as two differing base domains (in your case shop.nl & home.lan) should not be being detected on match; as even if the domain matches but the TLD does not i.e google.com vs google.net.
Otherwise this would defeat much of a password manager’s usability, as it would be matching other non-equivalent domains such as accounts.google.com being matched to accounts.mit.edu

What I believe is happening is since your home.lan is not a proper gTLD or available on the Mozilla public suffix list (which Bitwarden uses to parse for matching) Bitwarden is ignoring the home.lan and simply matching on the hostname.
Since there is a matching URI in your vault from server1.home.lan the hostname server1 is being matched to server1.shop.nl

Another community member was recently experiencing trouble with their internal domain as well, as pointed out by one member here.
http://community.bitwarden.com/t/add-on-doesen-t-recognize-internal-urls-behind-reverse-proxy/44879/21

@grb

If you read this comment on GitHub Issue #1509 , as well as the discussion that follows, it seems that Bitwarden’s domain matching algorithms only allow domains that have suffixes in the Public Suffix list.

Unfortunately being that the two base domains are being incorrectly matched due to the internal setup there really isn’t a way around this that I can think of other than to change each URI matching for your internal domain to the Host option.
There is also no way currently to bulk update URI items for match detection as you are requesting or a way to enter a global matching rule such as LastPass

@ddt3

In lastpass matching rules are set on “vault level” eg.:
if domain matches “home.lan” then exact match on host: yes, exact match on port:yes

You may be able to complete these changes in batch though using the CLI if you are comfortable with that.

---

@ddt3

Had a look at the CLI interface and solved it in zsh:

foreach i in $(bw list items --search "home.lan" | jq -r '.[] | .id')                                                                                                                                                     
do
bw get item $i | jq '.login.uris[].match=1' | bw encode | bw edit item $i
done

That did the trick

Edit: I see you were able to get this resolved with the CLI tool after-all. Glad to hear it all worked out for you
-Cheers