Different settings in the HTTP header for authentication and data request lead to connection failure (4226056)

ErrorMessages (YYYY-MM-DD HH:MM:SS.403) Executed on: jobservicedestination

[2134003] Error executing synchronization.

[1777018] Error executing synchronization project (SCIM Synchronization (STARLING CONNECT SUCCESS FACTORS HR))'s workflow (Positions).

[1777124] Error executing projection step (PositionsMapping) of projection configuration (Positions (cada3090-c9b8-4de1-8347-352860e5f08d)).

[1777219] Error executing synchronization step (PositionsMapping)!

[1777005] Error reloading 1024 system objects.

[System.Reflection.TargetInvocationException] Exception has been thrown by the target of an invocation.

[System.Reflection.TargetInvocationException] Exception has been thrown by the target of an invocation.

[System.Reflection.TargetInvocationException] Exception has been thrown by the target of an invocation.

[System.Reflection.TargetInvocationException] Exception has been thrown by the target of an invocation.

[VI.Projector.Connector.Base.ConnectionTSBrokenException] Unable to connect to the remote server

[System.Net.WebException] Unable to connect to the remote server

[System.Net.Sockets.SocketException] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond xx.xx.xx.xx:443

This is related to Product Defect CR ID 33884

In the HttpWebRequest class used, the connection setting "Connection: Keep-Alive" is active by default.

To switch this off, the flag "KeepAlive = false" must be set explicitly. If there is a request for authentication without the flag, it is automatically assumed that this connection remains active. If another request is made via this connection, and the flag "KeepAlive = false" is set, the connection is terminated on the server side after the request has been processed. However, this is not noticed by the HttpWebRequest class, which continues to assume that the connection can still be used. This leads to errors and, after approx. 4 further unsuccessful attempts, to a timeout.

This aborts the entire process in the SCIM Connector and initiates a new connection including authentication, the process starts again. The same process happens during a token refresh as well.

For Identity Manager v 8.1.4 "KeepAlive=true" is set for all requests, for Identity Manager v 8.2 this is configurable.