RocketChat / RocketChat/Rocket.Chat

Random amounts of idle time causes logouts

Open
#8,449 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

User

Server Setup Information:

Runs in Docker

I20171005-21:36:12.830(0) ➔ |                                              | 
I20171005-21:36:12.830(0) ➔ |  Rocket.Chat Version: 0.58.3                 | 
I20171005-21:36:12.831(0) ➔ |       NodeJS Version: 4.8.4 - x64            | 
I20171005-21:36:12.831(0) ➔ |             Platform: linux                  | 
I20171005-21:36:12.831(0) ➔ |         Process Port: 3000                   | 
I20171005-21:36:12.832(0) ➔ |             Site URL: https://rc.pkware.com  | 
I20171005-21:36:12.832(0) ➔ |     ReplicaSet OpLog: Disabled               | 
I20171005-21:36:12.833(0) ➔ |          Commit Hash: bd331177ef             | 
I20171005-21:36:12.833(0) ➔ |        Commit Branch: heads/0.58.3           |
Steps to Reproduce:
  1. Open Administation | LDAP
  2. Set LDAP Idle Timeout (ms) to be : 3600000
  3. Minimized Rocket Chat and in under 1 hour, the session will be logged out.
Expected behavior:

The value entered is respected as the timeout and activity resets it.

Actual behavior:

The user session is logged out before the value is reached.

Relevant logs:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at Administration > LDAP and trace how the LDAP Idle Timeout value is stored and applied to the user session. Reproduce the Docker setup with a 3600000 ms timeout while the client is minimized, then compare the observed logout time with the configured value. Done means the configured timeout is respected and activity resets it.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, 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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.