![]() Solution2: On Windows, in cases where the tool is run from a driver that is different from the one where the OS and Python is installed. Next, create an environment variable named REQUESTS_CA_BUNDLE and set its value as the path to thecert.pem file. If DER one fails, you already have the file in PEM format so rename the thecert.crt to thecert.pem, otherwise transform it to PEM using the first openssl command line above. Openssl x509 -text -inform PEM -in thecert.crt Openssl x509 -text -inform DER -in thecert.crt crt file is already PEM format or not, run these command lines first and see which one fails. Openssl x509 -inform DER -in thecert.crt -out thecert.pem -outform PEM If DER format is used, transform it to PEM using openssl command: ![]() Solution1: Obtain the firewall's CA certificate in PEM format (assume that its name is thecert.crt). Tip: It is because there may be some SSL inspection enabled on the proxy server (local environment setting) adapt the run time schedule of the UST to your organisation's work day when users need provisioned (eg if your organization doesn’t have a need to modify user provisioning at night, do not run syncing jobs during this time).if it is required to run the tool more often, reflect on the possibility to use UST with push strategy (delta of changes) instead of full sync.revise the scheduled task trigger time so it does not start at :00 or :30 minute mark (avoid peak traffic activity).revise the scheduled task frequency and make sure that it is set to repeat at least 2 hours apart.Here are some recommendations for best performance, in regards to the run frequency: In this case an error message might appear in the UST log referring to 'a process is already in progress'. Since the script recognises when two instances are launched at same time, no new instance can be triggered until the initial one has finished running. Although the timeout just puts the UST on hold for a period of time (so not a critical stop kind of error), the UST will know to recover and continue the sync right after. If an instance is observed to be run more frequently it will be throttled anywhere between 30 and 60 minutes. ![]() If the timeout is higher than 1800 seconds, this would be a throttling related to the run frequency of each User Sync Tool instance. The recommendaton here is to let the script run all the way to the end. The script stops after three failed attempts. Tip: If the timeout is less than 30 minutes, these Warning messages are received when the quota of API calls to make within one minute was reached. UST comes with an exponential back-off mechanism to retry the call, increasing the time between retries.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |