After you upgrade to VMware Identity Manager 3.3.6, you might need to configure certain settings.
Enable Multi-Tenancy with vRealize Automation 8.4
You can enable multi-tenancy if VMware Identity Manager 3.3.5 is deployed with vReallize Automation 8.4. See Enable Tenant-In-Host Name Multi-Tenancy with vRealize Automation 8.4.
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 do not work.
To resolve this issue:
- Log in to the virtual appliance.
- Search for log4j files with the .rpmnew suffix.
find / -name "**log4j.properties.rpmnew"
- For each file found, copy the new file to the corresponding old log4j file without the .rpmnew suffix.
Upgrading from 3.3.4 and 3.3.5 with Kerberos Authentication Adapter Configured
If you upgrade VMware Identity Manager from 3.3.4 or 3.3.5 to 3.3.6 and have the Kerberos adapter configured, after the upgrade, unjoin the connector from the domain, then rejoin the connector back to the domain.