From 80b34251e007892b88d93a689f2273078fdcf421 Mon Sep 17 00:00:00 2001
From: bastshoes
Date: Tue, 11 Sep 2018 20:39:05 +0300
Subject: [PATCH 1/3] 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
From 905676ba691680a1d6555f8ad8f66c84ebc02081 Mon Sep 17 00:00:00 2001
From: DubhAd
Date: Sat, 15 Sep 2018 13:32:40 +0100
Subject: [PATCH 2/3] Spelling/grammar tweaks
---
source/_docs/authentication/providers.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_docs/authentication/providers.markdown b/source/_docs/authentication/providers.markdown
index 6d3aa2360b0..de5e223b015 100644
--- a/source/_docs/authentication/providers.markdown
+++ b/source/_docs/authentication/providers.markdown
@@ -31,7 +31,7 @@ Home Assistant automatically configures the standard auth providers and you **do
-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.
+The legacy API password auth provider won't be loaded if your API password is located in a package. This is because Home Assistant processes the `auth_provider` during the `core` section loading, which is earlier than the `packages` processing.
Authentication providers are configured in your `configuration.yaml` under the `homeassistant:` block:
From be1223e91e3ed45b3e8a35d231a4e559b60620f4 Mon Sep 17 00:00:00 2001
From: Jason Hu
Date: Sat, 15 Sep 2018 14:33:32 -0700
Subject: [PATCH 3/3] Add issue link
---
source/_docs/authentication/providers.markdown | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/source/_docs/authentication/providers.markdown b/source/_docs/authentication/providers.markdown
index de5e223b015..8da14db4aaa 100644
--- a/source/_docs/authentication/providers.markdown
+++ b/source/_docs/authentication/providers.markdown
@@ -31,7 +31,7 @@ Home Assistant automatically configures the standard auth providers and you **do
-The legacy API password auth provider won't be loaded if your API password is located in a package. This is because Home Assistant processes the `auth_provider` during the `core` section loading, which is earlier than the `packages` processing.
+[Issue 16441](https://github.com/home-assistant/home-assistant/issues/16441): the legacy API password auth provider won't be automatically configured if your API password is located in a package. This is because Home Assistant processes the `auth_provider` during the `core` section loading, which is earlier than the `packages` processing.
Authentication providers are configured in your `configuration.yaml` under the `homeassistant:` block: