The Android app (both regular and beta versions) will no longer connect to the server (either local or remote). I get an Authentication error:
“Authentication failed. Please check the configured username and password respectively the provided SSL client certificate (HTTP code 401).”
I can connect to my sitemaps via a Web browser; both locally and remotely (I am using NGinx), although I do get an error ‘SSE subscription failed: running in fallback mode’ on the remote connection that I haven’t seen before.
In the new GUI I have ‘API Security->Allow Basic Authentication’ enabled, and ‘API Security->Implicit user role for unauthenticated requests’ enabled too.
I have changed the app server credentials to the new ones I created when I first logged in to OH3 on the GUI.
There are a lot of ‘Unauthorized API request: Invalid Basic Authentication credentials’ messages in the log files.
Is something broken between the Android app and OH3 or do I have a configuration issue somewhere?
Ah, you didn’t have it turned on in the first place. keep in mind that if you do turn authentication on in MainUI, you’ll need to reflect that in the Android app. I believe it should be the same credentials as your admin account.
Don’t fully understand. Where to I turn that on in the Main UI?
Didn’t see before that I can actually do quite a lot in the Main UI without login, you’re right. Only to go into settings I need to log in with an administrator account. That’s the account I was also using in the App, but reading your description, I assume there’s a place I can add / define users and turn on authentication?
I tried both regular and beta apps. Both behave the same for me.
If I turn off ‘Implicit user role for unauthenticated requests’ API Security option then my Sitemaps still load in a Web browser but I can’t control any devices (connection for these is htttp://:8080).
@rpwong - thanks for your suggestions. I will try another device later. I suspect that this will be something to do with NGinx and the new security features in OH3. It will probably turn out to be an obscure security setting that I will need to tweak in my NGinx config file!