Generic REST Collector fails with 'Could not read the value for path(s) in response: $.['@odata.nextLink')' in RSA Identity Governance & Lifecycle
Originally Published: 2020-06-19
Article Number
Applies To
RSA Version/Condition: 7.2.0
Issue
Test REST API request returned 190 record(s)
Could not read the value for path(s) in response: $.['@odata.nextLink')
Probable Cause: Either the path(s) configured is/are incorrect OR it contains null or empty value.
Could not read the value for path(s) in response: $.['@odata.nextLink')
Probable Cause: Either the path(s) configured is/are incorrect OR it contains null or empty value.
Cause
This issue occurs if the number of data rows being returned are less than the configured page size (i.e., the configured page size is equal to or greater than the number of records returned.)
In this example, a generic REST collector is configured to collect 190 accounts from Azure and the page size is set to 999. When the page size is configured to be equal to or greater than 190, the collector will fail with the above error. Page size is configured in the collector definition (Collectors > {Collector type} > {Collector name} > Edit).
Resolution
- RSA Identity Governance & Lifecycle 7.2.1
Workaround
Related Articles
1 Virtual Disk(s) Degraded error or 1 Virtual Disk(s) is in Critical State error displays when RSA SecurID A250 Hardware A… 41Number of Views Generic REST AFX Connector fails with ValidationError in RSA Identity Governance & Lifecycle 133Number of Views Startup fails with Initialization Status error message 'Found invalid object(s) in the database' after migration or patchi… 988Number of Views How to publish CA certificate and user certificate under the same OU ? 8Number of Views Configure the SMTP(s) Mail Service 173Number of Views
Don't see what you're looking for?