Blacklist: disable Bitwarden extension entirely for specific sites

Similar to the request to disable autofill:

https://community.bitwarden.com/t/disable-autofill-on-page-load-option-for-specific-logins/22

But I think a blacklist where Bitwarden won’t operate, at all, on specific sites would help when dealing with issues such as the PayPal login problems.

To clarify, even if I’m not using autofill, something about BW seems to interfere with PayPal. Currently I have to disable the extension, login to PayPal, then re-enable it.

Since BW works great with most sites, being able to maintain a small blacklist of sites it ignores entirely would be nice. As in it doesn’t scan, doesn’t autofill, so as far as the site is concerned it doesn’t even exist.

Seems like a reasonable way to avoid the moving target of all the “Bitwarden doesn’t work/breaks site X/Y/Z” too.

I am out of votes, but being able to completely disable Bitwarden on specific sites would be very useful.

Device? OS? Browser?

Windows 10 20H2, Google Chrome:
Since a long time (months) I do not see any issue when trying to log into PayPal.

I vote for this, it is quite annoying to have to deny bitwarden everytime I check my online banking, which I don’t want to store.
Web extension, Chrome, Win11.

A blacklist feature is already available in Bitwarden, or are you guys asking for something different?

2 Likes

That would be great to have this feature in the Android app also, specifically to disable BW to complete on some other apps :slight_smile:

As mentioned here (*) to get this done just set the “Match detection option” of the relevant URI to “Never”:

image

(*) Using URIs | Bitwarden Help Center

A blacklist feature is already available…

However, the exclude domains definitely does not match this request. Personally I would like to have this feature because I’m developing a website and I don’t want to have bitwarden popping up and disturbing me when I’m logging in there. Therefore I would like to disable it for localhost (with strict match) but not for localhost:7080 as I have an admin panel there.

The “Auto-fill Blocked URIs” sounds like the correct feature, but it hasn’t been implemented to the firefox extension at least. (according to the linked site)

This feature request is several years old… but I would like to add to this discussion. I’ve found that the latest version of BitWarden Client (v6.X, chrome) causes significant slowdown on some web applications. I hope the BW team fixes the performance issue, but a great additional solution is to allow blocking BW from running on a site at all. The extension has the ability to opt-in to domains (site access in the extension manager). An opt-out option with be a massive enhancement.

1 Like

Yeah, same problem here. It slows storybook down a lot and even breaks style of some components

1 Like

I’ve yet to see any explanations for how to have BitWarden do nothing on a site you don’t have any Login for. Or for Identities… Like… tell me how to make this never show up again? Please?


[Screenshot edited by mod.]

@Keith_Woelke, welcome to the community!

Settings >> Autofill >> Show autofill menu of form fields has 3 values:

  • Off – neither the icon nor menu will appear. You then auto-fill with control-shift-L.
  • When autofill icon is selected. — just the shield appears until you click the icon, at which point it looks as your screenshot.
  • When field is selected (on focus) – behavior is as your screenshot.

If you do select one of the latter two, you can also dismiss the menu with the “esc” key.

Also, you may want to edit your screenshot to obscure your email address.

@Keith_Woelke I’ve taken care of this.

Thank you! And thank you for the reply. I guess that sort of solves the problem… ish. It’s annoying that I can’t do it per website though. I mostly just don’t want Bitwarden appearing AT ALL on work sites nor LastPass/Bitwarden. I guess it would also be less of an issue if Bitwarden was smart enough not to try to autofill Identities into every e-mail field of a login form…

I’d be OK with it appearing everywhere else. But I can settle for having to click the shield, I suppose.

One of the bigger issues I was having is that I have a website where I want Bitwarden to autofill and a website where I do not want Bitwarden to autofill. The domains are completely different, but Bitwarden kept offering to autofill, despite my setting of a Never URL in the Login for the undesired domain. The only way I finally got it working was with “Starts with” using the desired domain. None of the domain matching worked at all.

I finally realized it’s because Bitwarden has a default equivalency rule for the two domains, which (I assume) cause it to ignore my Never rule that I set for my Login. Once I modified the equivalent domains, it works more like I expect/want now. So… I don’t know if that’s a bug? I feel like a Never rule should override equivalent domains…

In the new browser extension UI (currently available in a beta release only), you will have the option to disable suggested Identity and Card items in the inline autofill menus.

Something does not seem quite right about what you’ve described. Would you mind starting a separate thread in the Ask the Community section of the forum, so that we can delve into whether there is a misunderstanding or a bug (while not derailing the current feature request topic)?

That is exactly what I want to do, but HOW?

BitWarden’s habit of popping up on a field when I did not click the bitwarden icon is really infuriating, and it completely masks the Firefox UI for removing Firefox autofill entries. There is no way to remove individual entries in Firefox when the bitwarden extension is running.

In the browser extension, go to Settings > Autofill, then uncheck the checkboxes for “Display identities as suggestions” and “Display cards as suggestions”:

Also, ensure that the checkbox “Display suggestions when icon is selected” has been checked.

I had actually tried setting autofill to “when icon is selected” in the settings before, and it didn’t seem to have any effect. I’ll try it again. But it’s a bigger hammer - doesn’t it affect ALL sites? Is there a way to disable this for specific URL patterns (which is what this post is asking for) ?

No, the settings I had mentioned above affect all sites accessed while the browser extension is active.