Downloading
All supported versions of the AppGate ZTNA client can be obtained from AppGate's secure Download Center. Mobile apps, including iPadOS and Chrome OS, are available from the appropriate app stores. Various special clients are also available, such as those for use on terminal servers or unattended machines that are required to connect through the AppGate ZTNA system. Once a Portal appliance has been deployed, users can also connect using any of the most popular browsers.
Deployment
It is possible to automate the initial deployment process.
NOTE
If you want to script/automate the distribution of the client when a new version appears, AppGate always posts the latest versions here with a static URL.
There are details covering all the different operating systems in the Client deployment and management section. We try to maintain forwards and backwards compatibility across five versions of the client.
Installation
All clients use standard native installers for the target operating system, so installation requires no special configuration.
NOTE
All clients except the Windows lite client require administrator rights to install.
At installation time, a unique device ID is derived from the system. This device ID forms the first part of the system claim ag.distinguishedName which also includes the user name and the identity provider. This is what allows the AppGate ZTNA Collective to manage every user session on an individual basis.
The client is designed to support multiple languages. This does not need to be set as the client is locale-aware and uses this to automatically switch languages. English, French, Spanish, Portuguese, and Japanese are currently supported.
Configuration
The combination of client profiles and device policies make a powerful way to configure your devices and the AppGate ZTNA clients. The system provides the capability to simultaneously tailor the device and the client's appearance and behavior to suit different user communities.
At first use, a client profile is required before connecting to the Collective. The client profile can be added during installation, when the client is first launched, or when it is running. Client profiles need to be created and exported, then installed into users/devices and/or selected for use in the Portal in User Access Settings.
Once the profile is there, an account is set up, and a policy/entitlement configured, then a user with valid credentials can authenticate to the Collective. The profileName claim will be returned from the client as a device claim. This claim can optionally be used in the assignment criteria to pick a specific device policy. This in turn can be used to impose specific device and client configurations.
Help with installation
See User/Device troubleshooting for more help if the client cannot connect. The user guide for clients can be found here.