I have implemented the before provisioning rule, it deleted the application from the user once the lifecycle state changes to inactive, however the account is not deleted from the target system. I have implemented the HTTP delete operation as well. Perhaps my schema is not fine.
Note: The body successfully works as well as the endpoint. I have tried it with POSTMAN and I can successfully delete using POST and the shared endpoint, however SailPoint does not yet seem to delete the account.
I have tried multiple possibilities including $., nothing seems to delete the account from the target system. Please note that the before provisioning rule works in the sense that the application is immediately deleted once the user lifecycle state changes to inactive, however after next aggregation the user comes back in as it seems like the user does not get deleted from the target system. Please share your thoughts, thank you all for the help so far.
How are you passing the values for id and name in the body?
BTW, you don’t need response mapping in the DELETE operation. Is there a reason you have added it here? (This is not going to be cause of failure though)
This is how I pass them as per Riversand’s documentation. It is indeed correct, because if I specify the endpoint already provided and this body, it will indeed delete the account (but manually using Postman).
PS: Does it matter if the access was granted through sailpoint? Because I also have remove entitlement and also disable account operations which are working fine. Also, I have added the response mapping as I thought that this would be needed.
