New Features

The following table describes the major features that are introduced in this release.
Major Features in 22.8R2 |
||
---|---|---|
Support for Lets Encrypt Certificates in vTM - This enhancement will allow vTM customers using Let's Encrypt certificates to renew them via widely supported ACME challenge types, such as HTTP-01 andDNS-01. Currently CloudFlare Domain provider is Supported. |
||
Pulse Secure Virtual Web Application Firewall Features | ||
The Traffic Manager will install version 4.10-14 of Pulse Secure Virtual Web Application Firewall (vWAF). Version 4.10-0 included a number of important internal updates, including migrating the codebase to Python 3. Before upgrading from version 4.9-x to version 4.10-x, users must ensure that any Python scripts they have included in script libraries are compatible with Python 3. Resource Requirements now includes a recommendation that virtual appliances running vWAF should have a RAM allocation of at least 4GB. Version 4.10-x of vWAF should be expected to consume approximately 500MB more system RAM than previous versions. |

The following table describes the major features that are introduced in this release.
Pulse Secure Virtual Web Application Firewall Features | ||
The Traffic Manager will install version 4.10-13 of Pulse Secure Virtual Web Application Firewall (vWAF). Version 4.10-0 included a number of important internal updates, including migrating the codebase to Python 3. Before upgrading from version 4.9-x to version 4.10-x, users must ensure that any Python scripts they have included in script libraries are compatible with Python 3. Resource Requirements now includes a recommendation that virtual appliances running vWAF should have a RAM allocation of at least 4GB. Version 4.10-x of vWAF should be expected to consume approximately 500MB more system RAM than previous versions. |

The following table describes the major features that are introduced in this release.
Major Features in 22.7R4 |
Openssl version used by vTM is updated to 3.0.13. |
Pulse Secure Virtual Web Application Firewall Features |
The Traffic Manager will install version 4.10-12 of Pulse Secure Virtual Web Application Firewall (vWAF). Version 4.10-0 included a number of important internal updates, including migrating the codebase to Python 3. Before upgrading from version 4.9-x to version 4.10-x, users must ensure that any Python scripts they have included in script libraries are compatible with Python 3. Resource Requirements now includes a recommendation that virtual appliances running vWAF should have a RAM allocation of at least 4GB. Version 4.10-x of vWAF should be expected to consume approximately 500MB more system RAM than previous versions. |

The following table describes the major features that are introduced in this release.
Major Features in 22.7R2 |
Support for life cycle management features for nSA platform integration With this feature enabled, upon integration with nsa platform, vTM can be rebooted, restarted and upgraded or rollback from nsa admin UI. |
Pulse Secure Virtual Web Application Firewall Features |
The Traffic Manager will install version 4.10-7 of Pulse Secure Virtual Web Application Firewall (vWAF). Version 4.10-0 included a number of important internal updates, including migrating the codebase to Python 3. Before upgrading from version 4.9-x to version 4.10-x, users must ensure that any Python scripts they have included in script libraries are compatible with Python 3. Resource Requirements now includes a recommendation that virtual appliances running vWAF should have a RAM allocation of at least 4GB. Version 4.10-x of vWAF should be expected to consume approximately 500MB more system RAM than previous versions. |

The following table describes the major features that are introduced in this release.
Major Features in 22.7R1 |
Support for vTM analytics on nSA Platform (Preview). This enables vTM to export analytics data to nSA platform. |
Pulse Secure Virtual Web Application Firewall Features |
The Traffic Manager will install version 4.10-11 of Pulse Secure Virtual Web Application Firewall (vWAF). Version 4.10-0 included a number of important internal updates, including migrating the codebase to Python 3. Before upgrading from version 4.9-x to version 4.10-x, users must ensure that any Python scripts they have included in script libraries are compatible with Python 3. Resource Requirements now includes a recommendation that virtual appliances running vWAF should have a RAM allocation of at least 4GB. Version 4.10-x of vWAF should be expected to consume approximately 500MB more system RAM than previous versions. |

The following table describes the major features that are introduced in this release.
Pulse Secure Virtual Web Application Firewall Features | ||
The Traffic Manager will install version 4.10-10 of Pulse Secure Virtual Web Application Firewall (vWAF). Version 4.10-0 included a number of important internal updates, including migrating the codebase to Python 3. Before upgrading from version 4.9-x to version 4.10-x, users must ensure that any Python scripts they have included in script libraries are compatible with Python 3. Resource Requirements now includes a recommendation that virtual appliances running vWAF should have a RAM allocation of at least 4GB. Version 4.10-x of vWAF should be expected to consume approximately 500MB more system RAM than previous versions. |

The following table describes the major features that are introduced in this release.
Pulse Secure Virtual Web Application Firewall Features | ||
The Traffic Manager will install version 4.10-9 of Pulse Secure Virtual Web Application Firewall (vWAF). Version 4.10-0 included a number of important internal updates, including migrating the codebase to Python 3. Before upgrading from version 4.9-x to version 4.10-x, users must ensure that any Python scripts they have included in script libraries are compatible with Python 3. Resource Requirements now includes a recommendation that virtual appliances running vWAF should have a RAM allocation of at least 4GB. Version 4.10-x of vWAF should be expected to consume approximately 500MB more system RAM than previous versions. |

The following table describes the major features that are introduced in this release.
Report Number |
Features |
Description |
VTM-45316, |
OAuthv2.0 Authorization |
OAuth 2.0 authorization framework along with openID is supported in traffic manager which enables user to provide session based restricted access to backend services using OAuth workflow. |
VTM-46013 |
Traffic Manager as an ingress point |
Traffic Manager as an ingress point for Kubernetes infrastructure, and to control Traffic Manager configuration through standard Kubernetes mechanisms. |
VTM-45571, RFE-1417 |
JWT TrafficScript support for parsing, validation, and generation of JWS tokens in a secure way by GUI based key management system |
New TrafficScript functions have been provided to parse, validate and generate JWT tokens. Support is only for JWS tokens and supports algorithms HS256, HS384, HS512, RS256, RS384, RS512, ES256, ES384, and ES512. |

The following table describes the major features that are introduced in this release.
Report Number |
Features |
Description |
VTM-45466, RFE-1417, SR34618 |
JWT TrafficScript support for parsing, validation, and generation of JWS tokens |
New TrafficScript functions have been provided to parse, validate and generate JWT tokens. Support is only for JWS tokens and supports algorithms HS256, HS384, HS512, RS256, RS384, RS512, ES256, ES384, and ES512. |
Pulse Secure Virtual Web Application Firewall Features |
||
The Traffic Manager will install version 4.10-7 of Pulse Secure Virtual Web Application Firewall (vWAF). Version 4.10-0 included a number of important internal updates, including migrating the codebase to Python 3. Before upgrading from version 4.9-x to version 4.10-x, users must ensure that any Python scripts they have included in script libraries are compatible with Python 3. Resource Requirements now includes a recommendation that virtual appliances running vWAF should have a RAM allocation of at least 4GB. Version 4.10-x of vWAF should be expected to consume approximately 500MB more system RAM than previous versions. |

The following table describes the major features that are introduced in this release.
Report Number |
Features |
Description |
VTM-43929, |
Update Appliance base operating system to Ubuntu 20.04 |
The base operating system of the appliances has been updated to Ubuntu 20.04.3. This ensures Ubuntu standard support until April 2025 for the operating system components. The following appliance form factors have their base OS changed: Docker, VMWare vSphere, Microsoft Hyper-V, KVM, Amazon EC2, Microsoft Azure, Google Cloud Engine and Bare Metal Server. Citrix Xen appliance with the updated OS is not published as part of this release. This will be included in a future release. There are no changes in the installation or upgrade procedures for the on-premise or cloud virtual appliances. Installation procedure using PXE boot has changed, where the installation ISO image needs to be served through a web server. Please refer to the "Appliance Image Installation and Getting Started Guide" for more information. |
VTM-45384, |
Base64URL Encode/Decode |
Support for a new TrafficScript function string.base64urlencode() has been added which helps in encoding a given input to a URL and filename safe base64URL format. Added support for TrafficScript function string.base64urldecode() which can be used for base64URL decoding. |
Pulse Secure Virtual Web Application Firewall Features |
||
The Traffic Manager will install version 4.10-7 of Pulse Secure Virtual Web Application Firewall (vWAF). Version 4.10-0 included a number of important internal updates, including migrating the codebase to Python 3. Before upgrading from version 4.9-x to version 4.10-x, users must ensure that any Python scripts they have included in script libraries are compatible with Python 3. Resource Requirements now includes a recommendation that virtual appliances running vWAF should have a RAM allocation of at least 4GB. Version 4.10-x of vWAF should be expected to consume approximately 500MB more system RAM than previous versions. |