[scim] Concerns Regarding Cursor-Based Pagination

["Bojitha Piyathilake (intern)" <[e-mail]>]

Hi all,

I am in the process of implementing cursor based pagination for WSO2
Identity Server, which is a SCIM service provider that supports SCIM 2.0. I
have encountered a few concerns and would appreciate any feedback.

Question 1

In the Cursor-based Pagination of SCIM Resources draft
<https://datatracker.ietf.org/doc/html/draft-peterson-scim-cursor-pagination-00#section-2>
[1], it hasn’t been mentioned how to handle an unspecified count. Am I
right to assume this can follow the same, as per RFC - 7644
<https://datatracker.ietf.org/doc/html/rfc7644#section-3.4.2.4> [2] which
states, “If unspecified, the maximum number of results is set by the
service provider”?

Question 2

In a situation where we wish to provide both cursor based pagination and
index based pagination in the same SCIM service provider, how would you
suggest the user decide the pagination approach? RFC - 7644
<https://datatracker.ietf.org/doc/html/rfc7644#section-3.4.2.4> [2], states
that both the startIndex value and the count are optional parameters when
making the first offset based request. startIndex will be defaulted to 1
and the count will be defaulted to the value specified by the service
provider. Furthermore, Cursor-based Pagination of SCIM Resources draft
<https://datatracker.ietf.org/doc/html/draft-peterson-scim-cursor-pagination-00#section-2>
[1], states that the cursor value of the initial request should be omitted.

eg:

Possible first request for offset pagination: /scim2/Users?count=20 ->
Offset will be defaulted to 1.

Possible first request for cursor pagination: /scim2/Users?count=20 ->
Initial cursor is omitted.

The SCIM service provider fails to distinguish the pagination mechanism
that the user wants for these requests.

Question 3

When querying for resources using a POST request combined with the
"/.search" path extension, the query params will be contained in the
request body. How should the cursor attribute be passed? This point is not
mentioned in the Cursor-based Pagination of SCIM Resources draft
<https://datatracker.ietf.org/doc/html/draft-peterson-scim-cursor-pagination-00#section-2>
[1]

{

  "schemas": [

    "urn:ietf:params:scim:api:messages:2.0:SearchRequest"

  ],

  "filter": "userName sw A",

  "domain": "PRIMARY",

  "count": 10,

  "cursor": "eyJ2YWx1ZSI6IlNDSU0yQ1"

}


[1]
https://datatracker.ietf.org/doc/html/draft-peterson-scim-cursor-pagination-00#section-2

[2] https://datatracker.ietf.org/doc/html/rfc7644#section-3.4.2.4


-- 
*Bojitha Piyathilake* | Software Engineering Intern | WSO2 Inc.
(m) [phone] | (e) [e-mail]

<http://wso2.com/signature>
[image: http://wso2.com/signature]
<http://wso2.com/signature>