--- title: "Version 7.0.x" slug: "releasenotes-v7-0-x" updated: 2026-11-16T08:48:15Z published: 2026-11-16T08:48:15Z canonical: "support.appgate.com/releasenotes-v7-0-x" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # Version 7.0.x | [***Before upgrading***](/v1/docs/releasenotes-v7-0-x#before-upgrading) | [***Upgrading with sdpctl***](/v1/docs/releasenotes-v7-0-x#upgrading-with-sdpctl) | [***Feature Deletions and Deprecations***](/v1/docs/releasenotes-v7-0-x#feature-deletions-and-deprecations) | | --- | --- | --- | | [***Known Issues***](/v1/docs/releasenotes-v7-0-x#known-issues) | | | > [!NOTE] > NOTE > > If a release does not specify *Appliance* or *Client*, then it relates to both. ## Before upgrading Consider the following before performing an upgrade: - Get the appliance upgrade file from the [Downloads](/v1/docs/downloads-v7-0) page and place the file where sdpctl can use it: on your local PC or on a web server the Controller can access. - Read the [Known issues](/v1/docs/releasenotes-v7-0-x#known-issues) related to the release. - Refer to the latest recommendations for [instance sizing](/v1/docs/instance-sizing-v7-0). - Check compatibility information for your operating system and hosting environments on the software download page for the release. - Check that any customizations you have installed on the appliances do not address issues that have been fixed in the new version. Temporary customizations should be removed and the system rebooted before starting an upgrade. - Create a backup of the current appliance and move the backup file off the device. See [Backup and restore](/v1/docs/backup-and-restore-v7-0) for information on how to create a backup. - Make a note of the primary Controller that sdpctl is using. You will need to know which Controller initiated the upgrade if you need to roll back. ### AppGate ZTNA Compatibility Appliance compatibility is tested for a maximum of two versions back, so a 7.0 Controller will work with 6.6 Gateways. AppGate ZTNA client versions should be kept within two versions of AppGate ZTNA appliances. For example, when using 6.6 appliances, clients must be on a version from 6.4 through 7.0. > [!CAUTION] > ⚠ **Action Required Before Upgrading Clients to Version 7.0** > > Make sure that your appliances are running 6.6.4, 6.7.2, 7.0.0, or a later patch version. Otherwise the Clients will not be able to communicate with the Collective. ### Upgrading Between Versions AppGate ZTNA appliance upgrades are allowed from a maximum of two versions back. For example, an upgrade from 6.6 to 7.0 is permissible, but an upgrade from 6.5 to 7.0 is not. Customers running AppGate ZTNA 6.5 would have to upgrade to 6.6 or 6.7 before then upgrading to 7.0. ### Downloads | Supported installers and upgrade files | [Downloads](/v1/docs/downloads-v7-0) | | --- | --- | | Client software and client compatibility information | [Downloads](/v1/docs/downloads-v7-0) | | sdpctl, API specs, k8s operator, Terraform provider, cloud marketplace | [Tools & Utilities](/v1/docs/tools-utilities) | ## Upgrading AppGate ZTNA with sdpctl To upgrade AppGate ZTNA, use the latest release of [sdpctl](https://appgate.github.io/sdpctl/) available in [Github](https://github.com/appgate/sdpctl/releases). sdpctl is available for all the main OS platforms. > [!NOTE] > NOTE > > It is critical to take a snapshot or backup of your Controller prior to upgrading. If the upgrade fails before the first Controller is configured and working, then you can use the switch partitions option to revert the upgrade. > > If the first Controller is working and something fails when upgrading the other Controllers, the switch partitions option cannot be used as this will break the one working Controller. In this situation the only way to revert is to restore from backup. sdpctl performs an orchestrated upgrade of all appliances. sdpctl has two phases: the **prepare** phase, and the **complete** phase which is the upgrade itself. The prepare phase performs distribution and verification of the image to avoid damaged files being used. For more detailed information on upgrading with sdpctl, see the [Reference Guide](https://appgate.github.io/sdpctl/). For more details on upgrading appliances, upgrading HA controllers, and backup/restoration, see [Upgrading appliances](/v1/docs/upgrading-appliances-v7-0). #### Prepare phase The prepare phase should be run ahead of time, because in this phase it will: - run a deprecation check and explain why an upgrade may not be able to continue. - distribute all files and perform a verification on them. - set the status of the appliance as ready to upgrade if no issues have been found. - not disturb a running Collective or attempt to perform the actual upgrade. Once any issues discovered during the prepare phase are fixed, run the prepare phase again to ensure you are ready to upgrade. #### Complete phase You will now run sdpctl to upgrade the first Controller. It will roll back automatically if it experiences any database migration errors. After the first Controller migration, the new database schema will be synchronized with additional Controllers. The remaining Controllers are then upgraded. > [!NOTE] > NOTE > > Because of the mixed schemata, if an upgrade fails on the remaining Controllers, there is no way to automatically roll back. To revert the upgrade at this point, you must go back to a single Controller and re-enable additional Controllers. Refer to [Upgrading appliances](/v1/docs/upgrading-appliances-v7-0) for more details. The remaining appliances are then upgraded in a pre-ordained order that is defined by AppGate but at [a rate that can be defined in sdpctl](https://appgate.github.io/sdpctl/sdpctl_appliance_upgrade_complete.html). If an appliance goes offline during the upgrade process, it can be brought back online by restarting the cz-config daemon with the command `sudo service cz-configd restart` > [!NOTE] > NOTE > > AppGate recommends testing all upgrades in a development environment to verify that upgrades are successful and don't cause integration problems with third-party solutions or local client tools. ## Version specific upgrade issues ### Upgrading to version 7.0.x - You need to be on v6.6.0 or later to perform this upgrade. - During the upgrade of the first Controller there will be a 30-60 second window in which the Controllers do not accept new client connections. This will be perceived by the user as a delay in the connection. Token renewals are not affected. - The Gateway will temporarily auto-suspend accepting new sessions when memory usage, the number of user sessions, or the event queue reach certain thresholds. These thresholds can be found in the "Gateway Failover when it is suspended" section of the [High availability](/v1/docs/high-availability-ha-v7-0) page. Check the appliance utilization before upgrading to avoid hitting those thresholds. - It is not possible to run appliances on ESX7.0.0. This is due to a bug that is fixed in ESX7.0.1. Please upgrade to the latest version available. - Gateways will download geolocation data from [https://bin.appgate-sdp.com](https://bin.appgate-sdp.com) (preferred) in addition to [https://updates.maxmind.com](https://updates.maxmind.com). Both must be allowed in the firewall. - Review the [removed API endpoints](/v1/docs/releasenotes-v7-0-x#removed). If you use any endpoints or fields that have been removed, migrate to their current equivalents before you upgrade to 7.0. - If a Site used QUIC in AppGate ZTNA 6.7 or earlier, the database stored its TLS version as TLSv23. The upgrade to 7.0 now changes this value to TLSv1.3 so the Site works with the 7.0 Controller. You don't need to take any action. - Ax-M2 hardware appliances cannot be upgraded version 7.0.0. If you attempt the upgrade, the appliance may freeze during boot and need a manual power cycle. To recover, power cycle the appliance and select the previous version from the boot menu. To run the latest version on an Ax-M2 appliance, do a clean install from USB. ## Feature Deletions and Deprecations ### Removed - The **Risk Model** page (Access > Risk Model). - IdP DNS settings. A [migration guide](/v1/docs/migrating-dns-settings-v7-0) is available. - The ***Object Class*** field from LDAP and LDAP Certificate identity providers. - The **Red Hat 8** fields from Client Auto-Update. - TLSv1.2, TLSv23, and DTLS protocols. - The **Run Analysis** button from the **Discovered Apps** page. - Removed the following deprecated API endpoints: - The `appliances` stats and `active-sessions` stats endpoints - All risk model endpoints - All token record endpoints - The `gateways` field on active sessions - The `riskSensitivity` field on entitlement - `redHat8` from auto-update settings - The identity provider `dnsServers`, `dnsSearchDomains`, and `blockLocalDnsRequests` fields - The LDAP provider `objectClass` field - Related admin message metadata ### Deprecated Support for the following has been deprecated and will be removed in an upcoming release: - AppGate ZTNA 7.0 is the last release that supports the macOS client on Intel-based (x64) Macs. This change follows Apple’s move away from Intel-based Macs. For details, see [Apple’s announcement](https://support.apple.com/en-us/102527). - The use of host entries for entitlements with the `domain://` prefix or any entries that have a glob pattern without a `dnsfwd://` prefix. - The `/home` shortcut to the Dashboard. If you have bookmarked `/home`, update your bookmark to point directly to the Dashboard. - Elasticsearch 6 on the LogForwarder. - Legacy syntax for resolver resource names. SDPCTL can be used to convert to the new common JSON syntax. - The following fields from their respective APIs: - `vpn.dtls` in `/admin/sites` - `cz-restore` (use `cz-config restore`). - API version 21. - Prometheus metric `ctr_client_sign_in_with_mfa`. It is now a label on `ctr_client_authentication`. - The **Service Users** page and related APIs and licenses have been deprecated. ## Known Issues ### NAT traversal - Only 1000 concurrent **relay** sessions are possible for each Connection Broker. ### Application Discovery - Public IPs are not discovered by Application Discovery. This is intentional in order to limit the number of discovered apps and will be enabled in a later version. ### *Authentication* - LDAP error “cannot connect to the server: Network is unreachable” happens if the LDAP server DNS name resolves to both IPv4 and IPv6 on an IPv6-only appliance. ### Traffic tunneling - URL access (HTTP up) does not support NTLM authentication. ### Audit logging - The status of LogForwarders is not always updated to Healthy when they experience a failure to connect to peer LogForwarders during an upgrade. ### Portal - Upstream verification fails for HTTPS endpoints using Let’s Encrypt issued certificates. ### Client #### *Windows* - Auto-update support for SSO clients no longer works as intended so it has been disabled. This feature will be removed in a future release. #### *macOS* - When macOS FileVault is enabled, the headless client will not be started on boot by the operating system until a user who has permission to decrypt the drive logs in. This is a limitation in macOS. #### *iOS* - Memory constraints in iOS mean that the number of sites and entitlements should be kept low (i.e., four sites with average entitlements). A group of appliances configured and managed together.