This repository has no description
0

Configure Feed

Select the types of activity you want to include in your feed.

configs.hass: only allow the id.lassul.us login

Mounts an empty auth_providers list to /config/auth_providers.yaml. homeassistant: auth_providers is read only from configuration.yaml, packages can't set it, so the volume's configuration.yaml includes it once (auth_providers: !include auth_providers.yaml under homeassistant:). Without the homeassistant provider only auth_oidc remains: the welcome page redirects straight to id.lassul.us and no password form is offered.

Long-lived access tokens have no credential and are not checked against a provider, so they keep working. Refresh tokens from earlier password logins fail on the next refresh and need one id.lassul.us login. The password credentials stay in the auth store, so a revert brings the password login back.

+6 -1
+6 -1
configs/hass/oidc.nix
··· 1 1 # Login via id.lassul.us (Zitadel project hass, configs/hass/proxy.nix) with 2 - # the auth_oidc custom component. The username/password login stays. 2 + # the auth_oidc custom component, the only login (auth_providers below). 3 3 { config, pkgs, ... }: 4 4 { 5 5 # Loaded from /config/packages like configs/hass/monitoring.nix. ··· 18 18 automatic_user_linking: true 19 19 include_groups_scope: false 20 20 ''}:/config/packages/auth_oidc.yaml:ro" 21 + # No HA auth provider, so no username/password login. Packages can't set 22 + # it, configuration.yaml in the volume has once under homeassistant: 23 + # auth_providers: !include auth_providers.yaml 24 + # Long-lived access tokens are not tied to a provider and keep working. 25 + "${pkgs.writeText "auth_providers.yaml" (builtins.toJSON [ ])}:/config/auth_providers.yaml:ro" 21 26 ]; 22 27 environmentFiles = [ config.clan.core.vars.generators.hass-oidc.files.env.path ]; 23 28 };