Profiles seed clients, allowing them to connect to Controllers. They can be installed manually, managed by a device policy, or used in client profile groups.
Profile groups are used for Cross-Collective high availability (HA). The client automatically tries the next profile when none of the Controllers are available for the current profile.
A client profile includes a profile name and the minimum information required for a client to connect to an AppGate ZTNA Controller. The resulting elements are:
The DNS name for the Controller(s)
An identity provider (IdP) the user authenticates against
The profile name that appears in the client
The single packet authorization (SPA) details—name and key—used to establish a TCP connection to the Controller
The fingerprints of the current CA and next CA, used to verify the Controller is genuine
The DNS name and IdP together define a unique profile. When you update a profile—changing the name, SPA, or CA—the system replaces the existing profile because the DNS name and IdP are unchanged. If you create a new profile with a unique DNS name or IdP, the system treats it as an additional profile.
To distribute a replacement profile—for example, when the CA has been renewed or the SPA key is compromised—create a new profile with a new name but the same DNS name and IdP. The new name lets you manage distribution within your organization. When installed on the client, the new profile replaces the existing one. After all clients have the new profile, you can delete the obsolete one.
Profile elements
DNS name. The DNS name resolves to one or more Controller instances. See Adding a Controller for DNS requirements.
IdP. AppGate ZTNA supports many IdPs configurations. Set one as the default so users can authenticate with their standard credentials.
Profile name. The profile name is the display name on the main screen of the client. From a security perspective, the name should help users identify which Collective they are signing in to.
SPA. Single Packet Authorization (SPA) prevents external connections to appliances without the correct SPA key. The profile includes the SPA key name and the key. The SPA key name is derived from the profile name; the SPA key is derived from the SPA key name. For a given Collective, a client profile named “fred” always generates the same SPA key. This is useful if a client profile is accidentally deleted.
Different profiles have different SPA keys, which is useful when you need to serve different types of users. You can issue one profile containing one SPA key to corporate users and a different profile to third-party users. This limits the distribution of your corporate SPA key. If a third-party SPA key is compromised, corporate users do not need a replacement profile. The SPA key name can be checked using the spaKey device claim, which is reported when a user signs in, and can be used to assign policies.
NOTE
SPA handshake packets must be received before the system can establish a TLS connection with an appliance. SPA packets on port 53 (UDP) and port 443 (UDP and/or TCP) are always sent regardless of the Global Settings SPA configuration. This is because the connecting device does not know the configuration of the receiving device.
For TCP SPA, the packet sent to port 443 (TCP) must be allowed through.
For UDP-TCP SPA, packets are sent to port 53 (UDP) and 443 (UDP). At least one must get through. If TLS is used for the tunnel, the system also performs TCP SPA, so the packet sent to port 443 (TCP) must be allowed through as well.
See Troubleshooting user and device access for more details about how SPA works.
CA Certificates. To establish TLS connections, the client must trust the Controller's certificate. The profile includes the fingerprint of the Controller's CA, which the system uses to cryptographically verify the Controller's authenticity. This mitigates man-in-the-middle attacks on first use. The next CA fingerprint is also included to make CA switches easier when using automation—for example, when you have an immutable image (k8s or Docker client) that uses a hardcoded profile URL. Without this, a new image would need to be deployed at exactly the moment the CA switches.
Inside the client profile
A client profile always uses the format appgate://<server>/<data-blob>, but the length varies based on the original configuration. The first part is the Controller URL. The second part is the base64-encoded data blob. A complete profile looks like:
appgate://myserver.company.com/eyJzcGEiOnsibW9kZSI6IlRDUCIsIm5hbWUiOi...........
You can decode this base64-encoded data blob using standard online tools. The decoded output contains:
"profileName":"myprofilename",
"spa":{"name":"mykeyname","key":"cd337b2..........453c98828"},
"caFingerprint":"f917fd6a4b.............0bfb18e6",
"nextCaFingerprint":"044b3e061............2c32bf918"
"identityProviderName":"LDAP"