2.2.24 Release Notes (05/15/26)
Document Details | |
|---|---|
Document Issue Level: | 1.0 |
Document Issue Date: | May 15, 2026 |
Product Details | |
|---|---|
Product Description: | Symmetry IDM - CONNECT and GUEST |
Release Version: | 2.2.24 |
Introduction
This bulletin provides an overview of product improvements and an introduction to new features included in Symmetry CONNECT/GUEST/IDM for hosted and on-premise deployments.
Note
For Hosted customers, the planned deployment date will be communicated via the online status page. Please visit: Symmetry Identity Management (IDM) Status
Private Cloud Customers, please access your dedicated status page.
Important Deployment Information
For general deployment guidance, please refer to the Connect and Guest Deployment Guide (Issue 1.54.0)
On-Premise Deployments:
Warning
Customer Notice – Upcoming Infrastructure Change for IDM (Effective from Release 2.3.0)
As part of our ongoing commitment to improving performance, scalability, and long‑term supportability, AMAG will be upgrading Identity Management (IDM) platform infrastructure starting with Release 2.3.0. This upgrade introduces a modernized architecture built on Kubernetes and PostgreSQL.
What This Means for On‑Premise Customers
Beginning with IDM 2.3.0, the platform will run exclusively on the new Kubernetes + PostgreSQL environment.
Customers currently running IDM On‑Premise using Docker Swarm with SQL Server will continue to receive support up to version 2.2.20. This includes:
Application support
Issue resolution
Maintenance updates
However, any new features, enhancements, and fixes introduced from 2.3.0 onward will not be available for Docker Swarm + SQL Server systems.
Action Required
To continue receiving the latest improvements and to stay on a fully supported upgrade path, customers will need to migrate their IDM environment to the new Kubernetes‑based architecture.
We encourage all On‑Premise customers to:
Begin planning for this transition
Review internal infrastructure readiness
Contact AMAG for guidance and support
How AMAG Can Help
Our team is ready to assist with:
Migration planning and best‑practice recommendations
Architecture and deployment guidance
Upgrade support to ensure a smooth transition
Please reach out to your AMAG representative to discuss your migration options and timelines.
Warning
This release requires additional Release steps:
USE CONNECT GO CREATE NONCLUSTERED INDEX IX_identity_access_group_audit_group_campaign_status ON [projection].[identity_access_group_audit] (group_id, audit_campaign_agg_root_Id, [status]) INCLUDE (department)
Warning
This release requires additional rollback steps:
USE [vms]
GO
-- 1. Recreate the TableCREATE TABLE [projection].[compliance_fips201_report](
[id] [bigint] IDENTITY(1,1) NOT NULL PRIMARY KEY,
[group_id] [uniqueidentifier] NOT NULL,
[visit_id] [uniqueidentifier] NOT NULL,
[hostid] [uniqueidentifier] NOT NULL,
[visitor_id] [uniqueidentifier] NOT NULL,
[site_code] nvarchar NOT NULL,
[change_date] [datetime] NOT NULL,
[change] nvarchar NOT NULL,
[change_details] nvarchar NULL,
[visitor_first_name] nvarchar NOT NULL,
[visitor_last_name] nvarchar NOT NULL,
[active_date] [datetime] NOT NULL,
[inactive_date] [datetime] NOT NULL,
[authorized_by] nvarchar NULL,
[authorizor_company] nvarchar NOT NULL,
[access_code_name] nvarchar NOT NULL,
[sequence] nvarchar NOT NULL,
[aggregate_root_id] [uniqueidentifier] NOT NULL,
[visitor_company] nvarchar NULL,
[visit_badge_template] nvarchar NULL,
[visitor_credential_number] varchar NULL,
)
GO
-- 2. Recreate IndexesCREATE NONCLUSTERED INDEX [IX_access_code_name] ON [projection].
[compliance_fips201_report]
(
[access_code_name] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF,
ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
GO
CREATE NONCLUSTERED INDEX
[IX_compliance_fips201_update_inactive_covering] ON [projection].
[compliance_fips201_report]
(
[group_id] ASC,
[visit_id] ASC,
[access_code_name] ASC,
[inactive_date] DESC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF,
ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
GOSymmetry Integration Client:
The AMAG.Symmetry.Client has been updated to version 7.31.0.1941. Certain new features or corrections will not be fully functional until the new client has been installed; any such items will be highlighted in the proceeding notes.
The Checksum for this Symmetry client is:
f5100ec77112b43ee89b34e5095ba311b32feda2230b06a88f29e74602d7a8f0.
Warning
Customers who utilize firewalls for their Amag.Symmetry.Client will be required to update rules to allow TCP port 5671, 5672 & 443.
New / Changed Functionality
Department Filter for Audit Screen - An additional dropdown filter has been added to the audit screen; this allows for the following;
Support of single and multi-select filtering, including other filters.
Filter applies to all audit events where the actor or target identity is associated with a department.
When a department is selected, only events involving identities from that department are shown.
Expanded Character limits in GUEST. We have extended character limits for First an Last name to 255.
Issues Addressed
ZD232425 - Resolved an issue where certain Access Groups would not sync to the physical access control system, remaining in a perpetual "Pending" state while other groups on the same integration synced correctly
Note
Requires Client version 7.31.0.1941
ZD235250 - Resolved an issue where the system would log users out when clearing a proxied user session in environments using Single Sign-On (SSO)
ZD234704 - Resolved an issue where the Badge Template configuration screen would fail to load with an "Unknown Error" in environments with a large number of companies defined
ZD234018 - Resolved an issue where navigating to the last page of a large identity list would return an "Unknown Error" and fail to load
ZD234266 - Resolved an issue where credential status changes made in Symmetry (such as expiration, lost, or force inactive) were not consistently reflected in the corresponding mobile wallet credential
ZD233802 - Resolved an issue where the IDM Identity Audit Report showed 'Unknown' as the source for photo upload events originating from credential/badge requests in CONNECT
ZD233421 - Resolved an issue where visitor name length limits were inconsistent between the GUEST UI and the CONNECT Public API
ZD231198 - Resolved an issue directly editing date fields in the CONNECT 2.0 view would cause the field to reset to a blank value instead of accepting the change
Resolved an issue where certain card transaction events recorded in Symmetry were not appearing in the CONNECT Card Activity Report, causing gaps in audit data
Resolved an issue in GUEST where card number data collected during visit creation or visitor check-in was not always displayed in the completed visit record