POST /api/source/loadAccounts

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

Replaced bys

After gathering feedback and evaluating options, SailPoint will be allocating additional resources to extend support for POST /api/source/loadAccounts until June 14, 2024.

If you are looking for more information on when and how the File Upload Utility will be updated to support the new endpoints, please read this post.

7 Likes
2

What is the replacement for this API, we need this for deoptimized aggregations.

3 Likes
4

Iā€™m asking engineering for an answer to this. Iā€™ll keep you updated when I find an answer.

5

Ditto.
disableOptimisation is highly important and necessary feature.

3 Likes
6

+1, this functionality is needed and is currently not being supported in any different API. It is not even supported through the UI.

7

Yes, we donā€™t have an alternative API in beta/v3 which can initiate aggregation with disableOptimization. It would be good if this post also documents whether an alternative API is available or not and the details of the alternative API if available.

1 Like
8

@colin_mckibben - I did test this functionality this morning, and the source reset functionality, and both API calls still work right now. I agree with everyone above though, if this is being deprecated we most definitely need a replacement for source resets and source aggregation with a disableOptimization argument.

3 Likes
10

Hello, has there been any update on the migration of this API yet? Thanks.

11

I know this isnā€™t about the API, but unaggregated optimization would be a great option to have the GUI. We have people who have postman and API access solely for the purpose of invoking an unaggregated optimization.

3 Likes
12

Any status update on this?

13

This is still in progress. Expect an update after the new year.

14

We also use this to update a CSV source via API. There is no other way that I am aware of to do so.

3 Likes
15

Looks like it was backwards day when I posted about ā€˜unaggregated optimizationā€™. :slight_smile:

2 Likes
16

Just adding my upvote and maybe a response from a SailPoint spokesperson that could confirm how we can disable optimization on aggregation. With the incident yesterday a bunch of our aggregations failed and have not updated correctly based on actual source account data. i want to aggregate with optimization off to see if it will correct these data issues. Resetting a source is a horrible work around and I will not accept that as a solution.

3 Likes
17

When this functionality is available, would it allow the manager correlation to be evaluated? The MANAGER_ID is populated, but needs to be re-evaluated. HR isnā€™t wanting to change the value and change it back, which makes sense.

18

what is the replacement call for this? Needed today to fix an erroring account!

19

@jodi_pruitt - It looks like the original CC API is still active. @colin_mckibben - Do you know if this would be turned off before a replacement is provided?

20

This CC API will be turned off on March 31st. A replacement is in progress. When the replacement is ready, I will update this post accordingly.

1 Like
21

Thanks Colin.

We definitely need the capability to run unoptimized aggregations. Glad there is a replacement in progress.

22

Hi @colin_mckibben ,

Do we have any replacement API for ā€œapi/source/loadAccountsā€.

We are struggling with the correlation issues and need this API to trigger unoptimized aggregation.

Also, we are not able to find the SourceID in the URL. Rightnow it is giving ā€œa3aa5822ce9c4b39aeadfaf32270ac74ā€ kind of SourceID