Fixed issues
4.2.4
-
Fixed an issue that caused input and output failures when the database password was rotated through HashiCorp or CyberArk identities.
-
Fixed an issue that prevented Trace-Id from being configured for scheduled inputs and outputs.
4.2.3
Version 4.2.3 of Splunk DB Connect fixes the following issues:
Fixed an issue on Windows where Java processes were not properly managed, resulting in "HTTP 401 — call not properly authenticated" errors. This was resolved by restoring native binary launchers to ensure correct process lifecycle management by Splunk. It affects versions 4.1.0 to 4.2.2.
4.2.2
Version 4.2.2 of Splunk DB Connect fixes the following issues:
Fixed a race condition that could cause database login failures due to errors during password decryption.
4.2.1
Version 4.2.1 of Splunk DB Connect fixes the following issues:
Fixed a configuration conflict with the DA-ESS-UEBA application related to the [script:connections] stanza in restmap.conf.
4.2.0
Version 4.2.0 of Splunk DB Connect fixes the following issues:
If no issues appear below, no issues have yet been fixed.