I have a “regular” HA setup with version 0.73. Regular meaning ubuntu 16.04 + python venv + nginx reverse proxy + lets encrypt certificate. I also have DNS configured, so I access my HA instance with same url from everywhere.
I’d like to use some new features in new versions of HA, but this means that I have to migrate to the new auth system as well. So I have set up an .84 instance beside my .73 setup.
If I stop the .73 and start up the .84 instance everything seems to be working, except one thing, the login.
In my .73 system I use nginx digest auth, and the username and password can be saved by the browser, so when I arrive home I only need to click “OK” on the login screen and I am in.
With the .84 system however the “best result” I could reach was that I need to type in the username every time. This is not convinient and takes down the WAF.
Yeah, I know that to some people this may not seem as a real problem, but I am convinced that my setup is the best way so all other family members can use HA now without hours of teaching and “getting used” to things.
I rather not lose the nginx reverse proxy, because I have geo ip and fail2ban set up with it as well.
I have read about “long last tokens”, but those are for services to be able to log in, as far as I see it.
I have tried the HA android app, but that needs to connect to HA directly and not through nginx reverse proxy.
Is there anyone out there who has a similar setup, and managed to solve this nuissance?