When selecting in the connector to use a Bluecoat web-proxy, this article goes over what to check for and do to get around any issues.
Question: Does Centrify have any limitations setting up to use a Bluecoat web-proxy for the connector service?
Answer: There are some main limitations to keep in mind when it comes to using a Bluecoat web-proxy.
The TCP relay connection of the connector cannot be 're-encrypted' by the Bluecoat web proxy, it needs to be a straight tunnel to the tenant. Also note that the TCP relay tunnel HTTP for purposes of the proxy as well. The correct way this should set up a straight tunnel without re-encrypt.
When registering the connector, the connector service will also reach out to edge.centrify.com to determine if there is a newer connector version than the one being used. The registration will fail if the connection to edge.centrify.com is blocked. Ensure that this domain is whitelisted in the firewall settings as well.
If whitelisting the domain mentioned above is not an option, uncheck the "enable auto-update" option in the Connector Configuration window.
Alternatively, edit the registry settings in \HKEY_LOCAL_MACHINE\SOFTWARE\Centrify\Cloud and add the autoUpdateEnabled REG_DWORD entry and set the value to 0.