Fixed issues for Splunk SOAR (On-premises)
Release 6.3.1
Splunk SOAR version 6.3.1 includes fixes for the following issues.
| Date resolved | Issue number | Description |
|---|---|---|
| 2024-11-25 | PSAAS-20015 | 6.2.2 upgrade to 6.3.0 fails due to table "indicator_artifact_record_archive" already existing |
| 2024-11-13 | PSAAS-20494, PSAAS-20496 | Multi-tenancy: Fail to run playbook configured with wildcard tenant (*) |
| 2024-11-06 | PSAAS-7499 | VPE: Playbook name field should be longer |
| 2024-10-17 | PSAAS-19917, PSAAS-20071 | Reports page drop down results in 500 Server Error |
| 2024-10-14 | PSAAS-19708 | Playbooks might remain in pending status |
| 2024-10-08 | PSAAS-18082 | VPE: Blocks invisible when using Safari Version 17.5 |
| 2024-09-30 | PSAAS-19362 | Placeholder values for custom indexes in the Forwarder Settings modal don't match the actual default indexes |
| 2024-09-30 | PSAAS-19171 | Pip packages upgraded during install, old versions still exist missing METADATA files |
| 2024-09-30 | PSAAS-17189 | Playbook deletion is not logged in the audit trail |
| 2024-09-17 | PSAAS-19321 | Non Root Installs: Do not allow phantom services to be run with root on non-root installs |
| 2024-09-10 | PSAAS-18888 | warm-standby: "--standby-mode --convert-to-primary" results in "File exists" when keystore is a mounted filesystem, and leaves soar instance in an unusable state with the potential for data loss |