The File Upload Utility was moved to the Developer CoLab awhile back. The latest release is linked above, but the Compass Community page wasn’t updated.
I updated the Compass Community’s File Upload Utility page to link the Developer CoLab page for File Upload Utility now. There should hopefully be no further confusion where this lives now. 
I would suggest keeping an eye on the below linked thread as you’ll likely hear news about it there if it isn’t announced in Announcements
Thanks you so much @neil_mcglennon. I have tried using new utility in our test tenants and it’s working amazing (Feed file with short ID in filename). I am aware that new utility will work with short ID as well. The question is, can we still keep short source ID’s in our daily feed files for current sources? Would it impact anything in near future or we need to change filenames with long IDs for existing sources? Going forward for new sources we will make sure to use long source IDs.
Hi @Shubhams_009 - Thanks for the feedback! Glad things are working well. The new File Upload Utility will work with both short (old) and long (new) source IDs. However, if you provide a short ID, that does require a lookup. That lookup does add additional overhead, and could fail or not exist in some cases. The best long-term option is to use long source IDs going forward, as it has everything it needs in order to aggregate the files.
If you have other ideas, I am all ears.
Is File Upload Utility compatible with any of the Java alternatives like Amazon Coretto or OpenJDK?
Sure is. In fact we test with OpenJDK and Amazon Coretto!
which version of OpenJDK would be needed for compatibility with File Upload Utility 4.0?
File Upload Utility requires Java Development Kit (JDK) 11 or higher to run. We build and test against OpenJDK 11 as well as OpenJDK 17.
For future reference the version is on the announcement and the documentation as well.
Hope this helps!
Two questions please.
Is the File Upload Utility 4.0.0 officially released? https://community.sailpoint.com/t5/Professional-Services/SailPoint-File-Upload-Utility/ta-p/76392
When is the last day I can still use the File Upload Utility 3.0.2?
Hi Huu
Version 4.0 is there - Releases · sailpoint-oss/colab-file-upload-utility · GitHub
You can download the jar and use that.
Hi Jason,
When is the last day (tentatively) we can use the old File Upload Utility 3.0.2?
Thank you,
Huu
I believe it is end of June, but not 100% certain.
Personally, I would move off 3.0.2 as soon as possible.
Thank you Jason, hopefully 1 last question, can it support Java 21?
Hi @huu11 - Yes, the Requirements are listed here:
- Java - is a Java based application and requires Java Development Kit (JDK) 11 or higher to run. We build and test against OpenJDK 11 as well as OpenJDK 17.
- Network - This also requires external, outbound access over HTTPS (443) via REST API calls to the SailPoint Cloud as indicated by the URL you configure the File Upload Utility.
Hope this helps!
Hi there, we are just now testing v4.0 with Open JDK 11 and are seeing an odd issue. Hoping you can see what the issue might be.
We run the java command from a PowerShell script on a scheduled task. Running the jar command from a command prompt works fine.
PS script kicks off and at the point of running the the external jar command:
cmd /c “java -jar D:\SailPoint\FileUploadUtil\FileUploadUtility.jar --url https://company-sb.api.identitynow.com --client_id “” --client_secret “” -f D:/SailPoint/FileUploadUtil/upload/ -r -v”
The script kicks off, however, the 401 (Unauthorized) Error is received:
Checking credentials…
Error Logging into Identity Security Cloud. Please check your credentials and try again. [Error authenticating with credentials: 401 ]
We attempted to create a new PAT and same same issue, jar command runs from a command prompt but not the PS script.
@RArroyo - At first pass this like an options naming issue. Per the documentation, the options for your PAT should be --clientSecret and --clientId, not --client_secret and --client_id. You shouldn’t need to put them in quotes either (unless that was just for the forum). Feel free to see the usage example here for additional reference. Hope this helps!
Thank you Glenn!
I received the reminder email from Sailpoint about the deprecation of non-public APIs. It also talks about the new File Upload Utility but doesn’t indicate the when the prior version will stop working. Is there a date we should expect that to quit working?
Older File Upload Utility versions (3.x or earlier) use CC APIs, and therefore will stop working when these CC APIs are deprecated. This is why we developed File Upload Utility 4.0 which uses the new APIs.
How is everyone securing the client secret, especially if automating the File Upload Utility?
We do not want to store the client secret in plain text, so I am looking for what others have done for this.
Thank you