NSX to vIDM Version Interoperability Testing
search cancel

NSX to vIDM Version Interoperability Testing

book

Article ID: 330594

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

This KB article provides additional information on NSX<> VIDM version interop testing and support.

Issue 1: Customers will need to patch VIDM's zero-day vulnerability as soon as possible otherwise will pose serious security risk to NSX/VMware solution.


https://www.vmware.com/security/advisories/VMSA-2020-0027.html




Issue 2
(1) Removal of embedded connector for AD systems using IWA
(2) Embedded connector usage in multi-site environment as mentioned in the VIDM 3.3.3 release notes .

VMware Identity Manager Connector 3.3.3 (Windows)

If you installed the VMware Identity Manager Connector for Windows 3.3.1 and 3.3.2 with vRealize Suite Lifecycle Manager, you cannot upgrade to 3.3.3. You must install the new 3.3.3 version of the connector.

If you installed the VMware Identity Manager Connector for Windows 3.3.1 or 3.3.2 using the .exe installer, you can upgrade your connector to 3.3.3.

Documentation

The VMware Identity Manager 3.3 documentation is in the VMware Workspace ONE Access Documentation center . The 3.3.3 upgrade guide can be found under VMware Identity Manager 3.3 in the Installation & Architecture section. 

Known Issues

  • Identity Provider configuration cannot be saved in VMware Identity Manager 3.3.3 multi-site environments with embedded connectors from secondary site
    • When using an embedded connector with VMware Identity Manager service in a multi-site environment, you cannot save the identity provider configuration in the secondary site if using an embedded connector.
    • Workaround: Use an external connector for the secondary site.

 

  • Sync fails after upgrading to VMware Identity Manager 3.3.3
    • After upgrade from VMware Identity Manager 3.3.2 to 3.3.3, if the embedded connector is being used with Active Directory over IWA, users can log in, but the directory sync will fail until the embedded connector is migrated to a VMware Identity Manager external connector on a Windows server.
    • Workaround: No workaround. You must migrate the directory from the embedded connector to an external VMware Identity Manager connector. 



Environment

VMware NSX-T Data Center

Resolution