Identity Intelligence 1.1.2 includes new features and resolves several previous issues.
Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs.
The documentation for this product is available on the Documentation website in HTML and PDF formats. If you have suggestions for documentation improvements, click Identity Intelligence Documentation page.at the bottom of any page in the HTML version of the documentation posted at the
The following sections outline the key features and the issues resolved in this release:
Identity Intelligence provides REST APIs to integrate with third-party applications. Using Identity Intelligence REST API, you can get information about a user, get access rights details of an identity, and manage views. The REST API documentation contains detailed information about using Identity Intelligence REST APIs. For information about accessing REST API documentation, see Using Identity Intelligence REST API.
Identity Intelligence now includes scripts to collect diagnostic logs from Identity Intelligence, its components, and the operating system. For more information, see Collecting Diagnostic Logs.
Identity Intelligence now includes an out-of-the-box Health and Performance Monitoring dashboard to monitor the status of the database such as disk usage and rate of event ingestion. For more information, see Monitoring Database.
Issue: When you create and delete an entity in quick succession in the data source, you can still view that entity in the Identity Intelligence user interface. (Bug OCTCR28E185344)
Fix: Identity Intelligence displays the entities properly.
Issue: Identity Intelligence does not display approver information in the Summary Panel for workflow processes from Identity Manager. (Bug OCTCR28E185296)
Fix: Identity Intelligence now displays the approver information.
Issue: When uninstalling database by using the uninstall-single-node.sh script, the process gets terminated unexpectedly if you press after typing y at the following prompt:
Are you sure that you want to UN-INSTALL database node(s)? (y/n)?y
Fix: Uninstallation continues even if you press y.after typing
For information about the software and hardware requirements for your deployment and performance tuning guidelines, see Identity Intelligence 1.1 System Requirements.
Before you begin installing Identity Intelligence, you must download and extract Identity Intelligence and all necessary product installation packages. The installation package also includes the respective signature file to validate that the downloaded software is authentic and not tampered by a third party.
You can download the following installation packages:
Contains files required for installing and deploying Identity Intelligence:
Legal information about third party code contained in Identity Intelligence
Driver shim and packages for Identity Manager Driver for Entity Data Model
Configuration utility for Identity Governance
SmartConnector for Identity Intelligence 126.96.36.199.zip
Includes the following:
Installation file for ArcSight Management Center (ArcMC)
To download and verify the signature of downloaded files:
Log in to the computer where you want to install Identity Intelligence.
Change to the directory where you want to download the installer files:
NOTE:If you are planning to install Identity Intelligence by using scripts, use /opt as the download location.
Download all the necessary product installer files from the Micro Focus Downloads website.
To verify the signature of the downloaded files, enter the following command:
Syntax: sha256sum <file_name>; cat <file_name>.sha256
Example: sha256sum identityintelligence-x.x.x.x.zip; cat identityintelligence-x.x.x.x.sha256
The output from each set of compressed installation packages must match their corresponding SHA-256 signatures. If they do not match, download the files again and verify the signature. If the checksum does not match even with the new files, contact Micro Focus Customer Support.
To extract the downloaded files, enter the following commands:
For tar file: tar xvfz <file_name>.tar.gz
For zip file: unzip <file_name>.zip
Micro Focus provides several options to install your Identity Intelligence environment. For more information, see the Administrator Guide for Identity Intelligence.
You can upgrade to Identity Intelligence 1.1.2 only from Identity Intelligence 1.1.1. For information about upgrading Identity Intelligence, see Upgrading Identity Intelligence.
Micro Focus strives to ensure that our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
Issue: In the User Profile page, Identity Intelligence does not display the account details for the account for which User logon name is modified in the Active Directory. Blank space is displayed instead of the modified account details. (Bug OCTCR28E185269)
Fix: This issue is caused by a bug in Identity Manager 188.8.131.52 (Bug 1157343) and is fixed in Identity Manager 184.108.40.206. Therefore, if you are using Identity Manager 220.127.116.11, ensure that you upgrade Identity Manager to version 18.104.22.168 or later.
Issue: Identity Intelligence receives data from Identity Manager through the Identity Manager Driver for Entity Data Model. This driver is designed to collect data that Identity Manager receives from drivers similar to the LDAP-based Directory Integration drivers for Identity Manager. Identity Intelligence can also receive data that originates from other types of Identity Manager drivers. However, some drivers might configure data in a way that the Entity Data Model driver cannot interpret. To avoid corrupting data that might be displayed in View and Profiles, the Entity Data Model driver ignores any collected content that does not meet its expected formatting.
For more information about the LDAP-based Directory Integration drivers, see the documentation site for Identity Manager drivers.
Workaround: If you have an incidence where Identity Intelligence fails to appropriately display data that originates from a non-LDAP-based driver, contact our Customer Center to determine the exact nature of the data problems.
Issue: In the View’s table, when you add a column with fields that contain a large data, Identity Intelligence fails to export data appropriately in the PDF file. For example, some rows in the (Bug OCTCR28E184432)column might contain a large amount of data that Identity Intelligence cannot incorporate it appropriately in the PDF.
Workaround: Export the data as a CSV file.
Issue: If user information such as a name or email ID contains non-English characters, Identity Intelligence displays (Bug OCTCR28E185328)for those non-English characters.
Issue: Identity Intelligence does not display account that was used as an identity source for the user in Identity Governance. (Bug OCTCR28E184435)
Workaround: If you have both Identity Manager and Identity Governance, configure data collection as follows:
Configure Identity Governance to collect data from Identity Manager.
For more information, see Identity Governance documentation.
Configure Identity Intelligence to collect data from both Identity Manager and Identity Governance and ensure that the data reconciliation fields for both the data sources are same.
Issue: In case of access request approval, Identity Intelligence displays approved date instead of creation date because creation date is replaced by approved date when the access request is approved. (Bug OCTCR28E185282)
Issue: Known issues associated with RedHat can affect Identity Intelligence by causing sluggish performance and errors in the server log, particularly in a single-node deployment.
You might observe slow responses times and that some of the deployed pods enter the “CrashLoopBackoff” state. This issue tends to occur because of large quantities of calls to the NFS client. (Bug OCTCR28E185219)
When logging into Identity Intelligence, the server might send you back to the login page, particularly after you first install Identity Intelligence. You might see the following type of error in the idi-web-app log:
Unable to fetch user details from management after retrying, error: StatusCodeError: 401
After logging into Identity Intelligence, you might be redirected to (Bug OCTCR28E185279)> page wherever you click on the user interface.
Follow the instructions in RedHat Solution 3915571.
Restart the User Management pod by performing the following:
Get the User Management pod details:
kubectl get pods --all-namespaces | grep hercules-management
NAMESPACE NAME READY STATUS RESTARTS AGE arcsight-installer-p2dlt hercules-management-7f876b4978-9xkl6 2/2 Running 6 10d
Delete the User Management pod:
kubectl delete pod -n <namespace> <management pod name>
kubectl delete pod -n arcsight-installer-p2dlt hercules-management-7f876b4978-9xkl6
When you delete any pod, the pod will start automatically.
Workaround: There is no workaround at this time.(Bug OCTCR28E185325)
Issue: When you view the details of an entity that was valid in the past but not valid currently by changing the time to (Bug OCTCR28E185326), it displays null values instead of a proper message.
Workaround: There is no workaround at this time.
Workaround: Manually restart all ITOM-DI pods after reinstalling Transformation Hub:
Get the name of all ITOM-DI pods:
kubectl get pods --all-namespaces | grep itom-d
Restart all the pods individually by executing the command:
kubectl delete pod -n <namespace> <ITOM-DI pod name>
Issue: The non-processed access rights event status is displayed as complete instead on non-process in the visualization.(Bug OCTCR28E184510)
Workaround: There is no workaround at this time.
Issue: When you click on a user to view its details in Users and Entities page, it displays the access right details even before the access right is granted to the user.(Bug OCTCR28E185304)
Workaround: There is no workaround at this time.
Issue: After upgrading Identity Intelligence to 1.1.2, when you try to launch the Views created in 1.1.1, it does not load properly.(Bug OCTCR28E185304)
Workaround: After upgrading to Identity Intelligence 1.1.2, you must edit and save all Views.
Log in to Identity Intelligence user interface.
Select a View, then click >.
Edit any property.
Repeat step 3 to 5 for all Views.
Issue: When scanning the cdf-2020.05.00100-22.214.171.124.zip file or an installer *.tar file that contains this file, certain malware detection programs might report a false positive in a subroutine called updateRoleId. This subroutine is within /cdf/images/cdf-master-images.tgz file.
Workaround: None needed. We validated that the code is not malware. We have verified that the package was built and compiled in a secure and trusted fashion. In an upcoming release, we will modify the packaging to avoid this false positive.
For known issues related to CDF, see
Transformation Hub Release Notes in the ArcSight Product Documentation website.
For known issues related to the Entity Data Model driver, see Identity Manager Driver for Entity Data Model Implementation Guide.
© Copyright 2020 Micro Focus or one of its affiliates.
The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.
For additional information, such as certification-related notices and trademarks, see https://www.microfocus.com/about/legal/.