Manage data source connections
You can manage and monitor the health of your connected sources from the ISPM console. When you rotate credentials for a source, you can also update the credentials in ISPM proactively to maintain continued connection to your source. You can update credentials directly in ISPM for the following connectors:
-
Entra ID
-
Google Workspace
-
GitHub
-
GitLab
-
Jira
ISPM automatically tests the connection to each source daily to ensure that your org's reported security posture status is current and reliable. You can check the latest status from either of the following pages:
-
Connected Sources: A detailed list of all sources and their individual statuses.
-
Dashboard: A summary is visible in the top-left corner.
When ISPM detects problems with the connection, it sets the connection status for the source as Failed. A Failed connection status is caused by one of the following errors:
- Failed authentication
- Missing permissions
- Missing configuration
Start this task
-
In the ISPM console, go to .
-
Click View error for the relevant source.
Missing Permissions
This error occurs when ISPM can't retrieve the necessary data for your org due to insufficient permissions.
To resolve this error, click Integration Guide to access the specific documentation for that source and follow the steps listed in the integration guide.
Missing Configuration
This error occurs when the ISPM integration wasn't set up correctly within the source application. This misconfiguration can include missing API roles or other incorrect system-level configurations.
To resolve this error, click Integration Guide and follow its steps.
Failed Authentication
This occurs when ISPM wasn't able to sign in to your environment due to an incorrect password, an expired token, or a revoked API key.
To resolve this error, click Update Credentials and enter the correct information.
Depending on the connector, edit any of the following fields as required:
-
Entra ID: Update Application ID and Client Secret
-
Google Workspace: Update Super admin, Email address, and the Credentials JSON file
-
GitHub: Update Personal access token
If your org rotates credentials regularly, Okta recommends that you proactively update credentials in ISPM as well to prevent errors.
Test connection status
After you resolve the connection error, complete the following steps to manually test the connection:
-
In the ISPM console, go to .
-
Find the source that you have fixed.
-
From the Actions column for that source, click Test Connection.
When the connection test succeeds, ISPM updates the source's status to Connected confirming that the issue was resolved.
