RocketChat / RocketChat/Rocket.Chat

6.3.0 Enterprise broken LDAP Background Sync Interval field

Open
#30,044 0 comments 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:

In previous 6.2.10, we used the Сron Text Parser expression to sync with LDAP 2 times a day at the correct time. In version 6.3.0 it is no longer possible to set your own expression, but there is only a choice of 5 options.

image

Steps to reproduce:

Open Administration->Settings->LDAP->Enterprise->Background Sync

Expected behavior:

Text input field supporting Cron Text Parser expressions

Actual behavior:

Drop down list with 5 options

Server Setup Information:
  • Version of Rocket.Chat Server: 6.3.0
  • Operating System: Oracle Linux Server release 8.6
  • Deployment Method: docker
  • Number of Running Instances: 20
  • DB Replicaset Oplog: yes
  • NodeJS Version: v14.21.3
  • MongoDB Version: 5.0.15 / wiredTiger (oplog Enabled)
Client Setup Information
  • Desktop App or Browser Version: Chrome 114
  • Operating System: Windows, Mac, Linux
Additional context

Our backgroun sync Cron Text Parser expression used: "at 21:00 also at 01:00"

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 in Administration → Settings → LDAP → Enterprise → Background Sync and compare the field behavior between versions 6.2.10 and 6.3.0. Restore support for Cron Text Parser expressions such as "at 21:00 also at 01:00", and verify that custom scheduling is available instead of only five dropdown options.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authentication
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.