Open nick-behrens opened 1 year ago
Hi @nick-behrens.
We always interpreted this as "The number of resources returned in a list response page.", not necessarily this list response page. An example of this can be found on page 74 of RFC7644 where the following example is given:
{
"totalResults":2,
"itemsPerPage":10,
"startIndex":1,
... etc
}
Description
RFC7644 describes the itemsPerPage value like this:
Currently, the itemsPerPage amount is set to
params.Count
, and when a partial page is retrieved the itemsPerPage doesn't equal the number of resources returned in a list response page.Examples
I recognize that consumers of the API could do the math (
totalResults - startIndex
) to figure out how many items are in the current page, but if I'm reading the spec correctly,itemsPerPage
should be the number of resources retrieved and not theCount
parameter.It looks like there is a split on this depending on the SCIM implementer. Okta, AWS, and Salesforce all seem to follow
itemsPerPage
equaling the number of resources but Azure keeps with what is implemented here, setting theitemsPerPage
to the count parameter.I'm more than happy to contribute a PR if we want to change the
itemsPerPage
to equal the number of resources in the page! I have a branch for that here.