-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authentication for Relay #156
Comments
Are you integrating with some other home automation platform? I resolve this by not exposing GAR to the internet but using the device created in my Hubitat to issue other announcements. That system has security built in so it provides a buffer between GAR and the internet. I know the same thing is possible with Samsung SmartThings and Home Assistant as well. Just a possible workaround. |
I've been having a look at this, and it's a bit of a pain at the moment. It's very simple to use, and I think it'd solve your problem quite quickly.
Ngrok will give you a URL, something like "https://13858332kg.ngrok.com:7989". You can then just call this URL rather than your IP address and it'll securely route the request to Assistant Relay. A word of warning though. If Ngrok is restarted, you'll get a new URL to use. You need to register for a basic account ($5/mo) to have a static ngrok URL |
Using a reverse proxy such as Nginx will help. You can add whitelisting or basic authentication to protect it. However I'm not sure if basic auth is supported by IFTTT. |
I believe you can do |
@gpetru1 Please see version 4 rework post. I'll leave this open until implemented |
@gpetru1 Added to v4. If you want to test then clone the v4 branch, do |
Since I have the Relay server port forwarded to the internet for IFTT automations, it would be nice to have authentication for the web interface. I understand potentially calls could still be made to the server but at least the configuration and sandbox are not wide open. Thanks again for all of your hard work!
The text was updated successfully, but these errors were encountered: