Make the Home Assistant Local Provider Appear First

[TheDuffman85]

For me always the OIDC is shown as first option. I would like have Home Assistant Local first. How can I change the order of the auth providers?

I tried to add it manually after the default provider, but without any luck.

homeassistant:
  auth_providers:    
     - type: homeassistant
     - type: auth_oidc

auth_oidc:
  client_id: "someclientid"
  discovery_url: "somediscoveryurl"

I always see this provider first

But i would like to see this first

Thank you for your great work!

[christiaangoossens]

Hi @TheDuffman85, thank you for your feature request! This is currently not a supported configuration option, but I will put it on the list.

I have converted the issue to a discussion post in the feature requests category as it is intended behavior at the moment.

[TheDuffman85]

Personally I think it would be best to configure the oidc provider under the homeassistant auth_providers section like the stock auth providers. The order in which you add these is also the order they are executed.

[christiaangoossens]

I looked at enabling this again, but it's currently not workable because it would also break the automatic login button. Let's leave this one open to revisit later.

[TheDuffman85]

The reason I need this is, I got a Wall Display that shows a dedicated dashboard. The authentication for this device is done using trusted IP with auto login. This is only working if it's the first authentication method in Home Assistant. I think no integration should break default behavior.

[christiaangoossens]

The reason I need this is, I got a Wall Display that shows a dedicated dashboard. The authentication for this device is done using trusted IP with auto login. This is only working if it's the first authentication method in Home Assistant. I think no integration should break default behavior.

That's true, but in this case HA forces me to do so to enable autologin (it requires oidc to be first so we can detect the cookie), so it requires some creative workarounds to fix your issue.

I likely will have to split the provider in two:

• detect autologin, if not set, execute next (trusted IP in your case)
• show code form (configurable at any position)