From 8afcdbfd248130b8e887d5d4e53674982c1b27e4 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Thu, 30 Aug 2018 15:57:09 +0200 Subject: [PATCH] Remove notice it's not enabled --- docs/auth_index.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/auth_index.md b/docs/auth_index.md index 2fa94854..a2fcfea4 100644 --- a/docs/auth_index.md +++ b/docs/auth_index.md @@ -3,8 +3,6 @@ title: "Authentication" sidebar_label: Introduction --- -> This is an experimental and unfinished API introduced in Home Assistant 0.69 and later. This is not enabled by default, it's not persisted to disk and should not be used in production. - Home Assistant has a built-in authentication system allowing different users to interact with Home Assistant. The authentication system consist of various parts. ![Overview of how the different parts interact](/img/en/auth/architecture.png) @@ -37,4 +35,4 @@ Clients are applications that users use to access the Home Assistant API. Each c The client will be provided with an authorization code when a user successfully authorizes with Home Assistant. This code can be used to retrieve an access and a refresh token. The access token will have a limited lifetime while refresh tokens will remain valid until a user deletes it. -The access token is used to access the Home Assistant APIs. The refresh token is used to retrieve a new valid access token. \ No newline at end of file +The access token is used to access the Home Assistant APIs. The refresh token is used to retrieve a new valid access token.