I am unable to run Entitlement Aggregation using File Upload Utility using below command:
java -jar FileUploadUtility.jar -url https//****.api.identitynow.com -client_id *** client_secret **** -e “path of file” --objectType group -v
File Upload Utility version used: 3.0.5
Getting below error:
Exception in thread “main” com.beust.jcommander.ParameterException: Was passed main parameter ‘–objectType’ but no main parameter was defined in your arg class
Exception in thread “main” com.beust.jcommander.ParameterException: Was passed main parameter ‘-objectType’ but no main parameter was defined in your arg class
Exception in thread “main” com.beust.jcommander.ParameterException: Was passed main parameter ‘-o’ but no main parameter was defined in your arg class
Could you please share how you were able to fix the issue using version 3.0.5?
Your advice and assistance will be greatly appreciated. Thank you in advance.
File upload utility is scheduled to run at 3 6 and 9 AM every day and scheduled job history shows that the job triggered on schedule at 3am,6am and 9am but file upload is happening only at 3am every day. Yesterday I triggered the job manually at 12:35pm and it worked fine. Now it skipped file upload at 3AM as well. Can it only upload once every 24 hours? I don’t understand why file upload is being skipped. Any thoughts on this?
We are being informed that for customers using the file upload utility, they need to upgrade to the latest version ASAP. Where the supporting endpoints will be deprecated the week of July 8.
We are using file upload utility and its critical for us to understand if the utility will stop working completely if we could not upgrade it till 8th July in PROD? We are working on upgrading our JDK version to 11 as its needed, so it might take some time for us to upgrade the file.
Could you let us know what will be the impact on FUU if not upgraded other than CC APIs not working?
Hi @Krishnapatil - Thanks for your patience, I’ve been out on vacation. The File Upload Utility is a pretty simple tool in all versions. It just looks at files or directories you specify, authenticates, and calls aggregations APIs for each file.
For File Upload Utility 3 and earlier - these call CC APIs for aggregations. When these APIs are deprecated, they will no longer work. The File Upload Utility will still do what it’s designed to do, and attempt a call. Just those responses will return something like a 410 Gone response. So it will run, but it won’t aggregate, because the APIs won’t be there anymore.
For File Upload Utility 4 - these call the new supported V3 APIs for aggregations. There are some structural differences in what the API expects with regards to source IDs, as we’ve documented on the readme and announcement posts. This also does use JDK 11 or later because that is what underlying libraries and tests needed to run in order to work.
Using File Upload Utility isn’t a requirement by any means; it’s a tool that I made for convenience for the community. You certainly can leverage the public API documentation to make your own scripts in your own language and framework of choice if you desire as well.
Hi @ram_sadhanala - Thanks for your patience, I’ve been out on vacation. The File Upload Utility is relatively simple; it’s just transit. It scans specified files and directories for files, authenticates, and calls aggregation APIs for each file it has. File Upload Utility will do what it does whenever it is called. The only reason it would skip files is if it can’t find the source IDs in the name of the file, but that should be a fairly consistent thing (I hope). As for aggregations, you can aggregate repeatedly for a source, only as long as there isn’t an existing running aggregation for that source.
For debugging, you can always turn on verbose logging with the -v option to see what is happening at an API call level. That should tell you what the API is returning.
Can anyone help with a step by step on the upgrade process? A SailPoint engineer set this up 2 years ago for our initial implementation and I would like to update it but I’m not seeing any documentation on the upgrade steps.
Thanks for this post, this really help clearing up all the requirements to run the upload tool. I’m able to aggregate account in my first go. Can I please make a suggestion to include “Personal access token (PAT) with ORG_ADMIN capabilities and sp:scopes:all” in the requirement? maybe it help others newbie like me.
If we need to schedule the execution of the file upload utility whether is using cron or windows task scheduler, how can we avoid adding the client id and secret in clear text as part of the command line to execute? Otherwise those credentials would be available to anyone that can use/read the cron job list/task scheduler.
@damianfraire - I know some customers have wrapped File Upload Utility’s execution in a script which can get these parameters dynamically and then invoke the execution. You might do that too!
@ram_raghothama - What version are you running? All of the File Upload Utility versions 3.x and earlier are using old APIs, and those APIs are now deprecated. File Upload Utility 4.0 uses modern supported APIs.
@ram_raghothama - All of the File Upload Utility versions 3.x and earlier are using old APIs, and those APIs are now deprecated, and won’t work. Theres been a lot of announcements about that on this site in particular.
File Upload Utility 4.0 uses modern supported APIs, so I would migrate to this version to get working again.
It works…