2.8.2 Release Notes

Document Details
Document Issue Level:	1.0
Document Issue Date:	Sep 1, 2026

Product Details
Product Description:	Symmetry IDM - CONNECT and GUEST
Release Version:	2.8.2

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: https://symmetry-identity-management-saas.statuspage.io/

Private Cloud Customers, please access your dedicated status page.

Legal Information

Please refer to the AMAG Technology Software License Agreement, available at: Legal References

On-Premise Deployments:

Customers who adopted Kubernetes with external Elasticsearch servers are advised to upgrade Elasticsearch to v8.19.20.
Customers who adopted Kubernetes are required to upgrade to 1.35.7 or later.

Customers are required to execute the following in PostgreSQL

CREATE INDEX CONCURRENTLY IF NOT EXISTS ix_visit_multiday_checkins_group_arrival_checkin_includes
    ON vms_projection.visit_multiday_checkins (group_id, arrival_date_utc, check_in_date_utc)
    INCLUDE (departure_date_utc, status, building_id, visitor_id, visitor_company,
             access_control_rule_id, visitor_type, host_company_id, host_delegate_company_id,
             receptionist_id, receptionist_company_id, id);
CREATE INDEX CONCURRENTLY IF NOT EXISTS ix_identity_group_id_lower_last_first_dept_title
    ON connect_projection.identity (group_id, LOWER(last_name), LOWER(first_name), LOWER(department), LOWER(title));
CREATE INDEX CONCURRENTLY IF NOT EXISTS ix_aar_group_id_lower_affected_identity_last_name
    ON connect_projection.access_assignment_report (group_id, LOWER(affected_identity_last_name));

Customers are required to perform the following;

Create a new YAML File called <idm-nats-creds-secret.yaml>

Input the values stated below, into the yaml file, ensuring to input the Operator.nk and Sys.creds

apiVersion: v1
kind: Secret
metadata:
  name: idm-nats-creds
  namespace: <PLACEHOLDER_NAMESPACE>
type: Opaque
stringData:
  operator.nk: |
    <PLACEHOLDER_OPERATOR_NK>
  sys.creds: |
    <PLACEHOLDER_SYS_CREDS>

Apply using:

kubectl apply -f idm-nats-creds-secret.yaml

Users requiring to rollback to IDM version 2.6.4, must deselect 'backend' within the Kubernetes installer before downgrading.

Symmetry Integration Client:

The AMAG.Symmetry.Client has been updated to version 9.0.0.2083 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:

ca8bc164e548d5dc45cee6c7811e9da15d3a8fd722a6f1a0395e02f4ea9ee63c.

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

This section contains an itemized list of all new feature deliverables. Supporting images should be used where necessary. Descriptions should be customer-friendly and simple. Must never contain customer or company names.

SCIM Support:

We have now introduced the capability to support SCIM 2.0. The SCIM configuration can be found under Configuration > System Settings > SCIM
Bearer Token Control - Customers will be able to fully manage the creation of Bearer tokens, with the ability to create, rotate and remove.
SCIM Attribute Mapping - We have implemented a full attribute mapping suite with the following functions;
- Provisioning behavior
  - Ability to control user deactivation behavior in certain identity States
  - Identity Manager mapping to company
  - Control over IDP managed field editing.
- Attribute Mapping
  - Allows for the mapping of User Defined Fields to IDP Attribute path. Additionally we have applied a quick link to User Defined Fields.
- Built-in Mappings
  - Pre-defined and fixed mappings supplied by the SCIM Endpoint. These mappings are defined by the SCIM endpoint and are only shown for reference.
- SCIM Provisioning status
  - Users are provided with real-time provisioning statuses along with error logging and a manual refresh function
Allow for multiple Access Rules in GUEST:
- We have now introduced the ability for Visits to be granted access across multiple integrations at the same time. Previously, a visit could only sync to one integration.
- Multi-System Check-In - At check-in, if applicable, matching rules on both/all integrations, visitors will automatically receive credentials in every relevant Symmetry system in one step, instead of being limited to just one.
- Independent Access Per System - Each Symmetry system continues to manage its own access codes and removal timing based on its own configured rule, so existing single-system behavior is unaffected.
- Single Shared Credential - Visitors still receive one physical badge or barcode; when multiple systems are involved, the system automatically determines which configured rule defines the shared credential details, while each system still grants its own access independently.
- No Setup Changes Required - This is enabled through a new setting in the Access Control Rule configuration; no changes to existing rule setup are needed, and single-system customers see no change in behavior.

Credential Request Notification Email Configuration

Administrators can now configure the frequency of Credential Request notifications. This can be configured within Configuration > Connect Settings.
- The default will be set to Daily Digest and will only apply to future emails post-deployment.
Frequency options:
- Immediately (default) — notification sent per request, as today
- Daily Digest — all requests from the past 24 hours batched into a single email, sent once per day
- Never — email notifications disabled entirely

Credential and Facility Code Whitelist

There is now an added Facility Code Whitelist to enable customers to automatically set and apply facility codes to Credential Assignments through all modules.
This feature also shows a real-time usage count of applied Credentials subject to each facility code in the whitelist.
- Selecting the usage counts shows a breakdown of modules utilizing the Facility Code, whether it be through Access Control Rules or Credential Assignment.
- Users can individually/multi select entries to either edit/remove the facility code from Access Control Rules or remove the credential entirely from users in the Credential list. Validation will take place if Access Control Rule configurations prevent the last card from being removed.

Key Issues Addressed

This section lists bug fixes included in the release.

Reference	Summary	New Symmetry Client Required
ZD234725	An issue has been addressed with Access Rules containing multiple Access groups. Users only matching to one Access Group in the Rule were not having their Access Removed.	N/A
ZD236688	An issue has been addressed with Credentials not being removed from Symmetry when removed from IDM.	✓
ZD237431	An issue has been addressed with Wallet Credential. First issues resolved was due to incorrect reporting on Credential activation. Second issue resolved was on Identity Employee/Non-Employee states on the Credential in Wallet.	N/A
ZD237692	An issue has been addressed with inconsistent results when applying Access Group filters in Access Requests.	N/A
ZD238170	An issue has been addressed with the naming conventions of Wallet Credentials as ‘corporate badge’.	N/A
ZD238019	An issue has been addressed with Credential Status Report data inconsistencies with UI reporting.	N/A
ZD238169	An issue has been addressed with an incorrect subject line for Credential Approval emails.	N/A
ZD238356	An issue has been addressed with incorrectly distributed Access Expiry emails when Access is set to a future date.	N/A
ZD238368	An issue has been addressed where adding the Photo Tech role to ACRMs reduces visibility of Identities.	N/A
ZD235479	An issue has been addressed with Hiding Names on Access groups was not being applied.	N/A
ZD238114	We have addressed an issue with the Card Activity Report not updating.	✓
	An issue has been addressed with the public API not allowing the reissue of a deleted Credential.	N/A
	An issue has been addressed with On-Premise Symmetry Client errors on background tasks	✓
	An issue has been addressed with Group badge pre-printing in GUEST if the print utility was not running.	N/A
	An issue has been addressed with the Kiosk Native Application losing toke authentication if left inactive for an extended period of time.	N/A
	An issue has been addressed Access granted in IDM was not propagating to Symmetry.	✓

In this section:

GUEST/IDM/CONNECT