All versions of Centrify for SaaS & Centrify for MobileProblem:
After upgrading the Centrify Cloud Connector to versions 15.2 or higher, web proxies can no longer connect to the internet, or periodically become disconnected.Cause:
In versions 15.1 and below, if the Cloud Connector was running behind a web proxy; use of HTTPS mode would result in an increasing number of unclosed TCP connections stuck in a CLOSE_WAIT
As the number of CLOSE_WAIT
connections increased in some connector hosts, network connectivity problems would eventually arise causing the need for the connector service to be restarted in order to clear out the TCP connections.To fix this issue and improve the stability of the product, version 15.2 of the cloud connector changed the default connection protocol to HTTP web sockets instead (as recommended by Microsoft).
However it was found that this change was
incompatible with some environments using web proxies.
- Open the Config file from the following location in a text editor:
- C:\Program Files\Centrify\Cloud Management Suite\Centrify.Cloud.Core.ProxyHost.exe.config
- Search for the following value:
- <add key="Microsoft.ServiceBus.OverrideAutoDetectMode" value="HttpsWebSocket" />
- Change this to:
- <add key="Microsoft.ServiceBus.OverrideAutoDetectMode" value="Https" />
- To make this change persist across Connector updates, search for the following line:
- Change this to: (Optional: If this edit is not used, then the change in Step 3 will be overwritten back to default values at the next Connector update)
- <enforce XPath="/configuration/appSettings/add[@key='Microsoft.ServiceBus.OverrideAutoDetectMode']" />
- If the <enforceSettings> change is NOT being used, open the Connector Configuration Panel and disable auto-updates to avoid the changes from being overwritten at the next update.
- Save the changes
- Restart the connector service to invoke the changes.
This will be fixed in a future release of the Centrify Cloud Connector.