Release Notes
Anyware Connector (RHEL and Rocky Linux) 24.10
This version (24.10) of the Anyware Connector (RHEL/Rocky Linux) contains bug fixes and stability enhancements.
Issues with Configuration Files
Recent code changes caused issues with config files used by some customers. This issue was fixed and config files shall work as expected.
Incorrectly Populated 'host' Field
Logs were being shipped (and then subsequently indexed within SplunkCloud) with the 'host' metadata field populated using the HEC endpoint URL instead of the actual hostname of the AWC host as Splunk would typically expect. This is now fixed and the logs are correctly formatted.
Clean install of the Connector recommended
A clean install of the Connector instead of upgrade resolves the issue and is recommended in these cases.
Issues with Installation in LDAP Mode
Sometimes, during LDAP mode installation, the following error was displayed in the initial stages of broker authentication: User Authentication Failure.
The issue was caused by inadequate configuration. It has been resolved.
Unsupported Characters in AD Names
Sometimes, the underscore character ("_") in AD names caused issues. This was because previously, underscores were not supported in AD names. Underscores are now accepted in AD names.
Firewall Settings Prevented Download of Container Images
Firewall settings in some customer environments prevented Redis container images from downloading during the installation of Anyware Manager. The issue can be resolved by using the darksite installer.
Connection pool exhausted overtime
The issue was fixed in 24.03.3.
Missing Update in Logrotate Script
An update in the logrotate script was missing from the latest release. This caused the script to check the wrong folder for logs. The script has now been updated to the latest version, and it checks the correct folder for logs.
OAuth column was removed and replaced by AUTHENTICATION column that provides more information about the setup. More details can still be obtained elsewhere as described in documentation.
There are no known issues in this release.