After upgrade to v3.1.0:
Login remains
After loading page is shown login page and error Invalid User
Nothing :confused:
[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFaviconService.replaceFaviconDataFromDataURL]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource:///modules/PlacesUIUtils.jsm :: loadFavicon :: line 209" data: no] PlacesUIUtils.jsm:209:28
loadFavicon resource:///modules/PlacesUIUtils.jsm:209
loadFavicon resource:///modules/PlacesUIUtils.jsm:362
setIconFromLink resource:///actors/LinkHandlerParent.jsm:154
receiveMessage resource:///actors/LinkHandlerParent.jsm:71
TypeError: window is null 2 WebRequestContent.js:143:7
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIInterfaceRequestor.getInterface] network-response-listener.js:84
Sync encountered an error - see about:sync-log for the log file. policies.js:1008
resetFileLog resource://services-sync/policies.js:1008
InterpretGeneratorResume self-hosted:1156
AsyncFunctionNext self-hosted:695
Since the update to 3.1.0 made yesterday, I have the same errors when connecting to the web application. It disconnects after closing the tab with Invalid user.
iOS (4.6.3) and Android (4.5.2) application no longer works. Unable to connect when I reset the app.
We've got the same issue here. Started with an image upgrade.
Rocketchat is running in a docker-environment with nginx as reverse-proxy and LDAP backend. Docker is using the official image from hub.
guys - option on Accoutn settigns - Forget User Session on Window Close is enabled?
guys - option on Accoutn settigns - Forget User Session on Window Close is enabled?
Not enabled here.
guys - option on Accoutn settigns - Forget User Session on Window Close is enabled?
Disabled
Rc confgired with ldap?
Отправлено с iPhone
11 апр. 2020 г., в 16:59, Daniel Nachtrub notifications@github.com написал(а):
guys - option on Accoutn settigns - Forget User Session on Window Close is enabled?Not enabled here.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
guys - option on Accoutn settigns - Forget User Session on Window Close is enabled?
Disabled for me
Rc confgired with ldap? Отправлено с iPhone
…
11 апр. 2020 г., в 16:59, Daniel Nachtrub @.*> написал(а): guys - option on Accoutn settigns - Forget User Session on Window Close is enabled? Not enabled here. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
We're using LDAP authentication.
Rc confgired with ldap? Отправлено с iPhone
…
11 апр. 2020 г., в 16:59, Daniel Nachtrub @.*> написал(а): guys - option on Accoutn settigns - Forget User Session on Window Close is enabled? Not enabled here. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
Yes, I'm use LDAP sync for accounts and authentication.
Its strange. I use the same conf and set. No login errors
Отправлено с iPhone
11 апр. 2020 г., в 17:20, DJeremyy notifications@github.com написал(а):
Rc confgired with ldap? Отправлено с iPhone
…
11 апр. 2020 г., в 16:59, Daniel Nachtrub @.*> написал(а): guys - option on Accoutn settigns - Forget User Session on Window Close is enabled? Not enabled here. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.Yes, I'm use LDAP sync for accounts and authentication.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
I have LDAP enabled
Checking the console output from devtools on client it states:
Error logging in with token: Error: Login forbidden [403]
E2E -> Stop Client
I found a workaround in our environment:
By enabling Login Fallback the issues do not arise anymore.
Seems that there's an issue to recognize existing sessions here. Perhaps request is cancelled when login fallback is disabled and therefore even existing sessions using tokens can't be validated.
I found a workaround in our environment:
By enabling Login Fallback the issues do not arise anymore.
This is also the case for me @danielnachtrub, activating 'Login Fallback' in the LDAP section no longer causes connection problems on Android and iOS. I no longer have 'Invalid user' when I close the tab and open it again.
On 3.1.0 developers attache able to login without ldap if ldap is enabled and configured. So localy account
--
Gerasim Shaverdov | Deputy CTO | Altarix
Mobile:
Lenina av.25, Samara, Russia, 443068
From: DJeremyy notifications@github.com
Sent: Sunday, April 12, 2020 2:45 PM
To: RocketChat/Rocket.Chat Rocket.Chat@noreply.github.com
Cc: Шавердов Герасим Сергеевич gerasim@altarix.ru; Comment comment@noreply.github.com
Subject: Re: [RocketChat/Rocket.Chat] Login errors in 3.1.0 (#17259)
I found a workaround in our environment:
By enabling Login Fallback the issues do not arise anymore.
This is also the case for me @danielnachtrub https://github.com/danielnachtrub , activating 'Login Fallback' in the LDAP section no longer causes connection problems on Android and iOS. I no longer have 'Invalid user' when I close the tab and open it again.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/RocketChat/Rocket.Chat/issues/17259#issuecomment-612595625 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKOGQJUSW3KVH6MHOFQPMKDRMGLRHANCNFSM4MF6HPUQ .
Did everyone who had this problem uses LDAP?
If so, this may have been caused by #16949
We at Cloudron hit this as well now in our package tests. Those instances also use LDAP.
Did everyone who had this problem uses LDAP?
If so, this may have been caused by #16949
For me @pierre-lehnen-rc, I use LDAP. it seems to me that this is the case for everyone here.
I have same problem. LDAP auth enabled.
Same problem with LDAP, Also cannot use SAML.
Upgraded from 3.0.12 to 3.1.1, now both mobile apps (ios and android) crash on login with ldap users.
ldap fallback is enabled (was all the time)
Edit:
only the apps with version 4.6.x crash, version 4.5.1 works. Opened an issue for the app:
https://github.com/RocketChat/Rocket.Chat.ReactNative/issues/2054
the app just crash? no additional info? @diegolmello how can we track down what is happening in this case?
@sampaiodiego There's a fix on the way here
I am seeing it as well and referenced in #17318 where the Syncing process has failed thus locking out my users.
Most helpful comment
I found a workaround in our environment:
By enabling Login Fallback the issues do not arise anymore.
Seems that there's an issue to recognize existing sessions here. Perhaps request is cancelled when login fallback is disabled and therefore even existing sessions using tokens can't be validated.