Closed yegle closed 4 years ago
Since the login workflow with Google cannot be run within an embedded webview, there is no way for us to intercept the cookies.
If it were possible to intercept cookies, it would complicate the app a lot. This is not something we should add to the official app.
This is a duplicate of #45
FWIW, there is a login API for Pomerium that doesn't rely on using embedded browser to authenticate with Google: https://www.pomerium.io/docs/reference/programmatic-access.html
Is this something that Home Assistant Android app would like to support?
Actually I think if Chrome Custom Tabs are used, the cookies are automatically shared with Chrome and problem solved?
Have Chrome Custom Tabs been looked into for this issue? I think they would fix the issue and make Home Assistant Companion possible for those that have Identity-Aware Proxies.
A lot of other apps use Custom Tabs for exactly this reason, and it's not just specific to Chrome.
https://developers.google.com/web/android/custom-tabs
This issue really should be re-opened since there is definitely a solution to this problem. This issue also prevents people (like me!) from being able to use the Android app at all due to it not supporting any sort of authentication providers/proxies being put in front of Home Assistant to secure it from the outside world.
An identity-aware proxy is a safe way to expose your web service/API/website to public network.
It works like this:
(Pardon my vague description).
I'm currently using pomerium.io (open source IAP). It would be great if the Hass Android app can:
(Pardon again for being vague, not an Android dev. Highly recommend any devs to take a look at pomerium.io and test out).