Skip to content

Troubleshooting

If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support.

For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information:

Debug Logs

For information about managing additional source settings, including debug logging and downloading connector logs, refer to Managing Additional Settings.

Aggregation Errors

  • Exception during aggregation. Reason: javax.ws.rs.ProcessingException: Error closing message content input stream.

    Resolution: Verify that that you correctly set up the Enable Default Connector Provider source field in the Advanced Settings section.

  • openconnector.ConnectorException: Invalid response or no resource received. Bad Request

    Resolution: Verify that the values of the configuration parameters such as filter conditions, API URL, and others are valid.

  • java.lang.RuntimeException: openconnector.ConnectorException

    Resolution: Ensure that you correctly set up the Maximum Retry Count Limit and entered the value for the maximum retry count in the Slack source. The default value is 5.

  • Account aggregation fails to retrieve the associated channels with an account.

    Resolution: Ensure that you correctly set up the Manage Channels source field and the service account token has the following administrator permissions: admin, channels:read.

  • An error message is displayed while performing group aggregation:

    connector exception :openconnector.ConnectorException{"ok":false,"error":"team_access_not_granted"}

    Resolution: Verify the auth token application is installed on Workspace.

Slack Bots Aggregation Errors

  • Slack Bots aggregation fails immediately with a message that the Bot User OAuth Token is required.

    Resolution: Select the Enable Slack Machine Accounts toggle and enter a valid xoxb- token during Express Setup or on Machine Identity Governance Settings.

  • No bots appear after aggregation.

    Resolution: Verify that the bot token has the users:read scope and that the app is installed on the workspace. The connector excludes Slackbot by design. For the complete list of bot scopes, refer to Required Permissions.

  • Account Subtype shows -- on a machine account.

    Resolution: Verify that the Non-Human Identity processor has the slack:bot system-managed subtype, and then run dataset aggregation again after you create or refresh the source.

  • Owner shows -- on a machine account.

    Resolution: Verify that slackAdministratorEmail has a value and that an identity exists with a matching email value. The default correlation matches slackAdministratorEmail to the identity email attribute.

  • Machine accounts are missing from the source account list.

    Resolution: Go to Non-Human Identities > Accounts to view machine accounts. The source account count and list show SCIM human accounts and might not list bots.

  • On Enterprise Grid, aggregation reports the following errors for a workspace:

    team_access_not_granted, team_not_found

    Resolution: The connector skips workspaces that the app cannot access and continues to aggregate the remaining workspaces. To include a skipped workspace, install the app on that workspace.

Provisioning Error

  • openconnector.ConnectorException: Bad Request

    Resolution: Ensure that the mandatory attributes required to create a resource on Slack are provided, and that the input data is valid and not duplicate.

Increase in Account Preview Execution Time

When Manage Channels is configured, the account preview execution time increases.

Resolution: Cache creation is enabled in the Slack source by default. To reduce the aggregation execution time, run sequential approach by setting the Disable Channel Caching option in Advanced Settings.

Test Connection Errors

While proxy is configured as HTTPS proxy, the test connection fails with the following error message:

Test connection failed. Unrecognized SSL message, plaintext connection?

Resolution: Ensure that you correctly set up the Enable HTTP Proxy option in Advanced Settings.

managerID Is Not Updated for the User

If the user is disabled in the managed system, the managerID of the user cannot be updated.

Resolution: Ensure the user is active on the managed system, and then, perform the update operation.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.