Troubleshooting

Test connection failed. Unrecognized SSL message, plaintext connection?

Resolution: Add the following entry key in the application debug page:

<entry key="useHttp" value="true"/>

openconnector.ConnectorException: Bad Request

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

• Aggregation fails with the following error message:

  Exception during aggregation. Reason: openconnector.ConnectorException: Invalid response or no resource received. Bad Request

  Resolution: Verify that the values of the Configuration Parameters are valid.

• In open JDK 11, account aggregation fails with the following error message:

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

  Resolution: For the Slack Connector to handle chunked data on open JDK version 11, add the following entry key in the application debug page:

  <entry key="enableDefaultConnectorProvider" value="true"/>

• 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.

Aggregation and Provisioning operations fail with the following error message:

too_many_requests

Resolution: The default retry count value is 5. Increase the value of the retry count for the Slack Connector by adding the following entry key to the application debug page:

<entry key="rateLimitMaxRetryCount" value="Enter the value of retry count" />

When Manage Channels is selected under the Configuration > Settings > Filter Settings, the account preview execution time increases.

Resolution: Cache creation is enabled in the Slack Connector, by default. To reduce the aggregation execution time, run sequential approach by adding the following entry key in the application XML:

<entry key="disableChannelCaching" value="true"/>

Resolution: Ensure that Manage Channels is selected under the Configuration > Settings > Filter Settings and that the service account token has the following administrator permissions:

admin, channels:read

Resolution: Ensure that the Slack connector is configured correctly and that you configured the required administrator roles. For more information, see Configuration Parameters and Required Permissions.

If you still don't see the Channel and Workspace schemas, perform the following steps to manually create the missing schemas:

1. Select Manage Channels in the Configuration Filter Settings.

2. Create new channel and workspace type objects. For more information on these object types, refer to Group Attributes.

3. Add the channels attribute to the Account schema (type: channel). For more information on these object types, refer to Account Attributes.

4. Add the workspace attribute to the Account schema (type: workspace). For more information on these object types, refer to Account Attributes.

5. Enter the required provisioning policy attributes to create the channel. For more information on each attribute, refer to Create Channel Attributes.

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.