Issues Resolved
- Last Updated: December 1, 2023
- LoadMaster
- LoadMaster LTSF
- Documentation
| LM-3143 | SSO Logging: Fixed an issue that caused "No such file or directory" logs being displayed while restarting the SSO management process. |
| LM-3131 | Azure: Fixed an issue in Azure deployments where the /var/log/waagent folder is filled and is not automatically cleared as needed. |
| LM-3129 | Custom Cipher Sets (FIPS mode): In previous releases, upgrading a system in FIPS mode to a version that does not support some of the ciphers configured into a custom cipher set, those ciphers remain available in the custom cipher set after upgrade. This issue has been fixed. |
| LM-3098 | RestAPI restorecert (FIPS mode): Fixed an issue that caused the restorecert API to fail when restoring certificates from a system in non-FIPS mode to a system in FIPS mode. |
| LM-2446 | GEO: Fixed a buffer overflow issue that could cause a system crash and resulting denial of service. |
| LM-2137 | Health Checking: Fixed an issue that caused health checks to fail when the associated LDAPS endpoint server is unavailable. |
| LM-2136 | Single Sign On (SSO): Fixed an issue observed on LM-X15 hardware where SSO logins are slow or fail under heavy load. |
| LM-2135 | Single Sign On (SSO): Fixed an issue that could cause a user authenticating via NTLM + KCD to gain access with an invalid domain and password. |
| LM-2131 | High Availability (HA): Fixed stability issues with failover where the passing of control from the currently active unit to the standby unit fails or results in control being re-assumed by the currently active unit when this behavior is not enabled. |
| LM-2130 | Content Rules: Fixed issues associated with client certificate headers being erroneously deleted. |
| LM-2129 | Logging: Fixed an issue that could cause the kernel log message “Error handling task x x” to appear repeatedly in the system log. |
| LM-2128 | OIDC/OAUTH: On Azure, it was observed that an initial OIDC/OAUTH login works correctly, but a second login fails with the error “The reply URL specified in the request does not match the reply URLs configured for the application”. This issue has been fixed. |