Jens L.
Jens L.
 
I've not had to do anything custom, the App just works for me (using authentik as IDP, envoy/istio ingress on k8s and using proxy mode for HASS)
Probably, I haven't really looked into the HASS auth code that this is based on in a while
I dont think this is something that should by done by the SSO client, I played around a bit and noticed that you can set the username to anything, so...
1. Make sure `http.trusted_proxies` is set correctly, I think HA requires this nowadays anyways, but make sure to set that to the IP/subnet of your internal reverse proxy. Thats about...
I've not run into this issue, but my install is also older, so I have this config ``` I have no name!@postgres-postgresql-0:/$ cat /opt/bitnami/postgresql/conf/pg_hba.conf host all all 0.0.0.0/0 md5 host...
*Partial reply, bear with* > Sorry for the long comment, the longer I think about this the more things I notice :D > > ## Problems with using #3156 for...
The should be fixed by using the nginx config from the docs https://goauthentik.io/docs/installation/reverse-proxy
Valid feature request, but not something on the roadmap right now and not something I expect too many people want so this'll have to wait, however any contributions for this...
If availability is this big of a concern then I'd recommend using the kubernetes helm chart which does rolling restarts for these changes Additionally, a lot of the config values...