Client types
There are three types of macOS client. For a quick overview of the differences, see the Client compatibility matrix.
Type | Designed for |
|---|---|
Normal enterprise usage, including pre-installation as part of standard builds | |
Installation on unattended machines such as servers. | |
Normal enterprise usage where an always-on connection to certain protected hosts is required. |
Confirm that the client version is compatible with the associated operating system version. See Downloads for more information.
NOTE
When macOS FileVault is enabled, the operating system does not start the headless client at boot until a user with permission to decrypt the drive signs in. This affects both headless and always-on clients.
Installing macOS clients
The standard installer file installs all elements that the full, headless, and always-on clients require. Each type of macOS client has a page with specific installation details. The default installation operates as a full client. Configuring headless or always-on mode requires additional manual configuration. See macOS headless client for details.
NOTE
Endpoint protection software sometimes interferes with client installation. You may need to allow several client components and executables within the endpoint protection software.
Uninstalling macOS clients
Run the AppGate SDP Uninstaller script in the .dmg file used to install the client. You can choose to keep saved configurations and credentials in the Keychain. The uninstaller removes all other configurations.
NOTE
Never partially uninstall the client—for example, do not remove only the AppGate ZTNA driver.
To manually uninstall the client, run as root:
sudo /Library/Application\ Support/Appgate/interactive-uninstallTo uninstall and remove all secrets stored in the Keychain, run as root:
sudo /Library/Application\ Support/Appgate/interactive-uninstall --clear-settingsComponents and executables
Upgraded clients may retain some existing paths even when new paths are used. The following table shows only the paths new installations use:
Location | Component/Executable | Description |
|---|---|---|
|
| Contains the |
|
| The virtual network adapter that handles connections to the Gateways. |
| Contains the | |
| Runs with root privileges. Handles auto-update of the client. | |
| Used for headless and always-on clients. | |
| Tool to control the headless client. Requires the | |
| The uninstall script. | |
| Runs with root privileges and full disk access rights. | |
|
| The configuration file containing the parameters required for the headless client to sign in. |
Setting defaults
The following table lists the commands that set default options:
Option | Command |
|---|---|
Skip the data usage approval screen |
|
Prevent device claim scripts from running
|
|
Set multiple default profiles after a fresh install Separate profiles with a semicolon inside quotes, for example": |
|
Set the default attention mode |
|
Prevent the full client from auto-starting at boot |
|
Configuration settings
The following table lists common configuration tasks:
Task | Details |
|---|---|
List local firewall rules |
|
Clean all client settings |
|
Remove a profile link |
|
Remove all stored passwords and certificates |
The following image shows typical AppGate Keychain entries:
|
DNS configuration
The client includes the option to run a custom DNS script. The script tries to change the network configuration when connecting so that AppGate ZTNA domains use AppGate ZTNA DNS while regular DNS continues to resolve everything else. Legacy applications that rely on /etc/resolv.conf for name resolution may require this.
To use a custom DNS script:
Create your script and save it: for example, at
/etc/custom_dns_script.shCreate a new file containing the line:
dns_script=/etc/custom_dns_script.shSave this file as
/etc/appgate.conf
When the client connects, the script is called with --servers <dns-server-ips> --domains <dns-domains>. On disconnect, the script is called with --reset.
