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
after upgrading the mobile app to 4.0.4, login at our server (version 2.2.0) is completely broken.
We are using the following environment:
Tag | 2.2.0
OS Type | Linux
OS Release | 4.15.0-66-generic
Node Version | v8.11.4
Mongo Version | 3.6.12
Mongo Storage Engine | wiredTiger
With the latest mobile application running on a Samsung Galaxy S8 with Android 9 and the patch level from Oct-2019.
According to the mobile applications, login credentials (using the Atlassian Crowd connector) are rejected.
When looking at the HTTP response code (401) in our reverse proxy (NGINX) this makes sense:
So I increased the log level in our Rocket.Chat server instance to Errors, Information and Debug enabled all the tracing options and looked at the output, which is a single line upon login:
server.js:204 API ➔ debug POST: /api/v1/login
Log in with a Browser (Chromium) and the same user & password works fine without any problems.
Hi,
after upgrading the mobile app to 4.0.4, login at our server (version 2.2.0) is completely broken.
We are using the following environment:
With the latest mobile application running on a Samsung Galaxy S8 with Android 9 and the patch level from Oct-2019.
According to the mobile applications, login credentials (using the Atlassian Crowd connector) are rejected.
When looking at the HTTP response code (401) in our reverse proxy (NGINX) this makes sense:
So I increased the log level in our Rocket.Chat server instance to
Errors, Information and Debug
enabled all the tracing options and looked at the output, which is a single line upon login:Log in with a Browser (Chromium) and the same user & password works fine without any problems.
After downgrading the mobile application to 3.5.1 which can be found for example in the F-Droid marketplace https://f-droid.org/en/packages/chat.rocket.android/ everything works as expected again.
How can we debug the issue further?
Thanks and regards,
Florian.
The text was updated successfully, but these errors were encountered: