Hi everyone,
During deprovisioning/disabling with our RACF connector, we have an additional rule that writes to a custom field that indicates that SailPoint has performed the revoke. This allows us to use this custom field as a filter and append a date to it, so that after a certain period of time the account is deleted. However, we have run into the issue where if the account is already revoked, this process breaks because it cannot revoke an ID that is already revoked. This is what it is currently sending to RACF: ALU <USERID> REVOKE CSDATA(<CustomField> (<String>))
I wanted to ask, how are others handling their RACF Revoke/Delete process? Is there a way to get around this issue? What we are thinking of was doing ALU <USERID> NOREVOKE RESUME REVOKE CSDATA(<CustomField> (<String>)) but is this possible with the ISC Connector?