Corporate Proxy Helper VS ArcGIS

In a corporate network environment it is very common that a proxy is deployed to secure all outgoing internet communication. The problem is that these proxies normally rely on specific Windows clients functionality, like NTLM authentication, PAC proxy scripts and Kerberos. Also, the SSL certificates injected by the corporate proxy are only installed in the Windows certificate store and only few specific applications like web browser and some Microsoft tools are able to "understand" all of this.

Specially for software development teams inside your company, they will use all sort of open-source tooling like Git, NodeJs, Java and many others that will NOT understand Windows-specific authentication protocols and SSL certificates. As result, the people working in these teams will spend countless hours dealing with HTTP proxy configuration errors and also will configure these tooling to ignore SSL validation errors, which is very harmful for your company!

Corporate Proxy Helper is designed to mitigate these problems and works as a layer that enables such apps and services to authenticate via NTML, Kerberos or even PAC scripts. It also solves the problem of errors with Windows-only SSL certificates by exporting them into other formats which are understood by the open-source tooling. By the way, it also has a nice set-and-forget GUI.

Then your development team can focus only on what they should be focused: not on environment configuration problems but on coding only!