Remove direct authentication via trusted networks or API password #27656
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
probot-home-assistant
bot
added
Hacktoberfest
core
has-tests
integration: auth
integration: http
integration: websocket_api
small-pr
|
Hey there @home-assistant/core, mind taking a look at this pull request as its been labeled with a integration ( |
|
Hey there @home-assistant/core, mind taking a look at this pull request as its been labeled with a integration ( |
|
Hey there @home-assistant/core, mind taking a look at this pull request as its been labeled with a integration ( |
delete-merged-branch
bot
deleted the
remove-api-password-trusted-networks
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Breaking Change:
It is no longer possible to make authenticated requests using trusted networks or by appending
?api_password=Xto the url. You will now first need to get an authentication token and use that token to make requests.These features were deprecated in Home Assistant 0.90 and 0.91 (released around April 2019). It was initially planned to be dropped in Home Assistant 0.96 (released July 17, 2019).
This also removes support of configuring the auth providers for API Password and Trusted Networks via the HTTP configuration. It now needs to be configured in the auth provider section (docs).
Description:
This removes the option to directly authenticate with Home Assistant API endpoints by adding an API password or by making the request from a trusted network. These features have been deprecated since early April of this year and were initially planned to be removed on July 17 with the release of Home Assistant 0.96.
Direct authentication meant that you could make an authenticated request without a bearer token by making the request from a trusted network or appending
?api_password=blato the url.These features are still available as authentication providers (docs).
The feature to use API passwords for direct authentication has been deprecated since Home Assistant 0.90 released on March 20, 2019 (#21884).
The feature to use trusted networks for direct authentication has been deprecated since Home Assistant 0.91 released on April 3, 2019 (#22487).
Related issue (if applicable): fixes home-assistant/architecture#174
Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Checklist:
tox. Your PR cannot be merged unless tests passIf the code does not interact with devices: