Admin Configuration for Okta Importer

1. Import Settings

When the application imports data in the background, it may encounter errors triggered by the API used for syncing data from Okta, particularly due to excessive requests. To address this issue, adjusting the timing and size of the items between batches can help mitigate the errors. However, it's important to note that this adjustment will lead to a longer synchronization process for all items, as the system will take more time to process the reduced batch sizes.

2. Set up Automation Notifications

If you want to receive automatic notifications regarding errors in your daily or hourly scheduled imports, you can set up a Jira Cloud Automation rule using a Web Trigger. For detailed instructions on how to create an Automation Rule, please visit the Notifications page. After successfully creating your rule, you can enter your automation URL below to ensure you stay informed about any issues that may arise during the import process.

3. Audit and Debug Logs

Audit logs serve as a comprehensive record of all changes made within the system, allowing users to track modifications and identify any discrepancies. If you encounter any issues, we recommend consulting our documentation for helpful troubleshooting tips. You can access the audit logs below for further insights.

Additionally, debug logs are invaluable tools for reporting and diagnosing problems with the application, providing essential information that can aid in resolving any technical difficulties you may face.

4. Reset Application

You can delete all the data stored by the application except for the Audit logs from here. Please note that this action will not remove the object schemas you created. For a complete cleanup, ensure that you also remove the object schema.