Tokenizing Out-of-Box Connectors for Language Switching in Identity Manager

Products

• CA Identity Suite
• CA Identity Manager
• CA Identity Governance
• CA Identity Portal

Issue/Introduction

The Language Switching feature in the Identity Manager User Console may fail to display localized content for out-of-box (OOTB) connectors, resulting in screens appearing in English only. Although the RoleDef JAR files provided with these connectors include translated property files, the default XML content within the JAR is not tokenized. To enable language switching, the RoleDef XML must be manually tokenized and updated to reference the existing localized properties.

Environment

Identity Manager

Resolution

To localize the OOTB connector screens, perform the following steps to tokenize the RoleDef XML file:

1. Extract the RoleDef XML: Locate the RoleDef JAR file for the specific connector (e.g., CA_Top_Secret_v2.jar) within the \standalone\deployments\iam_im.ear\user_console.war\WEB-INF\lib\ directory. Unjar the file to extract the META-INF.CA_<Connector_Name>-RoleDef.xml.

2. Generate Tokenized Files: Use the Identity Manager localization tool (refer to \Identity Manager\IAM Suite\Identity Manager\tools\samples\Localization\readme.htm for setup) to run the ant command:

   ant tokenizeroledef -Dinputfile=<Extracted_RoleDef_XML>

   Note: This generates a <FileName>_Tokenized.xml and <FileName>_Tokenized.properties file.

3. Update the XML File: Open the generated <FileName>_Tokenized.xml file. Perform a find-and-replace operation to ensure the bundle path references the provisioning resources.

   • Find: ${bundle=resourceBundles.<Connector_Name>-RoleDef_Tokenized
   • Replace with: ${bundle=provisioning.resourceBundles.<Connector_Name>-RoleDef_Tokenized

4. Import the Updated XML: Save the modified file (e.g., ..._Tokenized_Fixed.xml) and import it into the Identity Manager Management Console to replace the existing definition.

5. Finalize Changes: Restart the Identity Manager Environment (IME) on all nodes to apply the changes. The screens should now support language switching using the property files already bundled within the connector JAR.

Additional Information

The product documentation has also been updated with the "Import Role Definition in a Localized Environment" section as well which provides additional similar approaches on steps you can take to localize the out of box connector:

Import Role Definition in a Localized Environment