2028.8.1 HTTP YAML Deprecation Allow Bypass Login and Allow Trusted Users

Configuration
1

I just updated to 2026.8.1 and I have a number of settings in configuration.yaml that I do not believe have been fully implemented in the GUI, specifically allow_bypass_login and trusted_users

homeassistant:
  auth_providers:
    - type: trusted_networks
      trusted_networks:
        - 10.7.0.0/24 
        - 10.7.2.0/24 
      allow_bypass_login: true
      trusted_users:
        10.7.0.77: 9dsaf97sdfkakjf8asdf8asdfjkfd 
        10.7.2.23: 9dsaf97sdfkakjf8asdf8asdfjkfd 
    - type: homeassistant
  auth_mfa_modules:
    - type: totp

However, I do not see these settings in the GUI anywhere.

Has the HTTP yaml configuration been deprecated without complete support for all of the settings or am I missing something?

Edit: The warning states that

This stops working in version 2027.2.0. Please address before upgrading.

So I am assuming it that both will work simultaneously until all of the features have been migrated over. It looks like my configuration still works, so I will just ignore this message for now.

2

Related to this :up_arrow:

This post is more clear

You cannot trust a network that you are using in any trusted_proxies. The trusted_networks authentication will fail with the message: Your computer is not allowed

3

Those are auth_providers which are unrelated to the http integration & shouldn’t have been affected by the http migration.
In fact the documentation for those still tells you to set them up in yaml, so don’t delete that section - only delete the section under http:

4

yes…you did (see above)

5

Oh jeez… how embarrassing. That’s what I get for doing this too early in the day.

6

Not embarrasing at all! The instructions got lost in the mix!

7

Happens to all of us. Don’t worry about it.