Applicable to Client versions - Windows - v7.1.0 & above | macOS - v6.5.1, 7.1.0 & above | Linux - v5.9.x & above |
Overview
During inSync activation, if the inSync Client has to communicate with the inSync Server through a proxy server, you are prompted to provide the proxy server details to the inSync Client. You can configure the inSync Client for the proxy details by using one of the following methods:
You can leverage the system proxy server settings used by the web browser on your device. The inSync Client can use the same IP address and port number configured for the proxy server. On Windows and Mac, the inSync Client can also reuse proxy settings if you select automatic configuration scripts for your browser. The inSync Client uses SOCKS4, SOCKS5, and PROXY servers for authentication.
You can manually enter the IP address or FQDN and port number of the proxy server on the inSync Client. Suppose your proxy server requires a unique username and password for authentication, and the proxy server uses Kerberos protocol for authentication. In that case, you must provide the FQDN of the proxy server.
You can upload a PAC file or provide its WPAD URL to the inSync Client.
You can choose to detect proxy settings automatically. inSync Client automatically searches for the PAC file location based on the WPAD protocol. Alternatively, you can also select the DHCP (252 option) to allow inSync to detect the proxy settings automatically.
The inSync Client supports both authenticated and unauthenticated access to a proxy server:
If your proxy server requires a unique username and password for authentication, you can enter these credentials details on the inSync Client.
If your organization uses your Active Directory credentials for authentication at the proxy server, the inSync Client automatically facilitates it.
Before you begin
Before you configure the proxy details, contact the administrator for your proxy server information:
Proxy server details. You might need the IP address and port number of the proxy server, the PAC file, or the WPAD URL of the PAC file.
Authentication details for the proxy server.
Proxy type. inSync supports SOCKS4, SOCKS5, and HTTP.
Activate the inSync Client on your device.
To activate the inSync Client on your first device, see Activate the inSync Client on your first laptop.
To add a new device to your inSync account, see Add a new laptop to your inSync account.
To replace a device linked to your inSync account, see Replace a laptop linked to your inSync account.
Configure proxy settings for the inSync Client
Procedure
Start the inSync Client.
On the navigation pane, click Settings.
Click the Network tab.
Click OpenProxy Settings.
Select the Enable Proxy Settings checkboxto configure the proxy settings.
If you want to use system proxy settings, see Configure proxy using system proxy settings.
If you want to use proxy server details, see Configure proxy using proxy server details.
If you want to use a PAC file, see Configure proxy settings using a PAC file.
If you want to use the PAC file URL, you can see Configure proxy settings using the PAC file URL.
If you want inSync Client to automatically detect proxy settings, you can see Configure automatic proxy detection.Click Save.
Configure proxy using system proxy settings
To configure the proxy using system proxy settings:
Start the inSync Client.
On the navigation pane, click Settings.
Click the Network tab.
Click OpenProxy Settings.
Select the Enable Proxy Settings check box to configure the proxy settings.
In the Configure Proxy Server Using list, click System Proxy Settings.
If the inSync Client requires authentication, select the Requires Authentication checkbox. Do not select this checkbox if authentication is not required or if authentication is through your AD credentials.
❗ Important
In case of devices connected to the AD domain, inSync Client uses the Kerberos or NTLM authentication to validate and connect to inSync Cloud using the proxy. Leave the Username and Password field blank.
In case of devices not part of an AD domain, inSync user must type their Username and Password. inSync does not support Kerberos or NTLM authentication in the case of non-AD devices.
NTLM authentication does not work on macOS when using SOCKS5 and HTTP proxy types.
NTLM authentication works on Windows OS when using HTTP proxy type.
In the Username box, enter the proxy username.
In the Password box, enter the proxy password.
Click Save.
Configure proxy using proxy server details
To configure proxy using system proxy settings
Start the inSync Client.
On the navigation pane, click Settings.
Click the Network tab.
Click OpenProxy Settings...
Select the Enable Proxy Settings check box to configure the proxy settings.
In the Configure Proxy Server Using list, click Proxy Server Details.
In the Proxy Server IP Address box, enter the IP address for the proxy server.
In the Port box, enter the port number for the proxy server.
In the Proxy Type list, click the proxy type that your organization is using.
If the inSync Client requires authentication, select the Requires Authentication checkbox. Do not select this checkbox if authentication is not required or if authentication is through your AD credentials.
❗ Important
In case of devices connected to the AD domain, inSync Client uses the Kerberos or NTLM authentication to validate and connect to inSync Cloud using the proxy. Leave the Username and Password field blank.
In case of devices that are not part of an AD domain, inSync user must type their Username and Password. inSync does not support Kerberos or NTLM authentication in the case of non-AD devices.
NTLM authentication does not work on macOS when using SOCKS5 and HTTP proxy types.
NTLM authentication works on Windows OS when using HTTP proxy type.
In the Username box, enter the proxy username.
In the Password box, enter the proxy password.
Click Save.
Configure proxy settings using the PAC file
Start the inSync Client.
On the navigation pane, click Settings.
Click the Network tab.
Click OpenProxy Settings...
Select the Enable Proxy Settings check box to configure the proxy settings.
In the Configure Proxy Server Using list, click Configuration File.
If the PAC file is available on your device, click Choose file to select the file.
In the Proxy Type list, select the proxy type that your organization is using.
If the inSync Client requires authentication, select the Requires Authentication checkbox. Do not select this checkbox if authentication is not required or if authentication is through your AD credentials.
❗ Important
In case of devices connected to the AD domain, inSync Client uses the Kerberos or NTLM authentication to validate and connect to inSync Cloud using the proxy. Leave the Username and Password field blank.
In case of devices that are not part of an AD domain, inSync user must type their Username and Password. inSync does not support Kerberos or NTLM authentication in the case of non-AD devices.
NTLM authentication does not work on macOS when using SOCKS5 and HTTP proxy types.
NTLM authentication works on Windows OS when using HTTP proxy type.
In the Username box, enter the proxy username.
In the Password box, enter the proxy password.
Click Save.
Recommended Pac file format for inSync Client
Proxy auto-config
A proxy auto-config (PAC) file defines how web browsers and other user agents can automatically choose the appropriate proxy server (access method) for fetching a given URL.
A PAC file contains a JavaScript function FindProxyForURL(url, host). This function returns a string with one or more access method specifications. These specifications cause the user agent to use a particular proxy server or to connect directly.
Standard PAC File
By convention, the PAC file is normally named proxy.pac. The WPAD standard uses wpad.dat. The Pac file is expected to contain at least one function:
FindProxyForURL (URL, host), with two arguments and return value in a specific format:
URL: object
host: Host name derived from that URL. Syntactically it is the same string as between :// and the first: or / after that
return "...": String of signatures in the following format
Example:returnValue= type host,":",port,[{ ";",returnValue }];type= "DIRECT" | "PROXY" | "SOCKS" | "HTTP" | "HTTPS" | "SOCKS4" | "SOCKS5"
host= UTF16String (* ECMA262-compatible UTF16 string *)
port= UTF16String (* Digits *)
A standard template of the pac file for inSync client:
Basic pac file: It will return the proxy for all types of connections
Pac file with if else condition around dnsDomainIs(), here *.druva.com connection will go directly, all other connections will go via proxy.
dnsDomainIs(host, domain): Provides true value only if the domain of the hostname matches.host: Hostname from the URL.
domain: Domain name to test the hostname against.
Examples:
dnsDomainIs("www.mozilla.org", ".mozilla.org") // true
dnsDomainIs("www", ".mozilla.org") // false
Pac file with if else condition around shExpMatch(), here *.druva.com connection will go via proxy. In this it will first try proxies in the order of example1, example2 then Example 3.
Pac file with if else condition around shExpMatch(), here *.druva.com connection will go directly. In this, it will only try direct connection.
📝 Note:
If DIRECT is added to the list of proxies, inSync Client always gives preference to the Direct method and ignores all proxy configurations.
Do not use the DIRECT method if you want to use proxy always.
shExpMatch(str, shexp): provides true value if the string matches the specified shell glob expression.
str: is any string to compare (e.g. the URL, or the hostname).
shexp: is a shell expression to compare against.
Examples:
shExpMatch("http://home.netscape.com/people/ari/index.html", "*/ari/*"); // returns true
shExpMatch("http://home.netscape.com/people/montulli/index.html", "*/ari/*"); // returns false
Configure proxy settings using PAC file URL
Start the inSync Client.
On the navigation pane, click Settings.
Click the Network tab.
Click OpenProxy Settings...
Select the Enable Proxy Settings check box to configure the proxy settings.
In the Configure Proxy Server Using list, click Configuration File URL.
If the PAC file is available on a WPAD URL, enter the URL in the text box in the WPAD / PAC file URL.
In the Proxy Type list, select the proxy type that your organization is using.
If the inSync Client requires authentication, select the Requires Authentication checkbox. Do not select this checkbox if authentication is not required or if authentication is through your AD credentials.
In the Username box, enter the proxy username.
In the Password box, enter the proxy password.
Click Save.
Configure automatic detection of proxy
To configure proxy using automatic detection of proxy settings
Start the inSync Client.
On the navigation pane, click Settings.
Click the Network tab.
Click OpenProxy Settings...
Select the Enable Proxy Settings check box to configure the proxy settings.
In the Configure Proxy Server Using list, click Automatically Detect Settings.
In the Proxy Type list, click the proxy type that your organization is using.
❗ Important
inSync, by default, detects the proxy settings using the DNS.
Alternatively, select the Detect using DHCP (252 option) checkbox to allow inSync to detect the proxy settings using DHCP.
If the inSync Client requires authentication, select the Requires Authentication checkbox. Do not select this checkbox if authentication is not required.
❗ Important
In case of devices connected to the AD domain, the inSync Client uses the Kerberos or NTLM authentication to validate and connect to inSync Cloud using the proxy. Leave the Username and Password field blank.
In case of devices that are not part of an AD domain, inSync user must type their Username and Password. inSync does not support Kerberos or NTLM authentication in the case of non-AD devices.
NTLM authentication does not work on macOS when using SOCKS5 and HTTP proxy types.
NTLM authentication works on Windows OS when using HTTP proxy type.
In the Username box, enter the proxy username.
In the Password box, enter the proxy password.
Click Save.
Proxy support for Windows:
Proxy Protocol | Authentication |
HTTP | Basic Authentication, Kerberos & NTLM |
SOCKS5 | Basic Authentication & Kerberos |
SOCKS4 | Basic Authentication |
Proxy support for macOS:
Proxy Protocol | Authentication |
HTTP | Basic Authentication & Kerberos |
SOCKS5 | Basic Authentication & Kerberos |
SOCKS4 | Basic Authentication |