I am building a web services SAAS connector to manage non-employee identities within ISC. Due to the limitation of 500 profiles being pulled with the get profiles API endpoint, I’ve had to configure paging for account aggregation. I am using the paging configuration (with the correct profile type id for my tenant) found at this link: Push or Pulled IDN users into NERM via API. I have 933 profiles to aggregate, and I am able to aggregate 852 accounts before I get the following error:
“java.lang.RuntimeException - java.lang.IllegalStateException: [ConnectorError] HttpClientWrapper.ts Response status :400 doesn’t match to allowed success codes : 200,2**,2**,2** response : {“error”:“no profiles found”}”
Any insight on what could be causing this and how it can be fixed?
Based on the error, the aggregation is failing because it did not get back a 200 or 2** status code. It was returned as a 400 status with the error “no profiles found”.
From that, it is likely that the offset value had gone beyond the number of profiles that is available based on the query parameters. Example for that error from my SB where I have 129 profiles but I set the offset to 700:
What is the paging increment being used in the http operation? In general, you should be safe to increment the offset by the limit each time and use a TERMINATE_IF clause to end the aggregation before you hit the “beyond offset” error .
