RocketChat / RocketChat/Rocket.Chat
Global option for limiting invite expiry time
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Currently RC does not have an admin option to limit the expiry time of the channel owner created invitations.
Invitations are a good and necessary feature in an email provisioned service. But on RocketChat services that are hosted for less educated users the users often create never expiring invitations needlessly and carelessly.
Because the invitation urls are too short and simple, it is very easy for a malicious actor to arrange a long running harvest operation to find out the forgotten never expiring invite links.
It would be preferable that administrators would have a global option to disable never expiring token length from the options of the invite links.
Another solution to the same problem would be that the links would be much longer and hence harder to harvest.
Steps to reproduce:
- Create a channel
- Create an invite link
- Set the expiry time to never in the invite link
Expected behavior:
It would be preferable that never expiring invite links would not be possible to create haphazardly.
Actual behavior:
Any channel owner or moderator can create never expiring invite links.
Server Setup Information:
- Version of Rocket.Chat Server: 6.5.0
- Operating System: RHEL8
- Deployment Method: tar
- Number of Running Instances: 10
- DB Replicaset Oplog: Yes
- NodeJS Version: 14.21.3
- MongoDB Version: 5.0
Client Setup Information
- Desktop App or Browser Version: any
Additional context
A workaround for this problem is to clean up the database of any never expiring links using scripts. Or by deleting them manually under Administrator -> Invites.
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 channel invite creation and the Administrator → Invites area described in the issue, then identify where invite expiry choices and global settings are handled. Define the administrator-controlled maximum expiry, prevent channel owners and moderators from creating links beyond it, and add coverage showing that never-expiring links are blocked when the limit is configured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100