I have been messing around with the list-identity-snapshot-access-items API endpoint and it appears that it only returns 250 results at a time.
The documentation in the API specs does not mention this, but it will accept your limit and offset query parameters allowing pagination. It does not appear to accept a sorters query parameter to ensure that you aren’t paginating through duplicate results.
Any thoughts on if this data is already sorted and we’d be fine to paginate through it?
Note that because the API specs don’t include offset/limit query parameters, you can’t use the Invoke-Paginate Powershell cmdlet in the SDK
invoke-paginate -function "get-betaidentitysnapshotaccessitems" -increment 250 -limit 10000 -initialoffset 0 -parameters @{"id" = "2c9180878043083b0180479fb9761ac0";"date" = "2024-02-24T03:06:17.845Z"; "type" = "entitlement"} | select displayName,sourcename
A parameter cannot be found that matches parameter name 'Limit'.
ConvertFrom-Json: C:\Users\mcheek\OneDrive - Chesapeake Energy\Documents\PowerShell\Modules\PSSailPoint\1.4.3\Pagination.ps1:58
Line |
58 | … when calling {1}: {0}" -f ($_.ErrorDetails | ConvertFrom-Json), $Func …
| ~~~~~~~~~~~~~~~~
| Cannot bind argument to parameter 'InputObject' because it is null.
If you want, you can modify the BetaIdentityHistory.ps1 file to make it accept limit and offset parameters so that you can use invoke-paginate. This is my modified version