Hi,
We are integrating the Tivoli Directory Service with RSA IG&L where the AFX connector will be used to create/update/disable users in TDS.
There is a scenario where the TDS system will be shutdown once a day, per month for scheduled maintenance. What would be the best solution so that, even if the end point is down, the AFX can retry the request later.?
Hi,
Unfortunately, there are no retry system at this moment for the AFX.
They are working on it but I don't remember if they have given estimation release.
You have to switch to provisioning nodes or resubmit the entitlement.
Has someone used a provisioning command node, get the provisioning status and based on the status (say, if it says the end point is unavailable) give a time delay, attempt it again. ?
Not sure what status the provisioning command node throws if the endpoint is unreachable or if it gets stuck at that provisioning node if the endpoint is unreachable.
Is there a workaround to this issue by making use of provisioning command nodes.?
Although there is no native retry AFX capability, you can force it though in your fulfillment workflow with the following process. Be aware, this deletes records from the main application database tables and as such is unsupported by RSA.
SQL 1
SELECT crd.state as request_state
FROM pv_change_request cr
INNER JOIN pv_change_request_details crd ON cr.id = crd.change_requests_id
WHERE
cr.name = '${access_request_name}'
AND crd.id = '${jobUserData_ChangeRequestItemx2ExItemId}'
SQL 2
DELETE FROM t_av_afx_request_history
WHERE request_id IN (
SELECT id
FROM t_av_afx_request
WHERE
change_item_id = '${jobUserData_ChangeRequestItemx2ExItemId}'
)
SQL 3
DELETE FROM t_av_afx_request
WHERE
change_item_id = '${jobUserData_ChangeRequestItemx2ExItemId}'
FYI, related idea: AFX Retry Mechanism