Using this API in a scheduled workflow to run an unoptimized aggregation nightly, which is a requirement for this source. The workflow disables delta aggregation, runs unoptimized aggregation, and then it enables delta aggregation on the source again.
Will this be deprecated on 3/31 even if the replacement is not ready by then?
@maheshtare you can use the /v3/sources/:id API to get the source by the ID you have listed. Look for the “cloudExternalId” value in the response to find the ID that you are looking for (e.g 12345).
We are hard at work on a replacement before March 31st. Please subscribe to this topic to be alerted when the replacement is ready.
Colin - is the replacement going to handle both the use case of disableOptimization of direct connectors as well as uploading a CSV file for Delimited connectors?
The replacement being worked on is a direct replacement, which means that all existing functionality of /api/source/loadAccounts should be present in the new endpoint.
Adding another vote for the replacement of this endpoint. Looking forward to the replacement before the current one is deprecated.
Adding another vote for the replacement of this endpoint. Looking forward to the replacement before the current one is deprecated.
Maybe this was already said but are you going to punt the March deprecation of this API until the new one is ready?
Likely not based on this comment from earlier, but that will likely cause some chaos for those of us actually working with the system who don’t get to pick arbitrary dates.
The goal is to have the replacement ready before the March 31st deadline. I can’t guarantee an exact date on when it will be ready though.
@colin_mckibben Will part of the deprecation of this endpoint include an update to the SailPoint File Upload Utility (FileUploadUtility.jar) as well? Will there be a separate announcement on that as we currently utilize that tool.
Here’s the answer you’re looking for:
What is the replacement for this
These timescales are not acceptable with API’s being decommissioned in March. We have applications written that automate many of these functions not provided in GUI, to prevent errors that can arise if using postman. We are now approaching 6 weeks away from losing this functionality, making time to get apps re-coded and tested incredibly short. I am sure a lot of other organisations need to document and train their support staff too. Sailpoint have not even updated all the API’s from their own GUI, items around password management are still using cc API’s. Is the March date going to be postponed to allow sufficient time for organisations to adapt their processes.
@johnheal I agree 10000%
Considering none of the client/partner work can start until the replacement is available this provides numerous challenges for getting development resources scheduled, changes made, testing completed, documentation prepared, Change Advisory Board review process and deployment within a short timeframe.
We’re all aware this process is happening, but without the vendor supplying the raw material (i.e. updated API endpoints) we can’t build the end products.
Our organisation is in the same boat (SailPoint theming pun intended). We’ve already reached out to our CSM about this deprecation, as we need enough time to carefully test and confirm the behaviour of any replacement before starting our change management process, and even if the replacement was released now, with no bugs, this would be a very tight timeframe for us.
Same situation here … in our case if we do not have this endpoint working, is literally as if you shutdown IdentityNow completely for us. Our CSM is aware of this.
I get that deprecating the old APIs is important, but it has to be done in the right way, and not just for Sailpoint, but for their clients too.
Just to add to the already growing list of concerns:
Without this API available, setting up any IDNow deployment as a partner is impossible.
Currently running deployments will stop working or slowly deteriorate until they stop working.
I surely hope the replacement comes quickly and also that the date of 31st of March is revised, as I do not see how this will work with change processes being as slow as they are.
Hoping on a quick answer for this.
After gathering feedback and evaluating options, SailPoint will be allocating additional resources to extend support for POST /api/source/loadAccounts until June 14, 2024. A public replacement endpoint is in progress and expected to be available in mid-March (IDNARSENAL-16687). Closely following the availability of the public replacement, updates to the File Upload Utility are expected the week of March 18, 2024. Stay tuned for updates that will be posted in this topic as they come available.
Hello, has there been any update yet? Thanks.