search

bitwarden / mobile

Retired Bitwarden mobile app for iOS and Android (MAUI/Xamarin).
https://bitwarden.com
GNU General Public License v3.0
21 stars 2 forks source link

Android App Ignores Ports in Hostnames #1620

Open K11LNZs2bosaN8de2oDP4Wxi42t7a4SQ1hskNRk opened 2 years ago

K11LNZs2bosaN8de2oDP4Wxi42t7a4SQ1hskNRk commented 2 years ago

Steps To Reproduce

1) Add a site with a hostname and a port and set the match to "Host"

For example, for my Synology NAS (Diskstation), a local domain in Bitwarden that works fine on Windows is: http://diskstation.services.lan:5000 (Host Matching)

2) Open http://diskstation.services.lan:5000 on Chrome on Android 3) Bitwarden will not find any matches. 4) Manually search for "diskstation", select the proper entry. Then get popup to autofill, autofill and save (I think that's the wording), etc. 5) If I hit "autfill and save," it fills in the user/pass fields and moves on. 6) Now, my Diskstation site in Bitwarden has two sites:

This will now find the site in BW every time, but now all my other home services on the *.services.lan domain will also have a "Diskstation" entry, which I was trying to avoid.

Expected Result

Expect auto search to be able to find the correct site just as it would in Windows

Actual Result

Many home services are the exact same domain, just different ports. Instead of having to scroll through a giant list of them, I set each entry to "Host" so that it matches everything exactly. No issues with this approach in Windows, but Android never finds the BW entry and wants a basic domain stripped of ports.

Screenshots or Videos

No response

Additional Context

No response

Operating System

Android

Operating System Version

11

Device

Samsung Galaxy S21+

Build Version

2.14.0 (3977)

Beta

pcg26ZgYydIb2crsdSBsA5TChJXm9d9BKIRXyzr commented 2 years ago

I am having the same and another related issue! The browser Extentions work well, only the app has this problem...

I set my whole app to "Host", just like my browser extentions and saw other problems as well. If I take your site as example: http://diskstation.services.lan will work just fine http://www.services.lan does not work

That means if the app is in "Host" mode, then no website without custom subdomain or with port will work. (Not sure if that is entirely true, didn't test enough but that's my theory) Hopefully that will be fixed! Thanks for your awesome development! :)

pcg26ZgYydIb2crsdSBsA5TChJXm9d9BKIRXyzr commented 2 years ago

Everything is working for me now! Running the Bitwarden App Beta V2.14.2

Maybe the stable app only has this issue? I don't know. Is it working for you as well?

K11LNZs2bosaN8de2oDP4Wxi42t7a4SQ1hskNRk commented 2 years ago

Signed up for beta, but didnt get an app update. Still have the same issue on stable.

pcg26ZgYydIb2crsdSBsA5TChJXm9d9BKIRXyzr commented 2 years ago

Which app version are you running at the moment? It will probably take a while for the update! If you get it, I hope it will work :)

K11LNZs2bosaN8de2oDP4Wxi42t7a4SQ1hskNRk commented 2 years ago

Version: 2.14.2 (4005)

egXTfmPmnBXJxz8sjHYER57B0OrBt0n0eEYnCie commented 2 years ago

I have this issue on 2.16.2

pcg26ZgYydIb2crsdSBsA5TChJXm9d9BKIRXyzr commented 2 years ago

For me it is also broken again.

URI Match Detection "base domain" works but URI Match Detection "host" which I am using is not working

eiBk8O6y2yOgRcn1aSg9uyRhTw8N0RN7vfKDXcv commented 1 year ago

I am still getting this issue on version 2022.6.1 (4795).

I'm wondering if this is at all on the radar of the team?

6i2HnONqIAiQ9FNlAF1wxxPTIRN0s64GHi87haV commented 1 year ago

Same on android 12 and Bitwarden version 2023.1.0

mzNrROprCr4gxgzB1M6gcUQVhsz3eyZPJepHMa8 commented 1 year ago

same on android 12, bitwarden version 2023.3.2 (6098)

HXBjsO3MbJc0gspuhL4GfWNVPIntKuek9Z79wtw commented 11 months ago

I have an issue that seems to be along these same lines.

I have a service running on https://10.13.1.100 My entry was set to: https://10.13.1.100/login Browser works fine, but on mobile is says "no item found for 10.13.1.100" (using android btw) Ive tried changing the URI match to base domain, host, and starts with, none of them worked on mobile. If i change the entry to https://10.13.1.100/ it still does not work, but if I remove the / at the end, it suddenly does recognize it. However I run dozens of internal services on the same IP but different ports. The android version completely ignores entries if there is anything following the IP address, regardless if it actually matches.

This means that I can't use any of my saved logins on my internal services, unless I manually search for them. This is incredibly frustrating because mobile is already the least convenient to use, and this issues makes it nearly unusable.

GKxqjXJftyBRqcKmCoeU9pv4dZTh0tMKL5OCAdk commented 9 months ago

I'm also having the same issue. Autofill works without issue on desktop but on mobile it won't auto fill HOST:IP correctly, regardless of the match settings.

NZMlQN0ey4HhoPXGjQOPVi45R4BuiY8hPTiteLZ commented 9 months ago

same on android 13, bitwarden version 2023.8.0 (7466)

PQDJ9D6eAbX75Tdwy0IAKCSGmcjTs6KPAtML2MU commented 7 months ago

I'm facing the same problem on Android (bitwarden version 2023.10.0 (8257)). I tried chrome and brave with same results. The port gets somehow lost in the way when trying to match URIs. I tried "starts with..." and "host", but bitwarden only sees the local IP and not the port.

If I press add login then the URI is shown without the port

LdINcj8kl5sH87BQ9RwrB1psVHeAoh1yBO1jvXx commented 7 months ago

Same issue here on 2023.10.0 (8257) (Android 13).

With multiple home hosted apps often with the same home domain/host hosting apps on multiple ports with multiple logins Bitwarden needs to recognise the port as a part of the URI.

In the Bitwarden docs it says port is considered to be part of the host for matching purposes so why doesn't it behave like this on Android?

Update: Oh. Just realised this was raised in 2021. No chance of this getting resolved then. Looking at alternative Bitwarden options now as this is a deal breaker for me.

7TRwjYhTKI9UNwTv7k30jjfkcXXFf6Vhl5imATy commented 2 months ago

Exact same in v2024.3.0. I've had this problem for ages, and only finally tried to pin down the problem today.

No issues with the browser extension, and this happens on all auto fill modes (inline and whatever the normal one is called).

Here's how it works. URIs like http://{IP}:{Port}:

Why is it a problem?:

So hopefully that helps point in the right direction of a fix. For anyone having this issue, you can workaround it by using base domain matching on the full socket address. I've only been on mobile since writing, so I don't know if this will mess up matching on the extension version though.

O2tuluFTQL4kYvs5O2y0xl3zEJQJpyj9YynrOIe commented 4 weeks ago

Same issue here on v2024.4.0

It's disappointing to see that the issue has persisted since 2021

uniquePWD commented 1 week ago

Has this been pointed to because there's something happening in regards to a fix?