Jump to content
Enpass Discussion Forum

Possibility to use wildcards in Inline Autofill Popup Menu blocklist

Recommended Posts

Hello Enpass!

First of all, thanks for updating the browser extension, it's a really amazing tool now!
I just have one tiny question, maybe I missed it in my search on Google and around the forums here, maybe I just miss something, I don't know.
But I was wondering if it's possible to use wildcards in the Inline Autofill Popup Menu blocklist.

Reason being is I also use Enpass for my personal accounts at work (like the password for my business e-mail account), where we also have another password manager for the business wide password credentials (sensitive internal information, internal credentials etc).
On our dev environments, I have two passwords managers that would like to be used, the URLs are quite the same, like appXX.dev.domain.tld.
In this case, it would be useful to just add *.dev.domain.tld on the blocklist, but it seems it doesn't do anything currently and it would be amazing if it did!

Keep up the great work you're doing, I really love using Enpass! Thanks for making me forget my passwords! ;)

Kind regards,

Edited by Mokaraa
  • Like 3
Link to comment
Share on other sites

  • 1 year later...
  • 6 months later...

Hi, I also have the problem that the wildcard does not work.


  • OS: OSX 13.5.1 
  • Enpass App: 6.9.0
  • Browser Extension 6.8.6
  • Browser: Chrome 116.0.5845.110 (arm64)


to reproduce:

configuration of exact hostname matching is not active

Website: https://discussion.enpass.io

URL pattern which work:

URL pattern which not work:

  • .enpass.io
  • *.enpass.io
  • https://*.enpass.io
  • https://dis*.enpass.io
  • https://discussi*.enpass.io


Kind regards

Edited by Tobl
added missing version
Link to comment
Share on other sites

Hi! Sorry for the very late response, but this issue still remains.
I have had this issue on both the latest versions of Windows 10 and Windows 11 (currently at 22H2, 22621.2134), using the latest Enpass from the Microsoft Store (currently 6.9.0 (1466)). For browser I have this issue independent of versions, currently at least with version 117, but had the issue with older versions as well (dating back to when I started the topic). The browser extension is version 6.8.8.

For pattern, I try to have something like this being wildcarded, but doesn't work: https://*.dev.domain.tld.

Edited by Mokaraa
  • Like 1
Link to comment
Share on other sites

Hi @Tobl

Following a meticulous analysis of the reported issue, I'd like to communicate our findings with you -

To block the example URL "discussion.enpass.io":

You can use the following regex pattern: discussion.enpass.io. This will block only the exact URL "discussion.enpass.io."

To block all subdomains of "https://www.enpass.io/" , i.e, any.enpass.io, another.enpass.io, etc.:

You can use the following regex pattern: *.enpass.io

This will block all subdomains of "https://www.enpass.io/".

To block nested paths under "https://www.enpass.io/" (e.g., "enpass.io/login/" or "enpass.io/signup/"):

You can use the following regex pattern: enpass.io/**

This will block any URL paths under "https://www.enpass.io/" including nested paths.

However, we have identified certain issues with specific regex patterns, which are as follows:

  1. Patterns like "https://*.dev.domain.tld" with wildcard usage in this format

  2. Regex patterns such as "localhost/*" for blocking URLs under "localhost".

Our dedicated team is now working on resolving this issue and these will be patched in a future update. Your patience in the meantime is greatly appreciated.

Link to comment
Share on other sites

Hi @Abhishek Dewan,
some answers to your findings.

URL pattern: discussion.enpass.io

Result: Password suggestion is shown for https://discussion.enpass.io/


And just to be clear, I don't want the wildcards to block URLs, they should match them 

URL pattern: *.enpass.io

expected behavior: 

  • match:
    • www.enpass.io
    • discussion.enpass.io
    • anything-else.anpass.io
  • should not match:
    • enpass.io

URL pattern: test*.enpass.io

expected behavior: 

  • match:
    • test-foo.enpass.io
    • test-bar.enpass.io
    • test-anything-else.anpass.io
  • should not match:
    • dev-test.enpass.io
    • www.enpass.io
    • discussion.enpass.io
    • www.discussion.enpass.io
  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy