Okta Push Group Error: "Premature end of chunk coded message body: closing chunk expected"
Last Updated:
Overview
When Okta pushes a group to a target application, Okta fails with a premature end of chunk error because the target System for Cross-domain Identity Management (SCIM) endpoint closes the connection before sending the complete response body. Reactivate the push group to allow Okta to retry the operation. Okta logs the following error in the application.provision.group_push.mapping.update.or.delete.failed.with.error event type:
Premature end of chunk coded message body: closing chunk expected
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- System for Cross-domain Identity Management (SCIM) Applications
- Group Push
Cause
The error occurs when Okta sends a request to the target SCIM endpoint and begins reading the response body, but the remote endpoint closes the connection before transmitting the entire response. Okta receives an HTTP 200 OK status with response headers, but the chunked response body remains incomplete. The remote endpoint typically closes the connection during the initial GET request that verifies whether the target group exists. Because this verification fails, Okta aborts the flow before constructing or sending the PATCH request to update group memberships.
The target SCIM endpoint closes the connection prematurely due to a timeout, a service restart, network instability, or the dropping of idle connections.
Solution
How is the premature end of chunk error resolved?
Reactivate the push group in the Okta Admin Console to retry the push operation and contact the target application vendor if the issue persists.
- Navigate to the push group configuration in the Okta Admin Console.
- Select the option to reactivate the push group.
- Contact the target application vendor to investigate potential connection or timeout issues on the remote endpoint if the error persists.
