Test that you can get keys back from kong "client_id": "03N4ehIbe44hYhnjGwO8hfW8jTHnxLSL", "username": a client id to the test consumer "provision_key": "uijq0y4dBFZITqirZ9QJr18DeHjaMpXS", "accept_http_if_already_terminated": true, Http POST name=oauth2 config:='' HTTP/1.1 201 Created Http POST hosts:='' paths:='' HTTP/1.1 201 Created Http POST name=me.io.apis host=api.me.io port:=5000 HTTP/1.1 201 CreatedĬontent-Type: application/json charset=utf-8 What am I doing wrong to make this work? This seemed to be the easiest implementation but it doesn't like anything. I have added trusted_ips to the envs so that I dont run it over ssl, which if you dont gives an error of Must use https. There doesn't seem to be any other information out there that indicates whats going on. I have tried following without any luck even removing the client_id doesnt work. I am constantly getting invalid_client error with nothing in the logs to really tell me whats going on. I am trying to setup the oauth2 plugin with the the grant_type=password. Passing in these env variables environment: Currently I have kong running inside docker-compose with access to the gateway making requests. If you don’t have a valid domain name for your Home Assistant instance, you can modify the hosts file on your computer to fake one.I have been setting up Kong locally and testing different kinds of setups. This is because we only allow an IP address as a client ID when your IP address is an internal network address (e.g., 192.168.0.1) or loopback address (e.g., 127.0.0.1). However, you can use the IP address to access Home Assistant in your home network. You have to use a domain name, not IP address, to remote access Home Assistant otherwise you will get Error: invalid client id or redirect url error on the login form. When you start Home Assistant next, you’ll be required to set up authentication again. storage/ folder in your configuration folder: You do this by shutting down Home Assistant and deleting the following files from the. While you should hopefully be storing your passwords in a password manager, if you lose the password associated with the owner account the only way to resolve this is to delete all the authentication data. INFO (MainThread) You need to use a bearer token to access /blah/blah from 192.0.2.4īefore using the procedure below, make sure you explore options provided here. Under the new authentication system you’ll see the following warning logged when the legacy API password is supplied, but not configured in Home Assistant: If you’re seeing authentication failures from 127.0.0.1 and you’re using the nmap device tracker, you should exclude the Home Assistant IP from being scanned. Troubleshooting Authentication failures from 127.0.0.1 Home Assistant provides several ways to authenticate. Treat the password like the key to your house.Īs an extra level of security, you can turn on multi-factor authentication. This means you are also exposed to random black-hats trying to do the same. Make sure to choose a secure password! At some time in the future, you will probably want to access Home Assistant from outside your local network.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |