Login via Groupoffice (OAuth) doesn’t work on the Starter Plan?

Community Support
1

Description

I have the Rocket.Chat 7.4.1 Docker image (yes, I know, it’s old) running on a Debian Buster server (yes, also old…). On another server, I have Group-Office. I want to log in to Rocket.Chat using my Group-Office account. I followed the instructions from the Group-Office documentation and configured everything exactly as described there. In the Community Edition of Rocket.Chat, login via Group-Office works, but it doesn’t work with the Starter Plan. Rocket.Chat API returns “User not found.” Why doesn’t it work with the Starter Plan?

Server Setup Information

  • Version of Rocket.Chat Server: 7.4.1
  • Operating System: Debian Buster
  • Deployment Method: Docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: 22.13.1 - x64
  • MongoDB Version: 6.0.13
  • Proxy: nginx
  • Firewalls involved: no
2

First thing is upgrade.

Your version 7.4.1 is out of support - min 7.4.5 and that is going EOL shortly the end of September.

Buster - EOL 10 Sep 2022

It’s not like you didn’t know. You’ve been running on a wing and a prayer since.

No one will help you on unsupported versions.

For your own safety & security get up to date. Fast.

———

I also don’t see Group Office in the docs? Which URL?

3

It is not due to Debian Buster and Rocket.Chat 7.4.1. The problem also occurs with Rocket.Chat 7.5.4 on Debian Bookworm. As soon as the Starter Plan is active, login via GroupOffice (OAuth) does not work. It works in the Community Edition.

The guide: https://groupoffice.readthedocs.io/en/latest/system-settings/rocket-chat.html#rocketchat

4

So again, you are not going to get support for unsupported systems and you should not be running them.

If you open a bug you will be asked to test on latest versions (and you’ll probably face me in triage so……)

Next, there is nothing in the Rocket docs so this a custom setup and you should check with GroupOffice if this still a supported option - it makes no mention of required Rocket versions. Rocket may have changed something that GO is not aware of.

It would also help if you posted any log errors when you test on latest - if they are long use something like pastebin so you don’t clog up the thread.

Thanks.

5

NB. I don’t work here - don’t shoot the messenger.

6

I found the problem. I need to disable the ‘Map Roles/Groups to channels’ option in the OAuth settings. It was enabled when switching to the Starter plan. In the Community Edition, this option is not available and is disabled by default — that’s why it worked there.
I tested it up to version 7.10.x and also with Debian 12 and Debian 13. Same behavior everywhere.
I don’t think it’s a real issue.
Anyway, it now works in the Starter plan as well. Thanks anyway.

7

Cool.

Yup that is a “Premium” setting.

For your own security get your upgrades done immediately.