Client types
There are two types of Linux client. For a quick overview of the differences, see the Client compatibility matrix.
The following table lists the Linux client types, the use each is designed for, and the installer filename pattern:
Type | Designed for | Filename pattern |
|---|---|---|
Normal enterprise usage, including pre-installation as part of standard builds. |
| |
Installation on unattended machines such as servers. |
|
Confirm that the client version is compatible with the associated operating system version. See the Downloads page.
The full client is installed using the command line (or a desktop installer app) but is intended for use by a user in a desktop environment. The headless client is installed and configured to run as a service entirely using the command line
Downloading the client
See the Downloads page, or use the commands found in the full or headless articles.
Installing and running the client
There are separate installers for the full and headless clients. See the article for each type for exact commands.
Configuration settings
Find client settings in ~/.config/appgatesdp-service.
In ~/.config/appgatesdp-service/user.settings, find <configuration><appSettings> and:
To skip the data usage acceptance screen on first launch:
<add key="userApprovalPref" value="True" />To prevent device claim scripts from running (these run with full administrator privileges and present a security risk):
<add key="scriptsDisabledPref" value="True" />
The following table lists common configuration tasks:
Task | Details |
|---|---|
List local firewall rules |
Look for the |
Clean all client settings |
|
Remove a profile link |
|
Remove all stored passwords and certificates |
|
DNS configuration
The client includes a set_dns script that changes network configuration so that AppGate ZTNA domains use AppGate ZTNA DNS while regular DNS resolves everything else. It runs a local DNS resolver (dnsmasq) named appgate-resolver, or systemd-resolved if detected, and resets the network configuration on disconnect.
The set_dns script requires:
dnsmasqdbussystemdas PID 1
This was tested against network-manager and wicd.
Because the built-in script cannot cover every network configuration, you can write a custom script that uses the same command-line interface. For more information, run:
/opt/appgate/linux/set_dns --help
journalctl -u appgatedriver.service | grep set_dnsYou can configure a custom script that uses the same command-line interface in /etc/appgate.conf to replace the built-in one.
Troubleshooting
If the network configuration is left in an incorrect state, restore it with the following:
/opt/appgate/linux/set_dns --reset=
chattr -i /etc/resolv.conf
mv /etc/resolv.appgate /etc/resolv.confThen restart your network manager.
Verifying package files
AppGate signs Linux installer packages with GPG using the AppGate public key. Use the relevant tools for each distribution to verify package validity. The client installs the key at /opt/appgate/appgate.gpg. You can also download the key from appgate.pub.
Fingerprint
F36B 319B CE07 48F7 7930 52E6 F600 207F 0680 FA29
Fedora
Verification requires the rpm package, which RPM-based distributions install by default.
Import the AppGate public key:
sudo rpmkeys --import appgate.pubIf using the keyring installed with the client, export the key before importing:
gpg --keyring /opt/appgate/appgate.gpg --export --armor > appgate.pubVerify the package:
rpmkeys --checksig PACKAGENAMEUbuntu
Install dpkg-sig:
sudo apt install dpkg-sigImport the AppGate public key:
gpg --import appgate.pubOr, if using the keyring installed with the client:
gpg --import /opt/appgate/appgate.gpgVerify the package:
dpkg-sig --verify PACKAGENAME