You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Self-signed certificate
The setup works great and I can get the iOS Mobile app to connect. However, it took a little digging to figure out that the basic auth username and login had to be applied directly on the local url. Also, means that the password is just there in plain-text for anyone to see and likely not securely stored on the device (assuming that's possible; sorry not an iOS developer).
Describe the solution you'd like
Add two optional fields to the settings for local username and local password and add these to any requests made to the local OpenHab url. I have not checked what the app does with the remote password, but I would hope we store it in a keychain or other secure on-device storage -- and we should do the same with the local password.
Describe alternatives you've considered
For the time being I have modified the local URL to include both the user name and password. It works.
Another alternative is certificates. We could let the user store a client certificate within the OpenHab app (ideally the possibility of separate certs for local and remote). Then the server could be configured to validate the client cert.
Additional context
I have not read anything specific about plans to provide authentication for OpenHab out of the box, so I don't know whether if the basic auth scheme is about to be replaced by something better. If not, it's better than nothing and simpler/cheaper than many alternatives.
The text was updated successfully, but these errors were encountered:
I would like to see this feature either, because entering a username/password is ok for my setup where a nginx with basic auth secures the public access to openhab. These credentials are also used for the local server and this leads to a HTTP 401
Is your feature request related to a problem? Please describe.
After reading through https://www.openhab.org/docs/installation/security.html I ended up securing my local OpenHab install using:
The setup works great and I can get the iOS Mobile app to connect. However, it took a little digging to figure out that the basic auth username and login had to be applied directly on the local url. Also, means that the password is just there in plain-text for anyone to see and likely not securely stored on the device (assuming that's possible; sorry not an iOS developer).
Describe the solution you'd like
Add two optional fields to the settings for local username and local password and add these to any requests made to the local OpenHab url. I have not checked what the app does with the remote password, but I would hope we store it in a keychain or other secure on-device storage -- and we should do the same with the local password.
Describe alternatives you've considered
For the time being I have modified the local URL to include both the user name and password. It works.
Another alternative is certificates. We could let the user store a client certificate within the OpenHab app (ideally the possibility of separate certs for local and remote). Then the server could be configured to validate the client cert.
Additional context
I have not read anything specific about plans to provide authentication for OpenHab out of the box, so I don't know whether if the basic auth scheme is about to be replaced by something better. If not, it's better than nothing and simpler/cheaper than many alternatives.
The text was updated successfully, but these errors were encountered: