After you upgrade to connector 2018.1.1.1, you may need to configure certain settings.

Log4j Configuration Files

If any log4j configuration files in a connector 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 into the connector instance.

  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 3.2, all standalone connectors must be version 2018.1.1.0 (the connector version in the 3.2 release) or later.

You must also upgrade to Integration Broker 3.2 or later.

Role Based Access Control

Role-based access control has been introduced in VMware Identity Manager 3.2. For known issues, see the VMware Identity Manager 3.2 Release Notes.

Changes in Past Releases

Changes in Release 3.1

  • Beginning with version 3.1, a new feature was introduced that changed the way user groups are synced. After you upgrade to VMware Identity Manager 3.1 or later, for all user groups already added prior to upgrade, ensure that entitlements are assigned. New user groups added after the upgrade are not synced to the VMware Identity Manager service until the group is entitled to a resource, added to an access policy rule, or, beginning with version 3.2, synced manually from the group's Group > Users page.

    If your entitlements are set to ALL USERS, users from new groups created after the upgrade will not be included if the users haven't been synced yet. Add entitlements for the new groups.

    See How Group Sync Works after Upgrading to VMware Identity Manager 3.1 for more information.

  • If you integrate Citrix published resources with VMware Identity Manager, upgrade to Integration Broker 3.1. VMware Identity Manager 3.1 and VMware Identity Manager Connector 2017.12.1.0 require Integration Broker 3.1.

Changes in Release 3.0

  • If you integrate Citrix published resources with VMware Identity Manager, upgrade to Integration Broker 3.0. VMware Identity Manager 3.0 and VMware Identity Manager Connector 2017.8.1.0 (the connector version in the 3.0 release) are not compatible with older versions of the Integration Broker.

    Table 1. Supported Versions

    VMware Identity Manager or Connector Version

    Integration Broker Version Supported

    VMware Identity Manager 3.0

    3.0

    VMware Identity Manager Connector 2017.8.1.0 (Connector version in the VMware Identity Manager 3.0 release)

    3.0

    VMware Identity Manager 2.9.1 or earlier

    2.9.1 or earlier

    VMware Identity Manager Connector 2.9.1 or earlier

    2.9.1 or earlier

  • If you integrate Horizon desktops and applications in VMware Identity Manager and you have deployed a VMware Identity Manager service or connector cluster, you must configure Horizon integration again.

    • In the primary connector, where you saved and synced Horizon resources, remove all the Horizon pods, add them again, and click Save and Sync.

    • In the other connectors, where you saved the Horizon resources configuration, remove all the Horizon pods, add them again, and click Save.