POST /api/source/reset/

Identity Security Cloud (ISC) Non-Public API Deprecations
,
22

I noticed this as well. Made recovery from Configuration Hub a NIGHTMARE

1 Like
23

Has there been any decision to roll this deprecation back? We really need a proper migration of this API. Thanks.

1 Like
24

A replacement for /api/source/reset is expected to be released by the end of March, 2024. In order to allow users enough time to migrate off of the private API and onto the new public endpoints, SailPoint is allocating additional resources to ensure that /api/source/reset remains operational until June 14th, 2024. The replacement for this API will be two separate endpoints. One endpoint will handle the resetting of accounts, and one endpoint will handle the resetting of entitlements.

Please subscribe to this topic to receive an update when the new endpoints are available.

6 Likes
25

Any update on the replacement API for resetting source?

1 Like
26

To reset entitlements on a source, please use reset-source-entitlements | SailPoint Developer Community

The public endpoint for resetting accounts on a source is still in progress.

1 Like
27

thank you Colin, do you have any ETA?

28

I do not have an ETA for reset accounts. It should be very soon™

1 Like
29

Reset accounts is now available. It is located here:

3 Likes
30

Hi Colin,
I was just going to ask “Is there also a way to reset/delete the entitlements?” as deprecated API uses same endpoint for both

Looks like reset entitlements endpoint is: reset-source-entitlements | SailPoint Developer Community

1 Like
31

What about resetting the internal name? That just became an issue for me, two weeks after the EOL of the /cc endpoint

1 Like
32

Hey @vsandhu1,

So you were able to update the internal name with the old api?

Do you remember the field or body of the request you used to update it?

33

I was down in our Sandbox, so I bit the bullet and Deleted the whole Source. There was no workaround, and time was ticking…

34

I have used this Reset API to reset the accounts and entitlements and it worked perfectly but after reset, I have made the couple of name changes on the entitlement schema types and its attributes as well and reran the aggregations. Here I noticed few observations where one of the entitlement ID did not sync with the Entitlement Name and after the troubleshoot, I got to know that Source file still having the old name references when I look at the source config data using the API in Postman.

So here I need some suggestions on how to clear those backend old references from the Source file although it doesn’t show up in the UI section.

35

Hi,
I would make a backup of existing source (copy and paste from Postman to Notepad etc) then delete it entirely and re-create it from scratch.

It is unfortunate, but this is the only way to have a clean source without old references. If you do everything with Postman/API calls, then it shouldnt be too much effort to re-create the source, I hope.

36

any update on this ? this is very much needed api

37

Having to go through a source fixup right now for several sources and very much missing the simple source reset api. It is very much needed and wanted.