Currently, we’re building a connection to a web service using the Web Services SaaS connector connector (not to be confused with SaaS Connectivity). It seems however, that there is a limitation in the processing of the data, since we get a “Command timed out” error message when we start to map a lot of the data.
According to this post it seems it must be a setting in IdentityNow (that we cannot change ourselves)?
Is there another way out, besides implementing pagination?
SaaS connectivity doesn’t have unlimited memory, so you have to use pagination to process large amounts of identities. If running out of memory isn’t your issue, and your command is just taking longer than 3 minutes to process the request, then you can issue an res.keepAlive() in your code to keep the command from timing out. Please see this doc for more information.
This is NOT a custom connector, so I don’t have any code here. This is using the Web services SaaS connector from SailPoint. Any idea if there is a way to force the keepAlive in that connector?
Oh, sorry about that. When you said “SaaS based web service connector” I thought you were referring to SaaS connectivity. You’re talking about the VA based web service connector.
You should be able to increase the timeout of VA connectors. Follow the solution here:
I think the only way the new SaaS based webservices connector will keep the connection alive is if you send a response within 3 minutes, usually done through pagination logic. Otherwise it will timeout. For any complex webservice calls that need to be made, we recommend to simply create a custom connector using the SDK.