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-24 09:46:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated to include example of using a Bearer token (#9429)

Browse Source 
* Updated to include example of using a Bearer token

This is the only way I got it to work with a secrets file and I thought it would be useful to share/capture the steps.

* Minor changes
This commit is contained in:
Rob Chandhok 2019-05-11 01:11:02 -07:00 committed by Fabian Affolter
parent 6cbcc1acdc
commit 625a07a832
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
source/_components/rest.markdown
View File

@ -191,6 +191,22 @@ Content-Type: application/json
User-Agent: Home Assistant
```
If you are accessing a resource protected by a `Bearer` token in an `Authorization` header, you can either put the token in the header field of the sensor configuration (not recommended) or store the token in your [`secrets.yaml`](/docs/configuration/secrets/) file. In that case, be sure to include the word `Bearer` in the `secrets` file.
```yaml
sensor:
- platform: rest
resource: http://IP_ADDRESS:5000/sensor
headers:
Authorization: !secret my_sensor_secret_token
```
Example entry for the `secrets.yaml` file:
```yaml
my_sensor_secret_token: Bearer gh_DHQIXKVf6Pr4H8Yqz8uhApk_mnV6Zje6Pr4H8Yqz8A8nCxz6SBghQdS51
```
### {% linkable_title Use GitHub to get the latest release of Home Assistant %}
This sample is very similar to the [`updater`](/components/updater/) component but the information is received from GitHub.