Rocket.Chat's Community Open Call 🎤 Dec 15, 2021 Join us!

Am I safe to update to 4+ (ldap)

Description

I am using LDAP authentification without fallback login and without LDAP goups etc.
Actually nur basic auth
Ldap config is: ou=chat,dc=Example,dc=com

Am I safe to update it to 4+ Version? Will my LDAP auth still working ?

Server Setup Information

  • Version of Rocket.Chat Server: 3.18.1
  • Operating System: Debian
  • Deployment Method: manual
  • Number of Running Instances: 1

hi! Welcome to our forums!

You should be ok.

The functionalities that were moved to EE in 4.X are advanced sync.

The users should only be added/synced with Rocket.Chat when they actually login.

Please, before upgrading, do the backups. Also, if possible, try doing some tests on a testing environment before with the upgrade.

Thanks!

1 Like

Thanks Sir, Ill give a try. I have possibility to snapshot server manually or use one of my hourly snapshots , so reverting changes ist one click thing.

I hope this basic auth will be working after update to 4.x … I am happy with rocket chat, supporting them on github, but those license EE prices are insane … If ldap not working anymore, ill check other concurrent products …

Everything moved to EE can still be done with some scripts and using the API.

I have some deployments myself, and only use the LDAP for login. User data sync and channels/teams/role mapping I do using python script. It connects to the LDAP and then consume Rocket.Chat’s API for that.

I think it’s better, because you have more control. For example, I have non mandatory channels (#company-pets, #company-fun, etc) that I only add users once they first enter the company.

is there any chance to share your script ?

It’s totally attached to a custom ERP.

but the idea is really simple, and with the below python libs is just a matter of scripting.

I have used these libs:

and:

with those two you can get data from ldap and consume Rocket.Chat apis.

regarding python rocketchat, it may not have all the methods, but you can call them adhoc, like:

            payload = {
            }
            rocket.call_api_post("integrations.create", **payload)
1 Like