Published on 2018-11-22 00:00:00

Humio 1.1.34

Improved LDAP Support

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.34

Archive

2018-11-22

2019-06-21

1.1.0

No

Yes

JAR Checksum

Value

MD5

ab1eafa8442d6ed275c94527ed96ed19

SHA1

7a48b49cba75653d610cc700fab5237707fada44

SHA256

4aa7256991fbc5275ede446402ae9540281bcf39ba8a4503a0510d559ddcd45f

SHA512

2c4b1ff36ee3d4409f0ae142cfd749d1ada4228b4a6c533685ff476093117f3a472ecc8c5b3e7354ab4412406d488488cc6ffb5f4ca905c8bd5144a128925d1a

TGZ Checksum

Value

MD5

ab1eafa8442d6ed275c94527ed96ed19

SHA1

7a48b49cba75653d610cc700fab5237707fada44

SHA256

4aa7256991fbc5275ede446402ae9540281bcf39ba8a4503a0510d559ddcd45f

SHA512

2c4b1ff36ee3d4409f0ae142cfd749d1ada4228b4a6c533685ff476093117f3a472ecc8c5b3e7354ab4412406d488488cc6ffb5f4ca905c8bd5144a128925d1a

Summary

Improved LDAP support

Change Log

  • By default users must be added inside Humio before they can log in using external authentication methods like LDAP and SAML. This can be controlled using the configuration flag AUTO_CREATE_USER_ON_SUCCESSFUL_LOGIN=false. If users are auto created in Humio when they successfully login for the first time, the user will not have access to any repositories unless explicitly granted. A new user will only be able to access the users personal sandbox.

  • Bug Fix for match function. In some cases it did not match quoted strings.