Single Sign On and aPriori Command Line Utilities
Single Sign On also applies to the aPriori following command line utilities:
Bulk Costing (bulkLoad.cmd)
BOM Loading (bomLoad.cmd)
Client Compatibility Updater (updateCompatibleVersions.cmd)
Doc Cache Cleaner (cleanDocCache.cmd)
Doc Cache Updater (updateDocCache.cmd)
Watch Point reports (runAprioriReport.cmd)
In general, when Single Sign On is enabled, these scripts will attempt to use the signed-in Windows user credentials, unless you override this behavior by providing the credentials on the command line or in a relevant properties file.
The order of precedence for using credentials is:
1 Command line arguments.
2 Stored in the relevant properties file (if applicable).
3 Signed-in Windows credentials from SSO.
Note that if you are upgrading to a release that uses SSO and you have existing command line scripts, you will need to review them and determine if:
You want or need to remove current credentials to make use of SSO.
You need to reorder the position of existing credentials on the command line as order may have changed as part of the implementation of SSO.
See the aPriori Professional Installation Guide for upgrade details.