Use of the API to configure All Users group universal permissions results in HTTP 400

Self Hosted Retool
1

We are using self-hosted (3.33 Stable) and trying to use the API to configure groups.

We have found that while it is possible to control the universal permissions of the All Users group via the UI it is not possible to do this via the API.

We get an HTTP 400 Bad Request with the message Cannot update the membership of group: All Users. even though we are not trying to change the membership at all and are passing no membership element into the API.

2

UPdate to add we have tried both PATCH Update Group and PUT Update Group and both result in the same message.

3

Hey @CPU! I'd be curious to see how you've written your queries. It's not very intuitive - to me, at least - but I was able to get it to work with an API key that has read/write access for "Users", "Groups, and "Permissions" scopes.

You can see the before, after, and details of the query below. I didn't quite capture it but the first query is a 'GET' request. :+1:

Screenshot 2024-08-13 at 6.04.58 PM
Screenshot 2024-08-13 at 6.04.58 PM1082×1038 87.8 KB
Screenshot 2024-08-13 at 6.06.28 PM
Screenshot 2024-08-13 at 6.06.28 PM1056×1488 117 KB

I didn't test any additional combination of scopes when generating the API key, but I imagine that at least read/write for "Groups" and "Permissions" would be required.

Definitely let us know if you continue to have trouble with this!

4

My API Key has all permissions assigned. Here's an example

Request: patch /api/v2/groups/4
Request Body: {
  "operations": [
    {
      "op": "replace",
      "path": "/universal_resource_access",
      "value": "edit"
    }
  ]
}
Error: Error applying change: {"op":"UPDATE","type":"group","name":"All Users","data":[{"op":"replace","path":"/universal_resource_access","value":"edit"}],"id":4,"scope":"All Users"}: Error: Failed to patch group: 422 {"success":false,"message":"Cannot update the membership of group: All Users."}
5

Hmm that's certainly odd. :thinking: I was specifically using version 3.33.37-stable when testing on my end, but the queries are pretty much identical.

I'm going to loop a few others into the conversation to hopefully brainstorm what might be going on here. In the meantime, can you try modifying another group just to see if it's solely an issue with "All Users"? Appreciate your patience!

If you're able to, I'd also recommend updating to the latest stable patch.