You’re right - by default if authentication failure is not handled - there is redirect to /login which is left empty. Once you have esh-io-transport-http-basic there is a basic challenge sent which covers “authentication failure”.
Got the new build and the prompt for credentials but it doesn’t accept my Karaf console user name / password combo. The only thing in the log is:
2018-10-09 23:31:48.310 [INFO ] [home.core.auth.AuthenticationManager] - Failed to authenticate using credentials openhab:*******
Any other ideas?
EDIT: I seem to be locked out of everything now. I can’t control any of my devices via Alexa, the openhab app or myopenhab.org. They are all asking for authentication. Well Alexa isn’t she just says "Hmm, item name is not responding.
Same here with #1386. Although that latest build is supposed to disable authentication by default, it does not.
And yes, we need this to get enabled/disabled based on some runtime config option and not by default.
And to issue a warning and point to Karaf auth docs would have been nice.
I’ve been using SSH authentication in Karaf. Now that’s difficult to enter in a basic auth window in a browser so I’m locked out, too.
I had the same issue. After several tries I also installed the openhab2-addons package along with the downgraded version (make sure you use the version of the same day of your downgrade version) and then the addons and UIs loaded just fine.
Thanks for the tip, that makes absolute sense. I did the downgrade but this time I chose #1383 it brought back my UI’s but they still suffer from that 404 can’t find /login error. However, I can access them from myopenhab for now so at least I have a running system. Here’s what I did:
apt-get update (to make sure I had all the builds available)
apt-get install openhab2=2.4.0~20181010032256-1
apt-get install openhab2-addons=2.4.0~20181010032256-1
systemctl stop openhab2
systemctl start openhab2
This at least gives me a working installation albeit I cannot access the basicUI.