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-20 07:46:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove strict connection (#32523)

Browse Source
This commit is contained in:
Robert Resch 2024-04-29 20:52:24 +02:00 committed by GitHub
parent 80b929ae8b
commit 8dee491489
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 0 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
source/_integrations/http.markdown
View File

@ -86,11 +86,6 @@ ssl_profile:
required: false
type: string
default: modern
strict_connection:
description: Specifies the strict connection mode. Please read the section ["Strict connection mode"](#strict-connection-mode) before changing this value. Can be one of `disabled`, `guard_page` or `drop_connection`.
required: false
type: string
default: disabled
{% endconfiguration %}
The sample below shows a configuration entry with possible values:
@ -126,33 +121,6 @@ http:
- 172.30.33.0/24 # You may also provide the subnet mask
```
## Strict connection mode
The strict connection mode specifies how the Home Assistant instance should react to unauthenticated requests to endpoints that don't require authentication.
**Requests from private networks are always allowed.** Make sure to set up the reverse proxy correctly; otherwise, this feature will be useless.
The following modes are supported:
- `disabled`: Strict connection mode is disabled, and all unauthenticated requests are allowed (Same as before `2024.5`).
- `guard_page`: Home Assistant will answer any unauthenticated requests with a guard page, informing the user about the strict connection mode.
- `drop_connection`: Home Assistant will drop/close the connection for any unauthenticated requests, similar to when no Home Assistant instance is running.
If activated, Home Assistant will not even show the login page. To log in on a new device, the user needs to ask the instance admin for a temporary link. The instance admin can generate the link by calling the service `http.create_temporary_strict_connection_url`.
### Service `http.create_temporary_strict_connection_url`
This service can be used to generate a temporary link with a validity of one hour to log in on a new device when strict connection is enabled.
It has no arguments and can only be called by admins.
This service populates [response data](/docs/scripts/service-calls#use-templates-to-handle-response-data)
with two URLs described in detail below.
| Response data | Description | Example |
| ---------------------- | ----------- | -------- |
| `url` | Temporary URL pointing to `login.home-assistant.io` | `https://login.home-assistant.io?u=https...`
| `direct_url` | Temporary URL pointing directly to your instance | `https://example.com/auth/strict...`
We recommend using the `url` response value so the user gets a generic help page when, for example, the token is expired. Especially when the mode is set to `drop_connection`, the user will get no feedback and will not know if there is a general problem or if, for example, the token is expired.
## APIs
On top of the `http` integration is a [REST API](https://developers.home-assistant.io/docs/api/rest/), [Python API](https://developers.home-assistant.io/docs/api_lib_index/) and [WebSocket API](https://developers.home-assistant.io/docs/api/websocket/) available.