RocketChat / RocketChat/Rocket.Chat
Blocking a user in LDAP does not disable the account in RocketChat
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Blocking a user in LDAP does not disable the account in RocketChat
the user was blocked a week ago, LDAP synchronization works and was successful, but the account works from the computer where the user was authorized before blocking
Steps to reproduce:
- Customize LDAP integration(I use Microsoft AD)
- Login LDAP account
- Block users(in LDAP)
- Force integration
- Account will continue to work
Expected behavior:
the user should be logged out when re-accessing the server
Actual behavior:
User can chat
Server Setup Information:
- Version of Rocket.Chat Server: 3.14.1
- Operating System: ubuntu 20.04
- Deployment Method: tar
- Number of Running Instances: 1
- DB Replicaset Oplog:
- NodeJS Version: v12.21.0
- MongoDB Version: 4.0.23 / mmapv1
Client Setup Information
Any operating system, tested in Google chrome browser
Additional context
I believe that when a blocked LDAP account is detected, the associated rocket chat account should also be blocked
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the LDAP integration synchronization described in the reproduction steps and how an existing Rocket.Chat session checks account status. Reproduce the blocked-account flow with the stated LDAP setup, then verify that synchronization prevents further chat access and logs the user out when they access the server again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100