Humio Server 1.6.10 Stable (2019-12-12)

VersionTypeRelease DateEnd of SupportUpgrades FromData MigrationConfig. Changes
1.6.10Stable2019-12-122020-12-121.5.19NoYes
JAR ChecksumValue
MD5c8cfd22a5be0456f5905247b6f2bab3b
SHA14c4b734217c5ac90bd9be5f6e2f34c4e182f8fa6
SHA2562a2529e2b2bdbd54162075adb55b514d80bbe60ec1854b8044fb7cbea985c006
SHA512883ee5a113ceeab99063d07d3b19b935e382dfdab598903fb896392d225d8dddc91716db56e29f4a92053d7b37e818806fcdad86126b9a5e2b68c17ad4f32c76

Bug Fixes and LDAP improvements. There are some changes to the configuration that will be required. See the change log below.

Bug Fixes

  • Summary

    • Bug Fix: Query sessions were not properly cleaned up after becoming unused. This lead to a leak causing high amount of chatter between nodes.

    • Add LDAP_USERNAME_ATTRIBUTE and LDAP_GROUPNAME_ATTRIBUTE configuration settings to enable more control over names carried from LDAP into Humio.

    • LDAP: It is now possible to specify an attribute within the LDAP record to use for the username rather than the default (an email address). This is only the case when using ldap-search method by specifying the LDAP_USERNAME_ATTRIBUTE in the environment. Group names when using LDAP have historically been the distinguished name (DN) for that group, it is now possible to specify and attribute in the group record for the name by setting LDAP_GROUPNAME_ATTRIBUTE. These changes necessitated a breaking change in the ldap-search code path in cases where users of Humio authenticate with a username (e.g. user) rather than an email address (e.g. user@example.com). To elicit the same behavior as previous versions of Humio simply specify the LDAP_SEARCH_DOMAIN_NAME which in the past would default to the value of LDAP_DOMAIN_NAME but no longer does.

    • Username/email is treated case-insensitive in Humio. This is more expected behavior of usernames as emails addresses are often used. In some rare occasions duplicate accounts might have been created with difference in casing and this change can trigger the otherwise dormant account to be chosen when logging in the next time. If this happens, use the administrations page to delete the unwanted user account and let the user log in again.

    • Require setting LDAP_SEARCH_DOMAIN_NAME explicitly when using ldap-search authentication method.