No tasks are displayed on new CA IdentityMinder environment creates after an upgrade or the new environment create fails after an upgrade to 12.6sp2

No tasks are displayed on screens for new environment creates after an upgrade of a CA IdentityMinder system.

QuestionKey

Issue:

Installing or upgrading IDM to 12.6 sp2 fails to display the correct screens or task rights for any new environments being created after the upgrade from 12.6 sp1 or prior versions. The access of even the “system Manager” role does not work or display the correct tasks associated with the role.

Root cause:

Once an upgrade is performed on an IDM system, the directory template is version specific. Meaning you cannot use an older directory that was built off the 12.6 sp1 or prior versions with an IDM at version 12.6 sp2 if you are trying to build/add a new environment.

*This has not been tested on other application servers other than JBOSS 5.1GA, however, the issue / resolution should be the same as it is tied to the IDM version and directory template XML.

A line at the top of the directory XML looks like this:

<ImsDirectory name="ImUserStore" description="IdentityMinder UserStore" version="12.6.1.0.318" wellknownfile="imsconfig://wellknown/LDAPImsWellKnown.xml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="imsconfig://schema/ImsDirectory.xsd">

As you can see it is version specific { see red above}.

12.6 sp1 = version="12.6.1.0.318"

12.6 sp2 =  version="12.6.2.0.213"

Solution/Workaround:

After the upgrade, export the existing directory(s), open the directory template in a text editor and replace the SP1 version with the SP2 version then save the file. Use the updated XML file to update the existing directory to the new version. Then you can create new environments with the updated directory. This has not shown to affect existing environments that are configured on the system.

The updated directory XML would look like this:

<ImsDirectory name="ImUserStore" description="IdentityMinder UserStore" version="12.6.2.0.213" wellknownfile="imsconfig://wellknown/LDAPImsWellKnown.xml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="imsconfig://schema/ImsDirectory.xsd">

See the updated version above { see red above}.

*If you are installing a new IDM 12.6sp2 application, be sure to use the directory template from the installation source. When doing this, be on the lookout for directory data field definitions that sate “searchable=false”. With, 12.6sp1, these fields are defaulted to “searchable=true”, but for some reason in 12.6sp2, CA decided to change the default to “searchable=false” even though the directory XML comment code says it should be true by default. At least this was one new issue I ran across in my testing.