# Network proxy support
## Overview
The Trust1Connector allows running in a system where a network proxy is defined. Basic authentication on this is also supported.
When it will try to synchronise with the Distribution Service it will automatically detect if a network proxy is defined and provide with OS dialogs to enter the username and password if basic authentication is required.
These credentials are stored in the `proxy.json` file in the installation folder of the Connector. If you have changed your username, password or connecting to a different proxy the `proxy.json` should be deleted and the connector will ask the credentials upon next synchronisation moment.
## Curl and Proxy
If your package uses CURL for specific reasons a proxy should not be set via the `HTTP_PROXY` and `HTTPS_PROXY` system environment variables. Curl will use these no matter which URL you are trying to access.
This will cause issues with internall communication of the Trust1Connector, causing the API and Registry to not be able to communicate with eachother.
## MacOS
### Squid 4.14
{% hint style="warning" %}
Apple sillicon has `/usr/local/` in a different location. Use `/opt/homebrew/` instead
{% endhint %}
Install squid
```bash
brew install squid
```
Start squid service
```bash
brew services start squid
```
Squid config file is stored at `/usr/local/etc/squid.conf`. (`/opt/homebrew/etc` on apple sillicon)
Comment or remove following line:
```
http_access allow localnet
```
Then similar to linux config (but with updated paths) add this:
```
auth_param basic program /usr/local/Cellar/squid/4.8/libexec/basic_ncsa_auth /usr/local/etc/squid_passwords
auth_param basic realm proxy
acl authenticated proxy_auth REQUIRED
http_access allow authenticated
```
Note that path to `basic_ncsa_auth` may be different since it depends on installed version when using `brew`, you can verify this with `ls /usr/local/Cellar/squid/`. Also note that you should add the above just bellow the following section:
```
#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
#
```
Now generate yourself a user:password basic auth credential (note: `htpasswd` and `htdigest` are also both available on MacOS)
```bash
htpasswd -c /usr/local/etc/squid_passwords username_you_like
```
Restart the squid service
```bash
brew services restart squid
```
#### Update network settings
Go to the network settings, on `Ethernet` or `Wifi` and click advanced
In the advanced view, go to `proxies` and enable both HTTP and HTTPS web proxy.
After that fill in the proxy server and port. The username and password can be provided optionally (for testing we let the applications handle this)
Save these settings, and you will now get a pop-up when the Trust1Connector needs to authenticate for the proxy.
Fill in both here and when it's correct this will connect with the Distribution server once again.
### Proxyman
{% hint style="info" %}
Proxyman does not support basic authentication
{% endhint %}
You can downoad proxyman here;
When opening it will automatically proxy all the requests of the system by automatically setting the network settings on your system.
Now your system has a proxy that can be used for testing the Trust1Connector application. ( will be automatically detected )
## Windows
### Squid 4.14
#### cygwin
Install cygwin via [www.cygwin.com](https://www.cygwin.com)
Install the **libcrypt2** library.
When installation is done, copy the libcrypt dll to squid, to make sure authentication works with squid
#### Squid
install squid from
When you click “Finish” the installation process is finished. You should see a squid application appearing in the tray. This application allows you to start/stop the squid service as well as change the squid configuration.
During installation the MSI installer opened TCP port 3128 required to connect to your Squid instance from another machines in your network. If for some reasons this does not work or works not as expected please follow these steps to open required TCP ports.
Type “Windows Firewall with Advanced Security” in the Start Search string on Windows 7 or 8 and press Enter. Click “Inbound Rules” and then “New Rule”.
Create an inbound rule to allow clients connect to the 3128 TCP port, the default port where squid is running.
Now we can configure the `squid proxy` to enable basic authentication for our tests. First we'll configure the squid config.
For this you can use the configuration below. Line 51-54 are the most important + we comment all the `http_access allow` variables except the `ncsa_users` one
```
#
# Recommended minimum configuration:
#
# Example rule allowing access from your local networks.
# Adapt to list your (internal) IP networks from where browsing
# should be allowed
acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
acl localnet src 172.16.0.0/12 # RFC1918 possible internal network
acl localnet src 192.168.0.0/16 # RFC1918 possible internal network
acl localnet src fc00::/7 # RFC 4193 local private network range
acl localnet src fe80::/10 # RFC 4291 link-local (directly plugged) machines
acl SSL_ports port 443
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443 # https
acl Safe_ports port 70 # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535 # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl CONNECT method CONNECT
#
# Recommended minimum Access Permission configuration:
#
# Only allow cachemgr access from localhost
# http_access allow localhost manager
http_access deny manager
# Deny requests to certain unsafe ports
http_access deny !Safe_ports
# Deny CONNECT to other than secure SSL ports
http_access deny CONNECT !SSL_ports
# We strongly recommend the following be uncommented to protect innocent
# web applications running on the proxy server who think the only
# one who can access services on "localhost" is a local user
#http_access deny to_localhost
#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
#
auth_param basic program "/cygdrive/c/squid/lib/squid/basic_ncsa_auth.exe" "/cygdrive/c/squid/etc/.htpasswd"
acl ncsa_users proxy_auth REQUIRED
http_access allow ncsa_users
# Example rule allowing access from your local networks.
# Adapt localnet in the ACL section to list your (internal) IP networks
# from where browsing should be allowed
# http_access allow localnet
# http_access allow localhost
# And finally deny all other access to this proxy
http_access deny all
# Squid normally listens to port 3128
http_port 3128
# Uncomment the line below to enable disk caching - path format is /cygdrive/, i.e.
#cache_dir aufs /cygdrive/d/squid/cache 3000 16 256
# Leave coredumps in the first cache dir
coredump_dir /var/cache/squid
# Add any of your own refresh_pattern entries above these.
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
refresh_pattern . 0 20% 4320
dns_nameservers 8.8.8.8 208.67.222.222
max_filedescriptors 3200
```
Next up we'll configure our user. We need to go to the squid folder for this.
In `etc` we will store a `.htpasswd` file which will contain our. You can create the user that needs to be stored in this file in
after this you can **stop** and **start** the squid service
The server side configuration is over. Now let’s configure the client side. For that you have to specify the proxy in the network settings
Provide the manual proxy server with ip `127.0.0.1` and port `3128` now you can save and test the Trust1Connector