Delete stucked entitlement?

Hi! I have a JDBC Source, which was redefined, and I want to reuse the same source instead of creating a new one with other name (like xxx v2). I forced account and entitlement queries to bring 0 results (adding ‘1’ = ‘2’ to queries), and that deleted all existing accounts. But from the original 900 entitlement, it remained 1… I deleted all possible objects that used, is there some way to remove it?

I do not want to remove and re create source, because it happened several times that when deleting sources, it appears that something remains in Sailpoint storages, because I always receives the message “Source with internal name xxx [source] already exists”:

There is undocumented method to delete entitlement via API - try this

of course first get the id of the entitlement you want to remove - I found that in some instances it works in some it doesn’t - honestly, don’t know why. I’ve created bug ticket for missing entry in documentation but it seems this method is not stable across environments but I believe you can try,

Hi Kamil, thanks!

I tried but received RESTEASY003650: No resource method found for DELETE, return 405 with Allow header

1 Like

I am seeing in github discussion that it happened to someone else, I think Sailpoint removed the endpoint, or it is not rolled out to all tenants yet.

1 Like

That’s what I would expect also.

We opened a case and returned to use some private API, in this case it reset source to oroignal state when created (which is useful for us):

https://cruzeirodosul-sb.identitynow.com/cc/api/source/reset/#####?skip=accounts

I will investigate parameters, but skip=accounts should retain existing accounts. Again, there should be an equivalent in v3/beta of this call in next months.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.