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

GET users.list broken for "normal" users #25728

Closed
mb987654 opened this issue Jun 2, 2022 · 2 comments · Fixed by #26050
Closed

GET users.list broken for "normal" users #25728

mb987654 opened this issue Jun 2, 2022 · 2 comments · Fixed by #26050
Assignees

Comments

@mb987654
Copy link

mb987654 commented Jun 2, 2022

Description:

When trying to perform a GET against /api/v1/users.list with no query parameters, the following response is returned for users who do not have a role that includes the "View Full Other User Info" permission:

{
"success": false,
"error": "Invalid attribute: emails.address [error-invalid-query]",
"errorType": "error-invalid-query"
}

If a user has a role that includes the "View Full Other User Info" permission, then the error does not occur and a list of users is returned as expected.

Steps to reproduce:

  1. perform a GET against /api/v1/users.list as a user that has no roles that include the "View Full Other User Info" permission

Expected behavior:

a list of users is returned

Actual behavior:

an error is returned:

{
"success": false,
"error": "Invalid attribute: emails.address [error-invalid-query]",
"errorType": "error-invalid-query"
}

I did not have this problem with 4.7.0.

Server Setup Information:

  • Version of Rocket.Chat Server: 4.8.0
  • Operating System: CentOS
  • Deployment Method: docker-compose
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: 14.18.3 - x64
  • MongoDB Version: 4.0.28
@debdutdeb debdutdeb self-assigned this Jun 8, 2022
@Gummikavalier
Copy link

Gummikavalier commented Jun 13, 2022

RC 4.7.4 seems to suffer from this too.
Edit: Ignore regarding 4.7.4. My bad. Something other has just changed in the parameters or their syntax. And more likely in what sort of hyphens can be read.

@gelpiu-developers
Copy link

gelpiu-developers commented Jun 14, 2022

Has anyone solved this? I'm having the exact same problem, and I don't find anything in the documentation explaining why this is not working now...

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