REST API Rate Limit

[Testy]

Is there a way to add a delay to Saviynt when making multiple API calls? I'm getting a 429 error "too many requests". the limit is 12 requests every 6 seconds, how would i add this to the rest connector?

I added the below to the configJSON (and something similar to the ConnectionJSON) but no luck
"apiRateLimitConfig": {
"retryAfterCalls": 12,
"retryWaitSeconds": 6
}

[rushikeshvartak]

• Multiple call in which json ?
• above is used per user/ task.

[Testy]

1. ImportAccountEntJSON
2. used to import accounts/groups/group memberships

[rushikeshvartak]

It should work. Do you see any logs on api rate limit during import job execution 

[Testy]

"ecm-worker","2024-05-30T17:55:49.946+00:00","2024-05-30T17:55:49.670428414Z stdout F 2024-05-30 17:55:49,670 [quartzScheduler_Worker-5] DEBUG rest.RestProvisioningService - Got Webservice API Response: [headers:[Server: openresty, Date: Thu, 30 May 2024 17:55:49 GMT, Content-Type: application/json, Transfer-Encoding: chunked, Connection: keep-alive, Access-Control-Allow-Credentials: true, Access-Control-Allow-Headers: X-Requested-With, Origin, Content-Type, Accept, Accept-Language, Authorization, If-Modified-Since, X-Api-Key, Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS, PATCH, X-Request-Id: , Retry-After: 1], responseText:{"error_code":"429050","message":"Too many requests"}"

[rushikeshvartak]

This is target application response. Can you check logs printing saviynt sending delay request parameter 

[Testy]

what should i be looking for? there are quite a few things going on in the logs.

[NM]

Hi @Testy , look for the parameter which you have defined in config json .. "apiratelimitconfig"

[Testy]

Thanks, i found the below

[quartzScheduler_Worker-4] DEBUG integration.ExternalConnectionCallService - Key=ConfigJSON Value={"showLogs":true,"
"ecm-worker","2024-06-04T12:39:19.789+00:00","2024-06-04T12:39:18.912641038Z stdout F "apiRateLimitConfig": {"
"ecm-worker","2024-06-04T12:39:19.789+00:00","2024-06-04T12:39:18.912647637Z stdout F "retryAfterCalls": 12,"
"ecm-worker","2024-06-04T12:39:19.789+00:00","2024-06-04T12:39:18.912653337Z stdout F "retryWaitSeconds": 100"
"ecm-worker","2024-06-04T12:39:19.789+00:00","2024-06-04T12:39:18.912658937Z stdout F }"
"ecm-worker","2024-06-04T12:39:19.789+00:00","2024-06-04T12:39:18.912664537Z stdout F }"

[rushikeshvartak]

This should be called from connection Json and not from configJson

[Testy]

i deleted it from the configJSON and ran it only in the connectionJSON, however it did not show in the logs. 
i see this entry in the logs: rest.RestProvisioningService - Called API 10 times. So, keeping 100 sec sleep mode for next API call" 

but i might've seen that also when it was in the configJSON

[NM]

@rushikeshvartak , this document suggest to use it in config json https://docs.saviyntcloud.com/bundle/Okta-v23x/page/Content/Creating-an-integration.htm

[rushikeshvartak]

Its for Okta and not rest connection 

[Testy]

hi @rushikeshvartak not sure if you saw my message above but i deleted it from the configJSON and ran it only in the connectionJSON, however it did not show in the logs. 

[rushikeshvartak]

Does it works for provisioning use cases ?

[Testy]

We're not provisioning, just importing users and groups

[rushikeshvartak]

Refer https://forums.saviynt.com/t5/identity-governance/rest-connector-is-it-possible-to-introduce-wait-ti... 

"apiRateLimitConfig": {
"retryAfterCalls": 50,
"retryWaitSeconds": 60
}

[Testy]

@rushikeshvartak this is what I have in the ConnectionJSON but its still throwing the 429 error when importing users and groups
"apiRateLimitConfig": {
"retryAfterCalls": 12,
"retryWaitSeconds": 6
}