Autofill match detection problems for URIs with ports (in Firefox for Android)

Ask the Community Password Manager
, ,
1

I have a bunch of self hosted services at

http :// raspberry.local:1000
http :// raspberry.local:1001
http :// raspberry.local:1002
http :// raspberry.local:1003

And HOST only detects those saved as http :// raspberry.local without any port. If I click auto fill and save, it saves them without the port. What OP and myself would like is for BitWarden to differentiate between 1001, 1002, 1003, 1004 automatically and offer the appropriate password.

1 Like
2

Check out regular-expression matching and equivalent domains. Either should accomplish your goal, with equivalent domains being the better approach.

That is not how it is supposed to work. You are putting the port number into the URL field, right?

3

I know how it’s supposed to work, but it’s not working and its super frustrating.

I’m using Bitwarden Version: 2024.4.1 (10283)

And Firefox (Android) Nightly 2024-05-17T03:26:59.244120172

Recently, Firefox took to only showing the domain name in the URL bar, could that be the cause of the issue? The full URI is there when you copy the URL, but it only displays the domain on the screen.

4

I would suggest reporting this as an Issue on GitHub. There is a possibly related issue with local domains already reported here:

 

The above issue was also discussed previously on the Community Forum, here:

5

Filed: Host Autofill doesn't work as it should in Firefox · Issue #9329 · bitwarden/clients · GitHub

6

I just tried this myself, and HOST matches the port as well. It differentiates your example URLs perfectly well. Maybe the match name HOST is a bit misleading, but it all works as intended

7

With Firefox for Android?

8

I need this as well, we have multiple sites running off of different ports on the same
URL or Domain or IP.

10.50.18.12:9080
10.50.18.12:443
10.50.18.12:8802

All of these are different credentials but in both Bitwarden Edge and Bitwarden Mobile. It just sees the IP and says try one of these 3 credentials.

9

@brink668 Welcome to the forum!

What setting(s) are you using for the URI match detection method for those URLs?

10

Hi @grb

I have tried all of the URI matches available but none of them seem to work, matching on the ports. The only one I have not attempted to create is regular expression.

11

@grb never mind, I just realized I had to update all of credentials stored.

I had to change all secrets that were for 10.50.18.12 to “HOST” match uri.

Now everything is good!

1 Like
12

All: I’ve moved this discussion from the feature request topic where it originally appeared, because the topic of discussion was a bug that was distinct from the feature request in question.

Also, according to this comment by Mozilla the issue was supposed to have been resolved with Firefox version 131 (August, 2024), if URI match detection is set to “Host”. It is possible that there has been a regression since then, in which case the following Issue on Bitwarden’s Github repo would be relevant:

1 Like