jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-23 17:27:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Adding warning regarding legacy_api password

Browse Source 
Currently there is an issue #16441. Leagacy_api password not loaded if api_password located in package.
This commit is contained in:
bastshoes 2018-09-11 20:39:05 +03:00 committed by GitHub
parent 513ef6f63a
commit 80b34251e0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
source/_docs/authentication/providers.markdown
View File

@ -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. 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.
</p> </p>
<p class='note warning'>
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.
</p>
Authentication providers are configured in your `configuration.yaml` under the `homeassistant:` block: Authentication providers are configured in your `configuration.yaml` under the `homeassistant:` block:
```yaml ```yaml