Core: Home assistant breaks previous trusted networks logic

[i-am-shodan]

Home Assistant release with the issue:
0.80.3

Last working Home Assistant release (if known):
Before auth was switched over

Operating environment (Hass.io/Docker/Windows/etc.):
Python3 virtualenv

Component/platform:
Auth / Frontend

Description of problem:

I have tried to set up home assistant for use in a kiosk environment. To do this:

• I have a set up home assistant to make use of trusted networks.
• I have a HTML site which has an iframe which points to https://SITE:8123/kiosk/group.kiosk.
• The HTML page removes the controls / menu which would allow someone to move away.
• Before the most recent HA update going to this site would push the user straight to the kiosk group.

Now even with the trusted network setting set, the user still has to chose what account to log in as. Can I provide this via a GET parameter? How can I force trusted network connections to automatically use a specified user account.

[reef-actor]

A number of people have expressed a desire to be able to specify a default, low-privilege, guest account that is automatically logged in on trusted networks, but balloob has made clear that this is not something that is in the vision for the future of the user functionality.
So really that means if you need to ensure that any time HA is opened the user is presented with the controls immediately, you need to stick with an older version or fork the project and make your own changes. Sorry :(

[awarecan]

Not a bug, won't fix. I am going to close it.

You can login via trusted network provider and save your login.

[acid2000]

Sure close the bug as home assistant has changed its operation.

But for the record:

• it’s a change in behaviour and for existing users was a bug. An upgrade literally broke my use case - which AFAIK was fully supported.
• saving the creds of the trusted provider doesn’t work in my specific use case