GUEST/IDM/CONNECT

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 the 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 only up to version 2.2.20. This includes:

However, new features, enhancements, and fixes introduced from 2.3.0 onward will not be available on Docker Swarm + SQL Server deployments.

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:

How AMAG Can Help

Our team is ready to assist with:

Please reach out to your AMAG representative to discuss your migration options and timelines.

Warning

This release requires additional rollback steps:

USE [vms]
GO
-- 1. Recreate the Table
CREATE 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 Indexes
CREATE 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]
GO