Webservice SaaS connector Pagination issue

Identity Security Cloud (ISC) ISC Discussion and Questions
1

Happy New Year !!

Looking for some help. I’m experiencing issue with Webservice connector … it is pulling maximum of 200 users wherein application got 8k users. Tried putting below paging steps but aggregation getting timed-out as soon as I increase the count from 200.

Without paging steps, aggregation only pulling 50 accounts.

TERMINATE_IF ($NO_RECORDS$ == TRUE) || ($RECORDS_COUNT$ < 200) $Index$ = $request.startIndex$ + 1 $endpoint.fullUrl$ = $application.baseUrl$ + “/scim/v2/users?count=200&startIndex=”+$Index$ $request.startIndex$=$Index$

2

Hi @NeetuDixit,

You may share your API response here, based on that i will guide you.

Thank you.

3

share your json and there is multiple way to set pagination.

4

Hello, can you try the following:

TERMINATE_IF ($NO_RECORDS$ == TRUE) || ($RECORDS_COUNT$ < 200) $Index$ = $request.startIndex$ + 1
$endpoint.fullUrl$ = $application.baseUrl$ + “/scim/v2/users?count=200&startIndex=” + $Index$
$request.startIndex$ = $Index$

regards,
Pablo

5

Hi @NeetuDixit ,

Happy New Year,

If you can share the API response, we will be able to help you better.

-Mehul

6

This is the user api response, I can see via Postman:

image
image978×711 31 KB

1 Like
7

@NeetuDixit Please use like below , just double check url(full url), also no need to mention count in request end point as you are getting only 50 default. So just use like below it will resolve your issue:-
$limit$ = 50
TERMINATE_IF $RECORDS_COUNT$ < $limit$
$startIndex$ = $startIndex$ + $limit$
$endpoint.fullUrl$ = $application.baseUrl$ + “/scim/v2//Users?startIndex=” + $startIndex$

8

Afraid to say but this is also only aggregating 50 users.

9

this one is not working either :frowning:

10

Hi @NeetuDixit,

I found this topic can you check whether its helpful Issues with WS Pagination - Identity Security Cloud (ISC) / ISC Discussion and Questions - SailPoint Developer Community

-Vasanth

11

You may share next page result screenshot as well. to guide better because i see in this screenshot you’re not using params like limit and offset or startIndex.

Try below paging rule and let me know if there is any issue:

$limit$ = 50
TERMINATE_IF $RECORDS_COUNT$ < $limit$
$startIndex$ = $response.startIndex$ + $limit$
$endpoint.fullUrl$ = $application.baseUrl$ + “/scim/v2/Users?startIndex=” + $startIndex$

Thank You.

12

You need to identify the pagination attribute supported by the API. By default, it might be startIndex, but some APIs use their own formats, such as _pageIndex. Once you identified the pagination attributes of the API, you can use the above pagination tab steps as a base and modify them accordingly.

13

@NeetuDixit please share task result just want to check something…Also please let me know your base url and url u configure in get API in conifguration

14

@NeetuDixit I had similar issue which got fixed, similar to what @gogubapu suggested, you can find the info from WebService connector rule add error - Identity Security Cloud (ISC) / ISC Discussion and Questions - SailPoint Developer Community

15

Thanks Himanshu !!
But somehow this is not working for me and were able to aggregate only 50 accounts.

16

image
image1289×549 17.2 KB

17

@NeetuDixit this is not a valid paginge step you have mentioned
/centers after that ? startIndex=$offset

18

@mkumariaas ,

I didn’t understand where the problem is, can you explain in more detail?

-Mehul

19

Hi Neetu,
Please use the below pagination logic.

$sysparm_limit$ = 100
TERMINATE_IF $RECORDS_COUNT$ < $sysparm_limit$
$sysparm_offset$ = $sysparm_offset$ + 1
$endpoint.fullUrl$ = $application.baseUrl$ + "/scim/v2/users?count=100&startIndex=" + $sysparm_offset$

Regards,
Georgi

20

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.