Long Lived Access token authentication fails

Hi,

I hope I just have a missing configuration here and not a bug but let’s see.

I use the latest docker version as provided by Causticlab 0.4.0. I’ve configured the following environment variables:

HC_BASEPATH=/hass-config/
HC_API=http://homeassistant:8123/api/                        <- docker interal routing
HC_HASS_WS_API=wss://homeassistant.url.tld/api/    <- browser url
HC_HASS_API_PASSWORD=token

Problem

1. When trying to observe events by websockets the connection is closed instantly.
2. When sending commands to HASS, like a restart, it fails.

Ha-configurator logfile:

WARNING:2020-08-22 13:42:33,417:__main__:<urlopen error [Errno 111] Connection refused>

Homeassistant logfile:

[homeassistant.components.http.ban] Login attempt or request with invalid authentication from 10.0.6.36

Question Am I missing a certain configuration or not using the right set here?

[danielperna84]

I’m not really familiar with Docker-setups, so I have to refer you to the documentation for that.

I don’t think the version is the issue here. Even though it’s been a while since I’ve worked on this, I believe from 0.3.7 to 0.4.0 no significant changes related to the access token have been made. It was mainly refactoring to make the package for pip and including some JavaScript code which usually was fetched from cloud resources. The Token-stuff has been stable for a long time. So that shouldn’t be the problem in this case.

[danielperna84]

I was also thinking about quotes, I find that the settings.conf file needs quotes around the values since it’s a json structure. Do you use quotes in your systemd configuration? Because I did not in my docker-compose file: I used it as a key value struct HC_HASS_API_PASSWORD=token.token.token

The quotes in the file are required because it’s a JSON file. It would be a syntax error to have a string without quotes. For the env-variable you don’t need quotes, and I don’t have quotes in my unit-file.

Yes, the API is now working and I can do things. On the websocket however I noticed that in the situation where I populated the token via environment variables in docker the password field was also pre-filled.

If the value is not prefilled, the API shouldn’t work as well. If it does, then that’s because you have configured HA to always allow connections from certain locations. The token used to communicate with the API and the prefilled value in the UI are exactly the same. So if one is missing, the other is missing too. So if one is working and the other is not, it must be a policy-thing outside of the scope of the configurator.