I agree with this and find the push to force users to use a password on the websocket silly. This is not a piece of software used by the technically inclined; people using this innately posses a sense of security. I too have hass completely separated from the internet by hardware and additional vpn. It’s even shielded from other internal networks and actively monitored.
The parameter to get it to work has ‘legacy’ in it’s name; that doesn’t seem to bolster a lot of confidence that the option will be supported going forward.
I can see the scenarios with multiple users helping with new development and features but to drop this without offering to ‘opt out’ is annoying. Perhaps,.If you really want to track what called who how and when then have it come in as attributes or metadata or otherwise log what’s known.
I’d keep the hurdles towards adopting and integrating hass as low as possible, the rest and ws was ideally positioned for that.
After we have long-lived access token fully implement, you can use that token to access WS API, just add one round-trip. Even now, you can still use current access token cached in your browser’s localstorage to access WS API, the token is only asked when establishing connection.
Yes and I’ve been able to get the expiring token from the browser to work connecting to the ws on my test hass setup. However, asking for a new token using the refresh token
When you remove password in http section, Legacy API password dissapear.
In my opinion Home assistant local logging with trusted networks is something that should be implemented. When I try to connect to HA from my private network I should have option to add my network as trusted and don`t have to login with multifactor authentication . TOTP is great but in this option will be more usefull in private networks.
I’m kind of frightened by how people percieve the added security as a bad thing only because it introduces minor inconveniences. Especially with regard to the numerous topics we had about people being hacked by unknowingly expose their HASS to the web unsecured.
That’s not how you get a new token. We follow the OAuth2 spec and we linked from the release notes to our API docs that explain how to get a new token.
A double-edged sword. Breaking functionality while still getting improved security is not my idea, especially since I segregated Home Assistant from my home network where Home Assistant is denied connectivity to the Internet.
No one will ever feel frightened once someone can help me migrate my code to Home Assistant’s new auth system:
However, perceiving the added security as a bad thing is unfounded. If anyone exposes HASS to the Internet whether it’s secured via HTTPS or not, I do not sympathize them.
I don’t want to continue my debate about Home Assistant security. And I do apologize for sidetracking this thread. It is not my intention, but I need to bring up about trusted networks which is what I use.
And yes, I also use Tasker to activate a script when my phone rings.
I upgraded to 0.77, set up user and password, removed the legacy one from config, activated the totp authentication and I had time to switched to Lovelace. it’s cool, fast and secure, but I use very often HTTP POST to send commands to HA from Tasker and now I can’t understand how to authenticate those requests.
The number of open configurations that can be found with a few mouse clicks, and the number of “I’ve been hacked” threads would suggest that you are incorrect in your presuppositions.
Well then put a sticky up informing people that security is no luxury. I don’t leave my car unlocked on a public parking lot, that’s common sense.
But when it’s in the garage at home I leave it unlocked, for easy access.
And when I want to leave it unlocked I don’t have to bust out the passenger window, weld shut the bonnet and stick the key in the exhaust pipe.
I’m not annoyed that Home Assistant did not include security out of the box. It’s up to us to secure our Home Assistant installation. And if I’m running Hass.io, I’d make sure to be diligent and look over the SMB configuration, but since I use Linux, I simply use SSH to get into the Home Assistant configuration. The only thing that I expose is my VPN and that’s it. I have a certificate for my smartphone and I already have created a certificate authority in my server.
There is a way to do this but it is not well documented and only developers are familiar with it, I think in the next release or 2 it will be addressed in a easier way. For now I am keeping the api_passowrd for IFTTT , Tasker and other components that depend on it.
Yeh, because that’s one of the deciding factors on buying a car.
At the risk of giving this car analogy even more stage time,… imaging taking it in for service and when you get it back the only way to start the car is having to call the dealer for a pincode with no way of turning that off. I’d have questions.
So to use @drbytes car analogy, you’d rather buy a car with no locks on the doors and no need for a key for the ignition and sort those things out yourself later?
Obviously if you choose to secure your car differently then you can use “aftermarket” stuff, or you can just stick with what it comes with.
Same with homeassistant. If you don’t want to use the Auth system, take it off. If you want to use something different, code it up.
Don’t make it harder for everyone else just because you know best.
