We have an enterprise on premise instance and I have noticed, that the browser addon doesen’t recognize certain websites even though the URL is correct in the entry.
I even tried the option autofill and save, and while this does actually save the entry the URL still isn’t recognized and hence it isn’t offered as a valid login for the site. I have to search the entry by hand and select it.
Yes this is correct, gitlab (now using gitea) is one of the few applications that are not behind the reverse proxy. What’s interesting though, is that if I use the IP to access these internal applications, bitwarden recognizes the host credentials correctly!
I reproduced this with gitea and another application. So it has to be some issue with the bitwarden extension not being able to lookup the local DNS from the machine/browser. The DNS is configured on the docker host where bitwarden is located and I can nslookup gitea without problems.
Can anyone else test/confirm/reproduce this on their internal sites?
I think Peter may be onto something that would be worth testing further. Can you test what happens if you change the stored URI from http:gitlab...https:gitlab...? If your server is not using SSL, the browser should redirect to the http: page, but perhaps this will help Bitwarden recognize the URL?
Another option to try: Use Host or Regexp options for the URI matching (instead of your default Begins With).
Can you provide a little more information? For example, what is the domain name suffix? My understanding is that there may be issues with URI matching if the domain suffix is not on the public suffix list.
Also, it may be a good idea to let us know more about your environment (OS, browser, etc.).