Fixed issues in Splunk UBA

This version of Splunk UBA fixes the following issues. If no issues are listed, none have been reported.

Date resolved Issue number Description
2023-08-15 UBA-16818 UBA UI not accessible after performing RHEL8 post-upgrade clean up tasks
2023-08-15 UBA-17437, UBA-17455 Error after enabling Splunk SSL certificate validation - Connection refused , Splunk host validation error: %s
2023-08-15 UBA-17106 MalwareThreatDetectionModel Failure: Spark-default.conf not updated under /var/vcap/packages/spark/conf directory after upgrading from UBA 5.1.0.x to 5.2.0
2023-08-15 UBA-15912 Upgrade from 5.0.5.1 to 5.1.0 or 5.2.0 (RHEL) OutputConnector re-import cert needed
2023-08-14 UBA-15963 krb5-libs(x86-64) = 1.18.2-* is needed by krb5-devel-1.18.2-* on Oracle Enterprise Linux and RHEL
2023-08-14 UBA-16762 Benign JNDI ClassNotFoundException: Impala queries complain, since removing Log4j2 vulnerability
2023-08-03 UBA-16850 Getting error about zookeeper-server service is not responding in Health monitor UI intermittently (Ubuntu only)
2023-07-04 UBA-17335 Threat dashboard throwing error "Cannot read properties of undefined (reading 'length')" upon changing time to local time instead of UTC
2023-06-06 UBA-16819 UBA Spark Server failing to store failed model execution record in redis
2023-05-09 UBA-17117 TLS/SSL Weak Message Authentication Code Cipher Suites
2023-05-08 UBA-17151 UBA backup script fails if Redis network connection password changed from default
2023-05-08 UBA-17233 Model execution failure caused by ModelRegistry.json not being applied correctly for deployments with 7 nodes or more after upgrading to UBA 5.2.0
2023-04-24 UBA-17188 Restricted sudo access for caspida ubasudoers file missing permissions
2023-02-19 UBA-16909 "UBA_HADOOP_SIZE key is either missing or has no value" error encountered when uba-restore is run from a backup created with the --no-data option