ISC Retry Mechanism - Failed Provisioning Behavior for Access Requests

[sushantkulkarni]

Hi everyone,
Have you configured retry provisioning mechanism for failed access requests? Is it possible?

Scenario:

• A user requests for certain access (role, access profile or entitlement)
• Request goes through multi-level approvals as configured
• Request goes through to provisioning
• Request fails during provisioning due to an error, say connection timeout (could be anything else)
• Access request is now “complete” but failed to provision the access.

In such a scenario, can retry configurations work to try and re-provision this failed access request, and if the retry successfully provisions, does the access request status change to reflect this? Say, from ‘completed with failed provisioning’ to ‘completed successfully’?

Or, does the retry create a new access request (if at all it is retried) and that request is auto-approved because the previous one was approved?

[ramrangasamy87 (Ram Rangasamy)]

Hi Sushant,

This is possible. All you need to do is, configure the provisioning retries in the source under “connectorAttributes” as shown below.

retryableErrors:

[
{
“op”: “add”,
“path”: “/connectorAttributes/retryableErrors”,
“value”: [“InvalidConfigurationException”,“Connection reset”,“Read time out”]
}
]

provisioningRetryThreshold:

[
{
“op”: “add”,
“path”: “/connectorAttributes/provisioningRetryThreshold”,
“value”: “1”
}
]

provisioningMaxRetries:

[
{
“op”: “add”,
“path”: “/connectorAttributes/provisioningMaxRetries”,
“value”: “3”
}
]

once you have configured it, if the access request fails, the source will retry and provision the request.

Note: All the possible error need to be captured in the retryableErrors, otherwise they won’t be retried.

Regards,
Ram