I’m attempting to aggregate accounts from a WebService endpoint I need to page through by setting a request header of the next query to the value of a response header that was returned in the previous response. The “Paging Tab Configuration” page ( Paging Tab Configuration (sailpoint.com)) of the WebServices connector doc indicates that the “requestHeaders” and “responseHeaders” are both keywords, and the “Paging Based on Response Header Links” page ( Paging Based on Response Header Links (sailpoint.com)) shows how the “responseHeaders” object is used in paging.
My requirement doesn’t match up perfectly, but I took a swing and came up with this in the “Paging Steps” configuration of my account aggregation call:
TERMINATE_IF ( $responseHeaders.offsetToken$ == NULL ) || ($responseHeaders.offsetToken$ == "" )
$requestHeaders.offsetToken$ = $responseHeaders.offsetToken$
It doesn’t work and seemingly would run forever if I let it. I’m guessing because I can’t set the “requestHeaders” object values at this point it’s just repeatedly fetching the first 200 results. Has anybody run into this type of approach before? I suspect I’m going to have to come up with a rule-based approach for this, but hoping somebody here can help me identify something I’ve missed.