I am the author and owner of the File Upload Utility, which I know many of you rely on for file source aggregations on a daily basis. I just wanted to provide you all with a quick status update on future plans, especially in light of CC API Deprecations announced, to help clarify, set expectations, and answer any lingering doubts.
Here is a quick rundown of questions we’ve received and answered to date:
Q: Is the File Upload Utility still an active tool?
A:Absolutely! We still support and update it. It is purposely a fairly straightforward, tried-and-true tool, so it doesn’t require a lot of attention. Keep it simple!
Q: What is the next version of File Upload Utility?
A:Version 4.0. The next version will have updates to V3 Account Aggregation and Entitlement Aggregation APIs.
Q: Will the File Upload Utility be updated with new V3 Account Aggregation APIs?
A:Yes! That will be coming with the next version (4.0). I have been working with our SailPoint Engineering teams on the needs here, and we know this is currently in development. Once we have our hands on the new APIs we’ll do some testing with these (along with some new test cases) to validate. We’ve already done some ‘pre-work’ on what we think is necessary, so that should get them to you quickly, but reliably.
Q: When will this happen?
A:Late April or Early May. It will happen as soon as the V3 Account Aggregation and Entitlement Aggregation APIs are available. We anticipate that should be in the next few weeks. We will make announcements here on the Developer Community.
Q: How will I be notified?
A:Here! Stay tuned. We will make announcements here on the Developer Community about the new version of this tool, as well as work with SailPoint Customer Success Managers (CSMs) to tell customers.
Q: Will there be any changes needed from my end?
A:Possibly. With the change from CC Account Aggregation APIs to V3 Account Aggregation APIs, we know that the V3 Source IDs are different from the older CC Source IDs. The File Upload Utility uses a Source ID in the name of the file, so this might be impacted.
The difference in Source ID is best illustrated by example:
CC Source ID: 62867
V3 Source ID: 2c9180835d191a86015d27b0a2c31334
Going forward, the File Upload Utility 4.0 will look for the new V3 Source IDs in the name of the file by default. If these are not found, then it will attempt to fall-back by looking for an older CC Source ID, and then map that to the new V3 Source ID based on the requirements of the V3 Account Aggregation APIs. This will require an additional lookup, which is done by looking at the source data under /connectorAttributes/cloudExternalId. If these cannot be found a warning will be issued, and the file will be skipped.
Q: What about V3 Entitlement Aggregation APIs?
A:Version 4.0. will support this. We’re currently waiting on these V3 Entitlement Aggregation APIs.
Q: Will there be any additional features added?
A:Not yet. Beyond the API transition, we don’t anticipate adding any additional features into the next (4.0) release. We want to get this in your hands as soon as possible. We’re always interested to hear what else you are keen to add to the solution.
Q: Are there plans to support other types of File Upload Utilities - i.e. not Java?
A:Not yet. This is something that we are considering, but have no definitive plans as of yet. We’re always interested to hear what other technologies you prefer. I know there’s been interest in Python and PowerShell as well. We chose Java because that has always been what the SailPoint implementation teams have been most familiar with, and because it runs cross-platform fairly well.
If you have any other questions, thoughts, comments, etc. - feel free to add to the thread below here, and I’ll try to accommodate. Thank you all for your interest and usage of the File Upload Utility! We look forward to getting new versions as the APIs become available. Thank you!
Neil McGlennon
Principal Architect
SailPoint Technologies
We only allow download of the latest (current) version of the File Upload Utility. We’ve never allowed previous versions of the utility to be downloaded. In my opinion, there is really not much point in distributing an old or outdated version.
That being said, if you somehow have an old, outdated version of File Upload Utility, there’s really nothing that SailPoint can do about it. The older versions of File Upload Utility will continue to work the way that version is designed to work - until the CC APIs are no longer available. I’d expect once the CC APIs are no longer available, these older versions of File Upload Utility will start returning 404 Not Found errors for any files (attempted) to be aggregated. That’s because the APIs will no longer be available once they are deprecated. File Upload Utility can’t do anything about that.
You’d just need to make sure to update to the latest version when it becomes available, If you want to keep an old version around for backup, posterity, memories, or whatever… go for it! Just be forewarned that the APIs it uses may no longer be in service.
Thank you. My biggest concern is the IDs. We have a lot of delimited data feed files that are sent daily and will require vendors and application owners to change the file names. I’m hoping the new version will still call the short ID until we can get all the files renamed. Has a solid date been set for the new one or still mid March sometime?
So for the File Upload Utility, let say once they have an update, will a new jar file be provided or something like that? For example, the one we are using now is “FileUploadUtility.jar -url https://usfca.api.identitynow.com”
Hi, when will be the new File Upload Utility.jar available.
We’re still waiting on API updates. I know these are in final stages of development and testing, so it should be somewhat soon. Once they are available, I will be able to finalize my updates, test, and publish to you all.
So for the File Upload Utility, let say once they have an update, will a new jar file be provided or something like that? For example, the one we are using now is “FileUploadUtility.jar -url https://usfca.api.identitynow.com”
Yes, the new version will have an updated JAR. It will be posted and announced on this site.
Today is already 03-26 and our office will close 03-29. Do we need to update this new File Upload Utility jar file before 3/31 then? Just thinking ahead that’s all. Thank you.
Today is already 03-26 and our office will close 03-29. Do we need to update this new File Upload Utility jar file before 3/31 then? Just thinking ahead that’s all. Thank you.
No, you don’t need to update by 3/31. The deadlines for the APIs were extended out a bit, so that means you can continue using the older File Upload Utility until then.
I am still waiting on the updated APIs in order to test and release File Upload Utility 4.0. I know what they’ll look like, so the code has been updated, they just haven’t been tested, and we want to make sure they are well tested before released.
Hi @huu11 , I imagine the old File Upload Utility will work until May at least, so the new version is not super-urgent.
Sailpoint have committed to providing a new version before the old one stops working.
That’s right, @jrossicare. The API deadline has been extended. You can continue using the older File Upload Utility until that deadline.
I am still waiting on the updated APIs in order to test and release File Upload Utility 4.0. I know what they’ll look like, so the code has been updated, they just haven’t been tested, and we want to make sure they are well tested before released.
Hi all! From what I have been told, the new API for account aggregations has been released for Sandbox and Production tenants. The new API is: POST /beta/sources/{id}/load-accounts, and it sounds like new API documentation should also be released to that effect today. I’ve been personally testing this end-point with the new version of File Upload Utility (4.0) and all looks promising so far.
The only thing holding the new version of File Upload Utility from release is the entitlement aggregation endpoint, which we expect to be POST /beta/sources/{id}/load-entitlements. We already have that new end-point coded into the File Upload Utility (4.0), and are awaiting some work on the SailPoint side to continue testing. We expect that new API to be available next week potentially.
If everything goes well, we should have File Upload Utility 4.0 ready with new APIs ready for the field by end of next week.
Hi Mahesh,
Wrong utility. The File Upload Utility is only for aggregating Delimited File sources.
To create roles, there is a separate utility called Role Importer. I dont know if it has been maintained or updated to use v3 API endpoints, or to handle roles with direct entitlement assignments.
