Okta Slack Deprovisioning Fails with an Internal Server Error
Last Updated:
Overview
Slack rejects the user deprovisioning API request that Okta sends due to an HTTP 500 error from the downstream Slack System for Cross-domain Identity Management (SCIM) server. Administrators must contact Slack Support to investigate the root cause and manually deprovision the user in Slack. When an administrator removes a Slack application assignment, the deprovisioning fails and Okta generates a specific error in the System Log.
Push user deactivation to external application
FAILURE: Internal Server Error. Errors reported by the connector : "fatal_error"
Administrators can locate the Slack deprovision failure event details by searching the Okta System Log for the specific event type.
legacyEventType eq "app.api.error.deactivate_user"
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Slack
- Okta Integration Network (OIN)
- Deprovisioning
Cause
Slack rejects the user deprovisioning API request that Okta sends due to an HTTP 500 error from the downstream Slack SCIM remote server.
Solution
How is the Slack deprovisioning failure resolved?
Okta cannot determine the root cause because Okta does not have access to external Slack SCIM logs. Administrators must contact the Slack Support team directly for assistance to determine the root cause.
Manual deprovisioning tasks require completion in the downstream application.
Administrators must proceed with manual Slack user deprovisioning in the downstream Slack application. Administrators manage manual deprovisioning tasks and set up notifications by reviewing the provided resources.
