Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LDAP - User not found - since 4.5.0 (aka better logging needed) #24694

Open
sgohl opened this issue Mar 3, 2022 · 2 comments
Open

LDAP - User not found - since 4.5.0 (aka better logging needed) #24694

sgohl opened this issue Mar 3, 2022 · 2 comments

Comments

@sgohl
Copy link

sgohl commented Mar 3, 2022

Description:

Since Upgrade to 4.5.0, I see those messages in logs while I was checking because some users said they can't login anymore (LDAP)

Steps to reproduce:

I don't really know. It just happened since upgrade to 4.5.0 that some users can't login anymore and I suspect the error message is related to the problem - but not necessarily. It's a guess.

Expected behavior:

mention the username in the log

Actual behavior:

Login page flashes a red warning at top right, that the user can not be found or the password may be wrong.

Server Setup Information:

rocketchat_app.1.1jvo3f3rpvge@rocketchat    | +-----------------------------------------------------+
rocketchat_app.1.1jvo3f3rpvge@rocketchat    | |                    SERVER RUNNING                   |
rocketchat_app.1.1jvo3f3rpvge@rocketchat    | +-----------------------------------------------------+
rocketchat_app.1.1jvo3f3rpvge@rocketchat    | |                                                     |
rocketchat_app.1.1jvo3f3rpvge@rocketchat    | |  Rocket.Chat Version: 4.5.0                         |
rocketchat_app.1.1jvo3f3rpvge@rocketchat    | |       NodeJS Version: 14.18.3 - x64                 |
rocketchat_app.1.1jvo3f3rpvge@rocketchat    | |      MongoDB Version: 5.0.6                         |
rocketchat_app.1.1jvo3f3rpvge@rocketchat    | |       MongoDB Engine: wiredTiger                    |
rocketchat_app.1.1jvo3f3rpvge@rocketchat    | |             Platform: linux                         |
rocketchat_app.1.1jvo3f3rpvge@rocketchat    | |         Process Port: 3000                          |
rocketchat_app.1.1jvo3f3rpvge@rocketchat    | |             Site URL: https://chat.xxxx.xxx  |
rocketchat_app.1.1jvo3f3rpvge@rocketchat    | |     ReplicaSet OpLog: Enabled                       |
rocketchat_app.1.1jvo3f3rpvge@rocketchat    | |          Commit Hash: 3901054684                    |
rocketchat_app.1.1jvo3f3rpvge@rocketchat    | |        Commit Branch: HEAD                          |
rocketchat_app.1.1jvo3f3rpvge@rocketchat    | |                                                     |
rocketchat_app.1.1jvo3f3rpvge@rocketchat    | +-----------------------------------------------------+

Client Setup Information

  • Desktop App or Browser Version: both
  • Operating System: any

Additional context

LDAP Server is Active Directory. In the Administration/LDAP page, using the buttons at the top - "test connection" and "Test LDAP search" are succesful, user can be found (green flash message)

Relevant logs:

rocketchat_app.1.1jvo3f3rpvge@rocketchat    | {"level":50,"time":"2022-03-03T15:29:13.266Z","pid":1,"hostname":"f9c9770d540f","name":"","name":"LDAP","err":{"type":"Error","message":"User not found","stack":"Error: User not found\n    at server/lib/ldap/Manager.ts:167:11\n    at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40"},"msg":"User not found"}

I started a LDAP background sync some hours ago which should be very much finished by now, but didn't solve.

After upgrading to 4.5.0 I had this index problem which prevented the server from starting, so I executed the statements from #24347 (comment) in the mongo primary.
Perhaps this has got something to do with it? I tried restarting rocketchat server hoping it will re-run migrations or create index, but at least it didn't tell

@basskitty
Copy link

Same here, a user notified me that he changed his AD password 2 weeks ago and cannot login with the new one, but the old password is still working.

Mar 14 11:06:23 ourhostname rocketchat[11829]: {"level":50,"time":"2022-03-14T10:06:23.758Z","pid":11829,"hostname":"ourhostname","name":"","name":"LDAP","err":{"type":"Error","message":"User not found","stack":"Error: User not found\n    at server/lib/
Mar 14 11:06:23 ourhostname rocketchat[11829]: {"level":50,"time":"2022-03-14T10:06:23.876Z","pid":11829,"hostname":"ourhostname","name":"","name":"System","msg":"Exception while invoking method login 'User not found [403]'"}
Mar 14 11:06:32 ourhostname rocketchat[11829]: {"level":50,"time":"2022-03-14T10:06:32.583Z","pid":11829,"hostname":"ourhostname","name":"","name":"LDAP","err":{"type":"Error","message":"User not found","stack":"Error: User not found\n    at server/lib/
Mar 14 11:06:32 ourhostname rocketchat[11829]: {"level":50,"time":"2022-03-14T10:06:32.692Z","pid":11829,"hostname":"ourhostname","name":"","name":"System","msg":"Exception while invoking method login 'User not found [403]'"}
Mar 14 11:06:37 ourhostname rocketchat[11829]: {"level":50,"time":"2022-03-14T10:06:37.023Z","pid":11829,"hostname":"ourhostname","name":"","name":"LDAP","err":{"type":"Error","message":"User not found","stack":"Error: User not found\n    at server/lib/

I'll update to 4.5.2 tomorrow and hope this is being fixed but I've read nothing about this password issue so far.

@basskitty
Copy link

Problem still exists in 4.5.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants