After you upgrade to VMware Identity Manager 3.3, you might need to configure some of the settings.

Configuring VMware Identity Manager Connector Instances

Only the external Windows-based connector is available with VMware Identity Manager 19.03.0.0 and later. The embedded connector is no longer included. The external Linux-based connector is deprecated. Existing instances of the external Linux-based connector continue to be supported for a limited amount of time. To experience full functionality of the external connector, both Windows-based and Linux-based versions, upgrade all connector instances to the newest version of the external Windows-based connector.

  • Installing External Windows-based Connectors. Perform the corresponding procedure depending on the type of connector you are upgrading from.
    Note:
    • Embedded Connector. If you used the embedded connector for a version of VMware Identity Manager earlier than 19.03.0.0 and are now upgrading to version 19.03.0.0 or later, you must install the VMware Identity Manager connector on a Windows system.

      To decrease the amount of information you provide manually, you can perform the necessary migration-related procedures. The following prerequisite applies. During the upgrade, you followed the prompts to save the embedded-connector configuration to the cluster-host-domain-conn-timestamp.enc file in the Install-Folder\VMwareIdentityManager folder.

      1. Copy the cluster...enc file to the Windows system on which you plan to install a respective Windows-based connector instance.
      2. During the installation of the external Windows-based connector and afterwards, perform specific migration-related steps. Use information in Perform Migration-Related Steps When Configuring the External Windows-Based Connector to supplement the instructions in the corresponding version of the Installing and Configuring VMware Identity Manager Connector (Windows) guide.
    • External Linux-Based Connector. If you used one or more external Linux-based connector instances for a version of VMware Identity Manager earlier than 19.03.0.0 and are now upgrading to version 19.03.0.0 or later, you can continue to use the existing connector instances. However, the external Linux-based connector is deprecated and does not include the newest functionality. To experience full functionality, install the respective number of instances of the VMware Identity Manager connector on Windows systems. To decrease the amount of information you need to provide manually, you can perform the following migration-related procedures.
      1. To save external Linux-based-connector configuration information to a cluster...enc file, on each external Linux-based connector instance, run the cluster-migration package (cluster-support.tgz). See Saving External Linux-Based Connector-Configuration Information.
      2. To transfer the external Linux-based-connector-configuration information stored in cluster...enc file instances to instances of the external Windows-based connector, copy each cluster...enc file instance to a respective Windows host before you install the VMware Identity Manager connector on the Windows system. Use information in Perform Migration-Related Steps When Configuring the External Windows-Based Connector to supplement the instructions in the corresponding version of the Installing and Configuring VMware Identity Manager Connector (Windows) guide.
      3. During the installation of the external Windows-based connector and afterwards, perform specific migration-related steps. See Perform Migration-Related Steps When Configuring the External Windows-Based Connector.
    • External Windows-Based Connector. If you used one or more external Windows-based connector instances for a version of VMware Identity Manager earlier than 19.03.0.0 and are now upgrading to version 19.03.0.0 or later, you can continue to use the existing connector instances. However, to ensure full functionality of existing external Windows-based connectors, update the connector instances to version 19.03.0.0 or later.

Enable Cert Proxy for Android Mobile Single Sign-On for Diagnostic Monitoring

If Android Mobile Single Sign-on is configured, after upgrading VMware Identity Manger, you must enable Cert Proxy through the UI to activate diagnostic monitoring.

Go to the Appliance Settings > Mobile SSO Android SSO cert proxy config page and select Enable Cert Proxy. Click Save.

Log4j Configuration Files

If any log4j configuration files in a VMware Identity Manager instance were edited, new versions of the files are not automatically installed during the upgrade. However, after the upgrade, the logs controlled by those files will not work.

To resolve this issue:

  1. Log in to the Windows host.
  2. Search for log4j files with the .rpmnew suffix.

    find / -name "**log4j.properties.rpmnew"

  3. For each file found, copy the new file to the corresponding old log4j file without the .rpmnew suffix.

Citrix Integration

For Citrix integration in VMware Identity Manager 19.03, all external connector instances must be version 19.03 or later.

You must also upgrade to the latest version of the Integration Broker. Upgrade is not available for Integration Broker. Uninstall the old version, then install the new version.