We’ve integrated one of the application using webservice out of the box connector. Currently during aggregation, we started seeing 503 service unavailable error. The application has limited the integration 5/10 (RPS/Burst) limits. How can we handle this on SailPoint side. Anyone has done this type of similar implementation.
Even this is happening during attribute sync as well.
Thanks in advance for the inputs!
Please consider addressing the following when creating your topic:
What have you tried?
What errors did you face (share screenshots)?
Share the details of your efforts (code / search query, workflow json etc.)?
What is the result you are getting and what were you expecting?
Are you able to increase the limit in your use case? One thing I have noticed with NERM using the WebServices connector is that if the page ends on last record on the page it will error out. Using your screen print say the page ended on record 6049 as there are not more records the server errors with a similar error message. Fix has been add another record.
I’m using webservice before operation rule for the update account operation for the attribute sync, where in I’ve to fetch the user mandatory attributes by using Get User API calls to update the identity attributes and also handling to update the additional attributes using another API calls. For aggregation also I’m using the rule
This is nothing to do with the pagination limit. This is more of request per second, which we need to configure at our end. The application team configuration handled 5/10 RPS for this integration, they can able to send the proper error message to distingusih if required.
Just like you have rule for updating attributes, you can have a rule for aggregation. See how you have put a delay in for making the updates, do the same thing when you are aggregating. Authenticate to the source, start the data collection, get a first set of data, delay, get the next set of data, delay, get the next set of data.
You do not have to have anything configured on the webservices aggregation section in ISC. Just write a rule and attach it to the aggregation.
I’ve attempted to use Thread.Sleep(), but its not allowing to save the file and warning to remove this.
‘idn://***.identitynow.com/beta/connector-rule-script/7337d2f73b9842139659697519acdf1a/Rule-WebServiceAfterOperation-PACE-Aggregation’ (Error: Illegal value “[{“line”:90,“column”:29,“message”:“Remove reference to Thread”}]” for field “sourceCode.script”.)