LM-6219 Virtual Services UI: Fixed an issue that caused a Virtual Service to be marked as available (up) when it is actually unavailable (down).
LM-6172 Partner Communication: After setting the same shared secret on both partners, an Unauthorized Remote Machine error is observed. This issue has been fixed.
LM-6162 Partner Communication: Fixed an issue that could mistakenly cause a shared secret password banner to appear on the User Interface (UI) Home page on a non-shared IP address (for example, a stand-by node or non-admin node).
LM-6146 Clustering: Fixed an issue that caused a deleted node to reappear in the configuration after rebooting the admin node.
LM-6006 Partner Communication: Fixed an issue where (in Azure or AWS) GEO partnering did not work once the shared secret is set.
LM-6005 Partner Communication: Fixed an issue where (in Azure or AWS) High Availability (HA) mode did not work once the shared secret is set.
LM-5988 GEO: Fixed an issue that allowed a user logged in with administrative privileges to execute arbitrary commands on the system using a carefully crafted domain modify Application Programming Interface (API) command.
LM-5966 SAML Authentication: Differences in case between the URL and the "IdP Entity ID" parameter cause SAML authentication to fail. This has been fixed by modifying the comparison between the URL and ID to be case-insensitive.
LM-5939 OIDC/OAuth Authentication: An error in state validation can cause users to be logged in incorrectly. This issue has been fixed.
LM-5865 NG Hardware: Fixed an issue where VLANs do not work on 10Gb interfaces.
LM-5638 LDAP Group WUI Authentication: Fixed an issue where LDAP groups did not work with alternate UPNs.
LM-5606 SAML Authentication: Fixed an internal issue where SAML authentication succeeds, but the user is then redirected to an incorrect URL.
LM-5370 Virtual Service API: Modified the way Virtual Service persistence is reported when set to “none” to be consistent with other parameters. In previous releases, the value was omitted when set to “none”; now it is explicitly reported as “none”.
LM-5331 Azure VLM: Fixed issues that could cause the /var/log/waagent folder to fill to capacity.
LM-5305 Console: The system console’s “Show Allowed Addresses” screen was titled “blocked” instead of “allowed”. This issue has been fixed.
LM-5229 Network Telemetry: The Flowmon probe process was not started for an interface without a shared IP address on a system configured in High Availability (HA) mode. This issue has been fixed.
LM-5228 ACME Certificates: Fixed an issue where requesting a new ACME certificate could cause configuration corruption.
LM-4907 Kubernetes Ingress Controller (KIC): Fixed an issue that caused several minutes of delay in displaying the Kubernetes settings.
LM-4403 SSO: Fixed an issue that caused the error message “ssomgr: ERROR: ssomgr too many threads” to appear in the logs, sometimes followed by a segfault.
LM-3164 Remote Logging: Optimized the flow for sending syslog messages to the remote syslog device to reduce local resources consumed.
LM-3127 WAF Custom Rules: Added custom rules validation on upload to flag a CIDR address with a "/32" suffix as an error. The Web Application Firewall (WAF) engine requires single IP addresses to be specified without the “/32” suffix.
LM-3096 WAF Custom Rule Data Files: Fixed an issue where spurious text may be displayed in the UI when uploading a custom rule data file.
LM-3014 PowerShell API: Added a "Confirm" flag to the installpatch API to match the REST API.
LM-2802 GEO Clustering: Fixed an issue that causes spurious log messages to be generated when a system boots that is configured with at least one GEO Cluster.
LM-2777 GEO RestAPI: Fixed a regression in the listclusters API introduced in 7.2.55.0. In that release, the cluster IP address field name was inadvertently changed to “Addr”. With this release, it has been changed to its pre-7.2.55.0 name, "IPAddress".
LM-2767 WAF: Fixed an internal issue where a null character in a request URI could cause truncation of the request before it is examined by the WAF engine, possibly resulting in an incorrect analysis of the URI.
LM-2762 SAML Authentication: Fixed an issue that caused SAML authentication to fail when using 4K key lengths.
LM-2731 OIDC/OAuth Authentication: Fixed an issue where the UI rejects a valid application secret generated from a PowerShell API script.
LM-2651 GEO RestAPI: Fixed an error that results in information regarding a deleted Virtual Service still being displayed in the listclusters API output, after the Virtual Service is deleted.
LM-2627 GEO: Fixed an issue where locations for IPv6 addresses are not returned in a DNS response when specifying an IPv6 address for the EDNS client subnet.
LM-2566 Persistence: Fixed an internal issue that can cause server cookie persistence to break for some requests when 'Always Check Persist' is enabled.
LM-2474 Log Message Priority: Changed the severity level of 'Being too busy...' log messages to Informational (from Error) to reflect its significance.
LM-2470 GEO: Fixed an issue where performing a PTR query on an FQDN (rather than on an IP address in a PTR record) results in a segfault.
LM-2447 GEO Clustering: Fixed issues that caused GEO to misjudge the health of LoadMasters in Clustering mode. GEO Clustering also now works when deployed on a LoadMaster in Clustering mode.
LM-2446 GEO: Fixed a possible internal buffer overflow issue that could be triggered by character expansion.
LM-2439 Logging: Addressed inconsistencies between messages logged for L7 and the SSOMGR in non-debug and debug modes.
LM-2423 ACME Certificates: Fixed an issue where a certificate added to a Virtual Service for re-encryption does not appear in the list of Virtual Services (associated with that certificate) on the ACME certificates page.
LM-2398 Kubernetes Ingress Controller (KIC): Fixed an issue where a manually removed Real Server is not re-added to the Virtual Service by the controller.
LM-2396 PowerShell API: On the KVM platform only, the getall command fails with the message: “Error connecting to device due to Invalid parameter on KVM”. This issue has been fixed.
LM-2357 Clustering: Starting with 7.2.58.0, some Virtual Services in the Cluster may be spuriously marked down due to the incorrect internal processing of Real Server status.
LM-2355 PowerShell API: The Get-ACMEAccountInfo command fails because the type is not specified, but there is no type parameter. This issue has been fixed.
LM-2034 GEO: Since 7.2.55.0, the Real Server Connection selection criteria is not distributing traffic as expected. This issue has been fixed.
LM-1924 PowerShell API: Starting with 7.2.58.0, the Backup-LmConfiguration command returned a 400 error (protocol violation / invalid header name). This issue has been fixed.
LM-1902 Networking: Modified the handling of the default gateway interface so that the IP address of the interface cannot be removed if the default gateway is defined on that interface.
LM-1892 Single Sign On: Fixed an internal issue that could cause a segfault in the SSO Manager process when SAML and Kerberos Constrained Delegation (KCD) were configured.
LM-1878 GEO Custom Locations: Fixed an issue where deleting a Custom Location Name could (under some circumstances) cause the GEO configuration to be corrupted.
LM-1867 Virtual Service Redirects: When an existing port 80 service is modified to redirect traffic to port 443, the Error Page still takes precedence when changing the Status Code from 200 to another Status Code. This issue has been fixed.
LM-1830 GEO: When using manual site recovery a "Failing" IP remains "Failing" even if it has come back up. This issue has been fixed.
LM-1800 Azure VLM: Fixed issues that could cause the /var/log/waagent folder to fill to capacity.
LM-1743 FIPS Mode Custom Cipher Sets: Fixed an issue where, after changing the system into FIPS mode, custom cipher sets still contained restricted ciphers.
LM-1709 Virtual Services: Addressed issues that caused a Virtual Service to stop responding to requests randomly when a specific number of content rules have been created.
LM-1450 GEO API: Fixed an issue where "Zone Name" and "ZOA Email" are missing from the Miscellaneous GEO Parameters returned by the API.
LM-1370 REST API: Fixed an issue that caused the unlockdomainusers API to return success when the user has not been unblocked, or when a parameter is incorrect.
LM-1342 Kubernetes Ingress Controller (KIC): Fixed an issue that caused the ingress controller to stop working when the default admin gateway is changed.
LM-1340 GEO UI: Clarified the error message received on adding an FQDN that contains more than the permitted number of characters.
LM-1325 ACME Certificates: Fixed an issue that could cause the certificate creation page to be only partially displayed.
LM-1323 Automated IP Access List Data Update: Improved the error message received when a download of the list fails.
LM-968 Online Certificate Status Protocol (OCSP): Modified connection processing for OCSP servers that have keepalive enabled.
LM-137 Kerberos Constrained Delgation (KCD): Fixed an issue that caused multiple logs to be written for a single login failure.
LM-123 GEO UI: Modified the default values for location coordinates so that they are the same across the UI.
LM-116 Real Time Statistics: Fixed an issue where the “Current rate - Conns/sec” under RS Totals does not match the “Current rate - Conns/sec “under Real Servers.