Marwan Shaher
27 minutes ago
if I’m reading the response correctly in the logs, it doesn’t look like the count is actually included:
{"totalResults":1,"startIndex":1,"itemsPerPage":1,"resources":[{"id":"24b511ab-9f66-4010-b43c-b1b1015b2e8d","meta":

{"resourceType":"Group","created":"2024-07-18T21:04:03.023Z","lastModified":"2024-07-18T21:04:03.023Z"}

,"displayName":"shaherTest20240718001","externalId":"50091cfbde8d46c99311cd401b9c57be","schemas":["urn:ietf:params:scim:schemas:core:2.0:Group"]}],"schemas":["urn:ietf:params:scim:api:messages:2.0:ListResponse"]}
The next line in the logs makes me think that both the count and startIndex aren’t included:
HTTP URL: https://scim.bitwarden.com/v2/xxxxxxx-XXXXX-XXXXXX/Groups?filter=displayName%20eq%20%22shaherTest20240718001%22 (edited)

Chris Hyzer
24 minutes ago
if it is searching for a specific group, then they arent included, since that should generally return 1 group. does your endpoint need paging for that? what are you talking to?
New

Marwan Shaher
22 minutes ago
I think this is specific to a “broken” application that I’ve been trying to get it work with Grouper. It’s Bitwarden. From my tests with doing similar calls with curl, every call, no matter what it is, needs to have both the count and startIndex in there.

Chris Hyzer
20 minutes ago
ok well, we can add that