If #3 above is yes, we would need the ability to disable this for organizations/enterprises using self-hosted or Bitwarden cloud who’s internal security policies prevent or deny the use of Tor on corporate networks or corporate assets/services.Is any additional support necessary for the server-side of this implementation? Docker container, reverse proxy/nginx configurations, etc.?.Also, would the UI settings for this be on the same configuration screen as the server/service URLs before logging in?.If these are linked through the native Android and iOS frameworks, we would need to know how that would work with Xamarin, which we are using for our mobile apps (along with Xamarin Forms).Kyle and I had a brief couple of messages and there are only a few questions we would want to address through your approach and investigation (which these questions may answer some of yours in regards to areas of impact, the “where” and what):
If you go to the Account Settings section of the Web Vault, there is a page called Domain Rules where you can define custom equivalent domains (for example, by defining an equivalence of, androidapp://).We would be perfectly willing to accept this and support it if you wanted to get this done. This won’t help with the launching problem, but there is an alternative approach to setting up a single login item to work on both websites and mobile apps (other than defining two URIs in the login items, which is what you’re doing now). See here for a starting point, but maybe some Android user will come along and give you more direct advice.
There are some hoops that have to be jumped through to get auto-filling to work on Android. If I launch the app directly, I see nothing that indicates any involvement by Bitwarden. This “tapping” was done on your Android phone, correct? If so, I would think it should launch the app, so hopefully someone else can help you troubleshoot. I get no response when tapping the launch icon for the app. I would suggest maybe setting the match detection to Host, Exact or Starts With for the androidapp:// URI, as a test. What is the default URI match detection method configured in your settings? The documentation describes mainly how the different options work for a an or scheme URL, so it’s unclear how the Base Domain matching method (the default method, unless you’ve changed it) and the others work when it comes to a mobile app URI.
I have specified Default match detection.
0 kommentar(er)
