Webservice Paging

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

We have a Web Service connector configured in SailPoint IdentityNow, and we’re encountering an issue with account aggregation.

Currently, the first API call retrieves the initial 2000 records. The response of this first call includes the URL for the next page in the field d.nextpage. Below is an example of the response:

{
“d”: {
“__type”: “FOUND”,
“nextpage”: “https://eupsrob.abc.com/automation/robots_api.asmx/NUATFull?RecordCount=10&PageGuid='MTjvt”,
“useridlist”: [
{
“userid”: “CL0AP000”,
“useridType”: “PERSONAL”,
“useridBelongsToEIN”: “1234567”,
“useridStatus”: “HISTORIC”,
“useridToHistoric”: “26/06/2020 19:15:00”
},
{
“userid”: “CL0PM000”,
“useridType”: “PERSONAL”,
“useridBelongsToEIN”: “987654”,
“useridStatus”: “HISTORIC”,
“useridToHistoric”: “10/03/2021 19:36:00”
}
]
}
}

We would like to understand how to configure paging in the connector so that subsequent calls automatically follow the d.nextpage URL until all records are retrieved.

I have tried $.d.nextpage, it is scanning accounts but not bringing in any. Could you please suggest the best approach to handle this type of pagination in IdentityNow?

Thank you for your help.

2

HI @sandashafreen26 !

Can you please share the paging steps/logic you have tried?

Here is an example from one of our connectors that would return 5,000 records, then provide a link for the next page of results.

image
image409×216 2.83 KB

Please let me know if the below Paging Steps works for you:

TERMINATE_IF $RECORDS_COUNT$ < 2000
$endpoint.fullUrl$ = $response.d.nextpage$

Thank you,

  • Zach