SL1 Ibiza 12.3.3 Release Notes

ScienceLogic strongly recommends that you review the installation and upgrade instructions, important upgrade notes, and known issues for this release before installing or upgrading to SL1 12.3.3.

The SL1 Ibiza 12.3.3 release includes package updates to improve security and system performance and addresses multiple issues from previous releases.

These release notes provide a comprehensive list of the features, enhancements, and addressed issues that are included in the SL1 Ibiza 12.3.3 release.

To view the updates that are included in previous SL1 Ibiza releases, see the following release notes:

• 12.3.0
• 12.3.1
• 12.3.2

Before You Proceed

As of version 12.2.0, SL1 no longer supports deployment on Oracle Linux 7 (OL7). Users who are upgrading from a version of SL1 that runs on OL7 must first upgrade to SL1 12.1.2 and then convert all appliances to OL8 before they can upgrade to 12.2.0 or later. For more information, see the Supported Upgrade Paths section.

If you are planning to consume SL1 Ibiza 12.3.3, be advised of the following:

• The 12.3.3 release is available only as a patch; there is no ISO version.

• You can upgrade to this release directly from the following releases:

  • SL1 12.3.0 through 12.3.2

  • SL1 12.2.1.1 through 12.2.6

  • SL1 12.1.2, if all of your SL1 appliances have been converted to OL8

    If you are on 12.1.2, you should upgrade directly to 12.3.3 without consuming the 12.2.x releases.

    If you are upgrading from a version prior to 12.2.3, then after upgrading SL1, you must also upgrade MariaDB 10.4.x to version 10.6.18. Failure to perform this MariaDB upgrade can cause major functionality issues in SL1.

• If you are on 12.1.0.2 or 12.1.1, you can upgrade to 12.1.2, convert to OL8, and then upgrade directly to 12.3.3 without consuming the 12.2.x releases.

• 12.2.x and 12.3.0 STIG-compliant users can upgrade to this release. Users who are on an 11.x MUD system cannot upgrade directly to this release; they must first follow the approved conversion process from 11.x MUD to 12.2.1.1 STIG and then upgrade to 12.3.3 STIG. For more information, see the section on STIG Support.

• AWS deployments that are using Aurora 3 can upgrade to this release.

  • If you are currently deployed using Aurora 2, you can upgrade to this release but you must perform a post-upgrade Aurora 2 to 3 conversion.

• SL1 12.3.3 is Department of Defense Information Network (DoDIN)-certified.

For more information, see the Important Upgrade Notes and Known Issues sections.

New Features and Enhancements in SL1 Ibiza 12.3.3

This section describes the new features and enhancements that are included in SL1 Ibiza 12.3.3.

Documentation

• The ScienceLogic API and GraphQL documentation is now available at the ScienceLogic Support site (login required) under the Documentation drop-down tab.

Platform and Security

• SL1 version 12.3.3 includes package updates to improve security and system performance.

Issues Addressed in SL1 Ibiza 12.3.3

This section describes the issues that were addressed in SL1 Ibiza 12.3.3.

API

• Added a new device_group_name filter for the device API endpoint and ensured that the existing device_group and organization filters work as intended. (Case: 00505039) (Jira ID: EM-72774)

Authentication

• Resolved an issue that sometimes prevented users from logging in to the classic SL1 user interface without first logging in to the default user interface (AP2). (Jira ID: EM-72725)

Backups and Data Retention

• Resolved an issue that caused the backup_retention cleanup process to sometimes fail with an unhandled exception when performing a disaster recovery (DR) backup. (Jira ID: EM-72403)

Device Management

• Addressed an issue to improve the load time for the Performance tab of the Device Reports panel when users view class-based quality of service (CBQoS) device performance metrics. (Case: 00488049) (Jira ID: EM-72670)

PhoneHome Collection

• Added a new, configurable keepalive timeout setting for PhoneHome collectors. This new setting, which can be set at the appliance command line using the command sudo phonehome config set keepalive_timeout <value>, enables you to adjust the timeout value for sending keepalive requests to the server, which can be helpful for PhoneHome collectors with high network latency. You can configure the keepalive_timeout setting to a value between 10 seconds (10s) and 10 minutes (10m). (Case: 00449593) (Jira ID: EM-65809)

Platform and Security

• Removed incomplete software inventory records from processing when the "Enterprise Database: Software Title" inventory updater process runs. When the process is in DEBUG mode, users will receive the log message for the incomplete software inventory result(s) in the /var/log/sl1/software_inventory_update.log file to denote which Dynamic Application and device has collected an incomplete inventory record that will not be processed. (Case: 00465611) (Jira ID: EM-72218)

• Addressed an issue in post-processing with Dynamic Application index mapping. In this situation, if an existing index that had a non-accented character was replaced by an accented version of the same character, or vice versa, that replacement would cause an infinite error loop. (Case: 00477206) (Jira ID: EM-72432)

• Addressed an issue that caused HF rows behind unhandled exceptions due to infrequent deadlocks. (Case: 00462819) (Jira ID: EM-66648)

Recently Deprecated Features

PowerPacks

If you are upgrading from a previous version of SL1, the upgrade process will not remove any existing PowerPacks from your system. The PowerPacks listed below are still available for download from the PowerPacks Support page.

The 12.3.1 release removed the following PowerPack from the SL1 ISO:

• SL1: System Upgrade Assessment

The 12.3.0 release deprecated the following PowerPacks and removed them from the SL1 ISO:

• Blackberry Custom Reports
• Cisco: Wireless
• EM7 Base Themes
• OpenStack
• ScienceLogic Integration Service/PowerFlow Monitoring
• ScienceLogic Rules Engine Events
• VMware: vSphere Base Pack, versions 306 and 307

Upgrading SL1

You can consume SL1 12.3.3 only if you are upgrading from an earlier SL1 version that supports upgrades to this release. There is no ISO version for version 12.3.3.

For a detailed overview of SL1, see the Introduction to SL1 manual.

For detailed instructions on upgrading SL1, see the section on Updating SL1 in the System Administration manual and the upgrade notes that are included in this document.

SL1 Extended Architecture

For existing on-premises deployments of SL1 Extended Architecture, see the section on Upgrading SL1 Extended Architecture in the System Administration manual for upgrade instructions. For help with technical issues, contact ScienceLogic Customer Support.

 New installations of SL1 Extended Architecture are available only on SaaS deployments.

Important Upgrade Notes for SL1 Ibiza 12.3.3

This section includes important notes for upgrading existing SL1 systems to the Ibiza 12.3.3 release.

Unless otherwise stated, the information in this section applies to all users who are upgrading from previous SL1 versions.

ScienceLogic strongly recommends that you review these notes in their entirety before upgrading to version 12.3.3.

Supported Upgrade Paths

You can upgrade directly to 12.3.3 from the following SL1 versions:

• SL1 12.3.0 through 12.3.1

• SL1 12.2.1.1 through 12.2.6

• SL1 12.1.2, if all of your SL1 appliances have been converted to OL8

  If you are on 12.1.2, you should upgrade directly to 12.3.3 without consuming the 12.2.x releases.

If you are on 12.1.0.2 or 12.1.1, you can upgrade to 12.1.2, convert to OL8 if you have not already done so, and then upgrade directly to 12.3.3 without consuming the 12.2.x releases.

For versions 12.2.0 and later, the SL1 platform can be deployed only on Oracle Linux 8 (OL8) operating systems. For more information, see the OL8 Conversion Resource Center on the ScienceLogic Support portal.

STIG Support

12.2.x and 12.3.0 STIG-compliant users can upgrade to this release.

Users who are currently on an 11.x MUD system cannot upgrade directly to this release. 11.x MUD customers should follow the 11.3 MUD conversion to 12.2.1.1 STIG re-ISO migration path; this process is documented in the ScienceLogic OL8 MUD Conversion Guide. (Ask your ScienceLogic contact for this manual.) Once you are on 12.2.1.1 STIG, you can upgrade to later STIG releases, including this release.

When deploying a STIG-compliant configuration, port 7700, the Web Configuration Utility, and the Database Tool page are all disabled. In addition, concurrent PowerShell, concurrent SNMP, and concurrent network interface collection are not supported for these deployments.

Aurora 3 Support

AWS deployments that are using Aurora 3 can upgrade to SL1 12.3.3. If you are currently deployed using Aurora 2, you can upgrade to SL1 12.3.3 but must perform a post-upgrade Aurora 2 to 3 conversion. If you are on a SaaS-hosted AWS deployment, the ScienceLogic SRE team will complete this conversion. If you are on a customer-hosted AWS deployment, you must complete this conversion, with additional steps in the section on Updating SL1 in the System Administration manual. Contact ScienceLogic Professional Services if you need assistance.

Upgrading MariaDB and Rebooting SL1

Some SL1 versions include important security updates. To apply these updates, you must upgrade MariaDB and then reboot all SL1 appliances.

If you are upgrading from a version prior to 12.2.3, then after upgrading SL1, you must also upgrade MariaDB 10.4.x to version 10.6.18. Failure to perform this MariaDB upgrade can cause major functionality issues in SL1.

The following table specifies the required MariaDB version for each SL1 version and which SL1 updates require you to reboot all SL1 appliances:

SL1 Release	Required MariaDB Version	Requires Appliance Reboot?
12.3.3 (Upgrade only)	10.6.18	Yes
12.3.2 (Upgrade only)	10.6.18	Yes
12.3.1	10.6.18	Yes
12.3.0	10.6.18	Yes
12.2.6 (Upgrade only)	10.6.18	Yes
12.2.5 (Upgrade only)	10.6.18	Yes
12.2.4.1 (Upgrade only)	10.6.18	Yes
12.2.3 (Upgrade only)	10.6.18	Yes
12.2.1.2 (Upgrade only)	10.4.31	Yes
12.2.1.1 (ISO only)	10.4.31	N/A
12.2.0	10.4.31	Yes
12.1.2 (OL8)	10.4.31	Yes
12.1.2 (OL7)	10.4.29	Yes
12.1.1 (OL8)	10.4.28	Yes
12.1.1 (OL7)	10.4.29	Yes
12.1.0.2 ISO (OL8)	10.4.28	N/A
12.1.0.2 Upgrade (OL7)	10.4.29	Yes

Required Ports

Beginning with SL1 12.2.0, if you have a firewall between your Database Server, data engine, and Administration Portal appliances, you should open TCP port 8200 to facilitate communication between those appliances.

For a full list of ports that must be open on each SL1 appliance, see the section on Required Ports for SL1 in the Installation and Initial Configuration manual.

Python 2 Support Deprecation

Prior to SL1 11.3.0 Forum, all Dynamic Application snippets, Execution Environments, Run Book Actions, and ScienceLogic Libraries utilized Python 2. With the introduction of Python 3 support in 11.3.0 Forum, ScienceLogic announced its intent to deprecate support for Python 2 in a future release.

The core SL1 platform switched to Python 3 with the 12.3.0 Ibiza release. However, ScienceLogic will still include Python 2 in parallel with Python 3 until Q2 2025. ScienceLogic will proactively migrate the product and the PowerPacks it supports to Python 3. However, any custom content in customer-created PowerPacks must be recreated utilizing ScienceLogic-provided enablement tools or migrated to Python 3 before Q2 2025.

Python 3.9 Execution Environment Support Deprecation

Users who currently use Python 3.9 execution environments for Dynamic Applications and Run Book Automations are advised that the SL1 12.3.0 Ibiza release removed support for Python 3.9 and added support for Python 3.11. For more information, see the section Important Notes on Creating ScienceLogic Libraries in the ScienceLogic Libraries and Execution Environments manual.

Default Use of tmux When Using SSH

Starting with SL1 version 12.2.1.1, the tmux utility runs by default when you access an SL1 system using SSH.

The addition of this utility, which is a terminal multiplexer that enables a number of terminals to be created, accessed, and controlled from a single screen, strengthens session-control mechanisms and aligns with industry-wide security practices.

With this update, sessions are automatically locked after 15 minutes of idleness or if an unclean SSH disconnect or dropped SSH connection occurs. Upon login, SL1 checks for and attaches any detached tmux session if it finds them; otherwise, it starts a new session.

This update also introduces advanced features like scroll-back buffering with search, built-in clipboarding, multiple sessions and panes, detaching or attaching sessions, and session supervision or sharing.

If you have turned off tmux in an earlier version of SL1 and upgrade to 12.3.3, be advised that you will need to turn tmux off again after upgrading.

For more information about tmux shortcuts and usage, see https://tmuxcheatsheet.com/.

System Update Notes

• SL1 updates overwrite changes to the configuration file /opt/em7/nextui/nextui.env. (For more details, see https://support.sciencelogic.com/s/article/1423.) ScienceLogic recommends that you back up this file before applying an update and then reapply your changes to this file.
• ScienceLogic recommends that you run backups of your SL1 system before performing a system update.
• The SL1 user interface will be unavailable intermittently during system update.
• During the normal system update process, multiple processes are stopped and restarted. This might result in missed polls, gaps in data, and/or unexpected errors. ScienceLogic recommends that you always install SL1 releases during a maintenance window.
• The SL1 system update process starts a background process that can perform any required post-upgrade tasks. The post-patch update process is automatically stopped after 24 hours. However, depending on the size of your database as well as the version from which you are upgrading, the post-upgrade tasks can take several days to perform. If the post-patch update process is stopped after 24 hours, the process will automatically re-start and continue processing from the point at which it was stopped. If you see an event that indicates the post-patch update process was stopped, you do not need to contact ScienceLogic support for assistance until you see the same event for three consecutive days.
• After upgrading, to ensure proper data collection, you should go to the Appliance Manager page (System > Settings > Appliances), locate one of the Data Collector or Message Collector appliances, and click the lightning bolt icon to force configuration push for that appliance.

Upgrading from Oracle Linux 7 (OL7) Versions of SL1

If you are upgrading from a version of SL1 prior to 12.2.0 and first need to upgrade to 12.1.2 and/or convert all of your SL1 appliances to Oracle Linux 8 (OL8), ScienceLogic strongly recommends that you review the Important Upgrade Notes section of the SL1 Golden Gate 12.1.2 Release Notes prior to upgrading.

Known Issues for SL1 Ibiza 12.3.3

ScienceLogic strongly recommends that you review all Known Issues for SL1. For more information, see https://support.sciencelogic.com/s/known-issues#sort=relevancy.

The following known issues exist for SL1 Ibiza 12.3.3:

Security

• Prior to the release of SL1 12.3.3, five new common vulnerabilities and exposures (CVEs) were released for Ingress-nginx, the highest being CVE-2025-1794, rated a 9.8 CVSS. This allows anything on a Kubernetes pod network to exploit configuration injection vulnerabilities via the Validating Admission Controller. When combined with other vulnerabilities, CVE-2025-1974 means that anything on the pod network has a good chance of taking over your Kubernetes cluster, with no credentials or administrative access required. In many deployments, the pod network is accessible to all workloads within the deployed VPC. This vulnerability has been fixed in 12.3.3 for AWS SL1 deployments but still persists for on-premises deployments. A fix for on-premises deployments is planned for the 12.3.4 release. (Jira ID: DO-6433)

Deployment and Configuration

• You might receive an error message when attempting to update the Web Config Utility login passwords for your SL1 appliances. (Cases: 00504492, 00505294) (Jira IDs: EM-72698, EM-72959)

System Upgrade

• When upgrading a large number of SL1 appliances, you might encounter an issue where the deployment summary shows that deployment timed out for many of the appliances but, upon further inspection, you discover that the appliances actually deployed correctly. This is due to a lag in the deployment status reaching the Database Server after the default timeout value of 3600 seconds (1 hour). If you check back later, the issue should fix itself. If you would rather work around this issue, you can increase the timeout value. For instructions, see the section on Adjusting the Timeout for Slow Connections in the "Updating SL1" chapter of the System Administration manual. (Jira IDs: EM-59433, EM-62316)

• When upgrading SL1 on AWS stacks, you might receive an error message that the Data Engines failed to patch correctly. If this occurs, re-run the pre-upgrade tests and then run the patch again; this should result in the Data Engines updating correctly and the correct version then being reflected on the Appliance Manager page (System > Settings > Appliances).

• The post_update script might show errors referencing scripts in incorrect directories. A fix for this issue is included in an upcoming release. For more information, see https://support.sciencelogic.com/s/article/16189. (Case: 00481367) (Jira ID: 71361)

Authentication

• A known issue with session cache management might cause SL1 to log you out unexpectedly, or prevent you from logging in again after a recent session. If you experience either issue, you can work around it by clearing the cache of your web browser before you log into the SL1 user interface. For more information, see https://support.sciencelogic.com/s/article/13701. (Jira ID: SLUI-21011)

• The use of a percentage character (%) in a password will prevent firstboot from completing. (Jira ID: EM-72924)

• SNMP v3 default authentication sometimes fails on new Message Collectors. A fix for this issue is included in an upcoming release. For more information, see https://support.sciencelogic.com/s/article/16042. (Case: 00482414) (Jira ID: EM-71374)

• The Single Instance Login setting, which can be set on the Behavior Settings page (System > Settings > Behavior), is not working as designed for local non-administrator user accounts that utilize CAC or ADFS authentication. (Jira IDs: SLS-1559, SLS-1674)

• If you attempt to reset your SL1 password from the default user interface (AP2), the email link that is provided will direct you to the incorrect page. A fix for this issue is included in an upcoming release. (Jira IDs: SLS-1544, SLS-1669)

Business Services

• The Anomalies tab on the Service Investigator page for device services might incorrectly display devices that have anomaly detection disabled, rather than showing only those devices with anomaly detection enabled. (Jira ID: EM-62884)
• Organizations must have at least one or more accounts assigned to them to ensure the relevant services are saved. (Jira ID: SLUI-17810)
• For services that have their RCA Options field enabled, and has had a child service removed, SL1 will not compute the health, availability, and risk values until the Service Topology Engine returns an updated topology, which occurs every 5 minutes by default. (Jira ID: SLUI-18853)

Before deleting child services in a 3-tier hierarchy, check if the parent service has the RCA Options field Enabled, then set this field to Disabled if it is not already.

Credential Management and Discovery

• For an unguided device discovery, the Search box that displays for creating a new credential does not work. (Jira ID: SLUI-20777)

• When using the SNMP Public V2 credential to discover devices, you might see an unhandled exception in the system log near the end of the discovery session, despite the devices being discovered successfully. (Jira ID: EM-59380)

• When selecting two or more SNMP credentials to discover a device, if the first credential with the lower ID number contains incorrect information and the second credential with a higher ID number contains the correct information, the discovery logs will not be able to get an SNMP response. (Cases: 00289639, 00292649, 00422558) (Jira ID: EM-39681)

• For systems with EKMS enabled, existing SNMP credentials are not rotating as intended. (Jira ID: EM-72425)

Data Collection and Retention

• The "Data Collection: Interface Bandwidth" process might experience an unhandled exception when upgrading from an SL1 version using Python 2.7 for interface collection to one using Python 3.6. (Jira ID: EM-72827)

• When an XSLT node is empty, an "XML/XSLT exception 'NoneType' object has no attribute 'strip'" error is logged to the device log. (Jira ID: EM-73096)

Device Management

• If you attempt to export the list of devices from the Devices page by clicking the gear icon and selecting Export (.csv), only those devices that appear on the page are exported to the report rather than all devices in the system. To work around this issue, you can export the full list of devices from the Classic Devices page (Devices > Classic Devices > Report). (Jira ID: EM-73157)

• Clicking the printer icon to print a report on either the Device Processes page (Devices > Processes) or Windows Services page (Devices > Services) results in a blank page appearing rather than a modal of report options. To work around this issue, go to the Classic Devices page (Devices > Classic Devices), click the bar graph icon for the device you want to print a processes or services report for, select either the Process tab or Services tab, and then click the printer icon. (Case: 00503774) (Jira ID: EM-73062)

Events and Alerts

• An issue is preventing the event engine from properly decoding some inbound email messages due to special characters. This can result in the event engine failing. For more information about this issue, including a workaround, see https://support.sciencelogic.com/s/article/16756. (Jira IDs: EM-72242, EM-72656)

High Availability and Disaster Recovery

• When EKMS is enabled in a high-availability (HA) configuration, the EKMS vault service might be unable to start after a failover due to bad configuration files. This issue is seen when a user has a working HA setup configuration, then later re-ISOs or rebuilds one of the Database Servers. One source of the rebuilt Database Server is swapping active node with DR node. For more information about this issue, see https://support.sciencelogic.com/s/article/15486. (Jira IDs: SLS-1341, SLS-1466)

Logging

• A known issue might cause several log configuration files to conflict, which could cause you to see errors for the sl_vault and slsctl logs or potentially block log rotation in some cases, depending on the order in which the files are executed. To work around this issue, delete the config files ~sl_vault and ~slsctl. (Jira IDs: SLS-1105, EM-62134)

Reporting

• A known issue is causing PDF and XSLX Ticketing report types to fail to generate properly due to an OL8 incompatibility issue. For more information, see: https://support.sciencelogic.com/s/article/11649. (Jira IDs: EM-51131)

• A new, non-administrator user that has all of the Reporting access keys aligned to their user account cannot create a new scheduler or see the archived reports. (Jira ID: EM-72259)

Support PowerPack

• The "Support: Configuration File Validation" and "Support: Appliance Validation" Dynamic Applications in the "ScienceLogic Support Pack" PowerPack contain SQL queries with the keyword "function", which is a reserved keyword in MySQL 8.0. Because of this, you might see unhandled exceptions relating to those Dynamic Applications. A fix for this issue is included in an upcoming release. (Jira ID: EM-72266)

User Interface

• In the SL1 user interface, the End User License Agreement (EULA) page is displayed on all pages that were iframed from the classic user interface, even after the user agrees to the EULA. This issue is occurring for ADFS, CAC, and AD authentication methods. (Jira ID: EM-67851)

• After upgrading to 12.2.0 or later, you might be unable to delete devices from the Devices page. If this occurs, you can work around this issue by deleting the device from the Device Manager page in either the default ("AP2") SL1 user interface (Devices > Device Manager) or the classic user interface (Registry > Devices > Device Manager), or you can delete the device from the Database Server. (Case: 00412497) (Jira ID: EM-62874)

• After upgrading to 12.3.2 or later, custom themes and logos might not display on classic user interface pages. To work around this issue, clear the cache of your web browser. (Case: 00503523) (Jira ID: EM-72921)

• The Expand and Contract buttons are not working as intended on the Dynamic Application Collections page (Devices > Device Manager > wrench icon > Collections). You can still expand and contract individual items on the page. (Jira ID: EM-64420)

• In STIG deployments, the DashSL1 column does not display on the PowerPack Manager page (System > Manage > PowerPacks). A fix for this issue is included in an upcoming release. (Case: 00465085) (Jira ID: EM-66815)

• In ISO deployments, on the guided discovery pages, bullet points might appear as â¢. A fix for this issue is included in an upcoming release. (Jira ID: SLUI-20614)

• The Access Keys page (System > Manage > Access Keys) might not count administrator users in the value displayed in the # Aligned Users column. To work around this issue, go to the Account Permissions page (Registry > Accounts > User Accounts > wrench icon) for the administrator users and re-save their permissions. (Jira ID: SLS-1576)

• When you bulk-select multiple event policies to align with a run book automation policy, additional event policies that you did not select might become aligned with that automation policy as well. (Jira ID: EM-70690)

• Dashboard auto-refreshing is not keeping user sessions active, even when the Page Auto-Refresh Keeps User Session Active field is set to Enabled on the Behavior Settings page (System > Settings> Behavior). For more information, see https://support.sciencelogic.com/s/article/16930. (Case: 00503563) (Jira ID: SLUI-21787)

• On the Organizations page (Registry > Accounts > Organizations), the filter-while-you-type feature is not working as intended in the Skylar AI Status column. A fix for this issue is included in an upcoming release. (Jira ID: EM-71414)

• On the Admin Processes page (System > Settings > Admin Processes), the Runtime Offset column does not display any values. You can view the runtime offset value by editing the process. (Case: 00506663) (Jira ID: EM-73218)

Windows Monitoring

• If your SL1 system is running Windows 2008 or Windows 2012, and you are using PowerShell collections that have the Encrypted field set to Yes in the credentials, those collections will stop working. For more information, see Users with Windows 2008 R2 Servers or Windows 2012 Servers in the SL1 Product Documentation. (Jira ID: EM-61204)

Known Issues Resolved in Available Releases

Several known issues that are present in 12.3.3 are resolved in the AP2 8.17.23.45 (Ice Pop) release. You can optionally download and install that release after upgrading to 12.3.3 to obtain the fixes to these known issues:

• Due to an issue with Aurora 3, you can no longer enable TLS verification through the user interface or the API. To address this issue, update the master.system_settings_general database table by setting value=1 where param='require_tls_verification';. (Jira ID: SLS-1500)

• On the Events tab of the Device Investigator, Skylar AI-cleared events cannot be found if you filter for an Event Source of Skylar AI in the Cleared Events tab. (Jira ID: SLUI-20889)

• The Classic Maps page fails to load properly whenever you attempt to log in to the default user interface (AP2) without accepting the End-User License Agreement (EULA). To work around this issue, create a "Grant All" user account, then sign in to AP2 with the newly created account. (Jira ID: SLUI-20801)

Several additional known issues that are present in 12.3.3 are resolved in the AP2 version 8.18.43.81 (Jelly Bean) release. You can optionally download and install that release after upgrading to 12.3.3 to obtain the fixes to these known issues:

• If you deploy SL1 Global Manager with SAML single sign-on authentication, you might experience an issue where the Global Manager stack cannot access data from its child stacks if Enterprise Key Management Service (EKMS) encryption was disabled on the Global Manager system, resulting in the following error message: "Stack <#> <IP address> results excluded. Consider disabling it. Reason: Response code 401 (Unauthorized)." To work around this issue, EKMS should be enabled for the Global Manager stack. It can be enabled or disabled for the child stacks. (Jira ID: SLUI-21476)

• If you attempt to duplicate a business, IT, or device service but that service includes organizations you do not have access to, you will receive an error message. (Jira ID: SLUI-20008)