Humio Server 1.6.10 Stable (2019-12-12)
|End of Support
|Req. Data Migration
Bug Fixes and LDAP improvements. There are some changes to the configuration that will be required. See the change log below.
The following items create a breaking change in the behavior, response or operation of this release.
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-searchmethod by specifying the
LDAP_USERNAME_ATTRIBUTEin 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-searchcode path in cases where users of Humio authenticate with a username (e.g.
user) rather than an email address (e.g. firstname.lastname@example.org). To elicit the same behavior as previous versions of Humio simply specify the
LDAP_SEARCH_DOMAIN_NAMEwhich in the past would default to the value of
LDAP_DOMAIN_NAMEbut no longer does.
LDAP_SEARCH_DOMAIN_NAMEexplicitly when using
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.
Query sessions were not properly cleaned up after becoming unused. This lead to a leak causing high amount of chatter between nodes.