From 80b34251e007892b88d93a689f2273078fdcf421 Mon Sep 17 00:00:00 2001 From: bastshoes Date: Tue, 11 Sep 2018 20:39:05 +0300 Subject: [PATCH] Adding warning regarding legacy_api password Currently there is an issue #16441. Leagacy_api password not loaded if api_password located in package. --- source/_docs/authentication/providers.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_docs/authentication/providers.markdown b/source/_docs/authentication/providers.markdown index 728ecb58b2d..6d3aa2360b0 100644 --- a/source/_docs/authentication/providers.markdown +++ b/source/_docs/authentication/providers.markdown @@ -30,6 +30,10 @@ To make the transition from API password to authentication system easier, we've Home Assistant automatically configures the standard auth providers and you **do not** need to specify `auth_providers` in your `configuration.yaml` file. Specifying `auth_providers` in your configuration will disable all auth providers that are not listed and can reduce your security or create difficulties logging in.

+

+Legacy API password auth provider wouldn't be loaded if your API password located in separete package. This is because Home Assistant process `auth_provider` during the `core` section loading, it is earlier then do the `packages` processing. +

+ Authentication providers are configured in your `configuration.yaml` under the `homeassistant:` block: ```yaml