Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[3.1.0] error-invalid-room after room creation with LDAP logged admin #17296

Closed
CodazziS opened this issue Apr 14, 2020 · 1 comment
Closed

Comments

@CodazziS
Copy link

Description:

After creating a new private room, we can't open the room. We need to logout / login for join the room.

Steps to reproduce:

  1. With an admin LDAP account, create new private room.
  2. When room is created, the url change for open the room, and an error message invalid room appear.
  3. With a logout / login, we can join the room

Expected behavior:

The room must appear without error. Room creation work with a regular admin (non-ldap logged).

Actual behavior:

  • step 1:
    image
  • step 2:
    image

Server Setup Information:

  • Version of Rocket.Chat Server: 3.1.0
  • Operating System: Debian 9
  • Deployment Method: tar
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version: v12.16.2
  • MongoDB Version: 4.0.16

Client Setup Information

  • Desktop App or Browser Version: Browser
  • Operating System: Ubuntu

Additional context

Admin user is logged with LDAP

Relevant logs:

  • client console error:
details: {method: "canAccessRoom"}
error: "error-invalid-room"
errorType: "Meteor.Error"
isClientSafe: true
message: "Invalid room [error-invalid-room]"
reason: "Invalid room"```
- No error for server
@rodrigok
Copy link
Member

@CodazziS this will be solved by #17282 on version 3.1.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants