Resolved issues in Security Center 5.11.1.1 - Security Center 5.11.1.1

Security Center Release Notes 5.11.1.1
Product
Security Center
Content type
Release notes
Version
5.11
Release
5.11.1.1
Language
English
Last updated
2022-12-20

The following software issues are resolved in Security Center 5.11.1.1.

Solution/Unit Issue Description
All 3298148 Config Tool freezes, disconnects, or crashes when a non-administrator user opens a map that contains a large number of entities in the Map Designer task.
All 3296988 Logging out of Config Tool or Security Desk can take up to several minutes on systems with large amounts of cardholder pictures.
All 3270131 An unhandled exception occurs when creating an event-to-action if Security Center has a plugin installed that uses custom actions.
All 3256466 The Federation™ role is displayed as offline after a federated system disconnects from the Federation™ host.
All 3245533 An incorrect Security Center build number is displayed in Config Tool and Security Desk after a hotfix is installed.
All 3245001 Event-to-action alarms that are triggered from zone events and have an acknowledgment condition are automatically acknowledged.
All 3244712 The Reverse Tunnel role fails to connect to the cloud server when pinned certificates are not found.
All 3224735 Roles might fail to start after updating the Directory server certificate.
All 3215841 Users cannot log in to Security Center if the SAML2 protocol of the identity provider (IDP) does not specify a Single Logout (SLO) endpoint.
All 3207533 On systems with large amounts of custom fields, generating a report in the Cardholder activities task times out and yields no results if only custom fields are used as filters.
ALPR 3302599 The AutoVu™ third-party data exporter is unable to connect to cloud-hosted instances of RabbitMQ if a forward slash (/) is entered in the hostname field.
ALPR 3255520 The hostname field in the SFTP connection section does not allow for a hostname longer than 50 characters.
ALPR 3255830 When upgrading LPR Manager from any prior version to 5.11, the LPR database upgrade fails and the LPR Manager role gets stuck in a warning state if the database that is being upgraded is greater than 25 GB.