Identity Governance 3.6.2 Release Notes

1.1 Form Builder

This release includes Form Builder, a customized version of a third-party software application, that enables administrators and developers to design complex access request and approval forms and render them dynamically within Identity Governance. For more information about Form Builder, see the Administrator’s Guide to the Form Builder.

1.2 Reporting Enhancements

This release includes enhancements to various reports and the following three new reports:

1.3 Access Request and Approval Enhancements

The integration with Form Builder in this release provides the ability to create default and custom forms and to simulate workflow. For more information about customizing forms, see Creating and Editing Request and Approval Forms in the Identity Governance User and Administration Guide and Administrator’s Guide to the Form Builder.

In addition, this release includes the following enhancements:

1.4 Delegation Enhancements

This release includes self delegation, which allows all Identity Governance users to delegate their tasks. In addition, authorized administrators and their delegates can delegate request approval tasks. For more information about delegation related enhancements, see Creating and Managing Delegation in the Identity Governance User and Administration Guide.

1.5 Enhanced Archiving and Metrics Collection

This release includes the Metrics Data Store, which allows authorized administrators to associate multiple metrics collections with a single data store, and specify the correct data table for collection. This release also includes the ability to archive to Vertica or a separate database. For more information about archive destinations, see Creating an Archive Destination in the Identity Governance User and Administration Guide. For more information about the Metrics Data Store, see Configuring Metrics Data Stores for Custom Metrics in the Identity Governance User and Administration Guide.

1.6 Fulfillment Enhancements

This release includes updated fulfillment target templates to support the Cloud Bridge connection. It also includes a new Flow Data attribute that, when selected, enables Identity Governance to pass custom request form data to the fulfillment workflow. For more information about Flow Data attribute and Fulfillment configuration procedures, see Configuring Fulfillment in the Identity Governance User and Administration Guide.

1.7 Business Role Enhancements

This release includes role hierarchy, which lets you create a hierarchy of roles, based on the mining attributes, that allow you to assign resources either at the candidate level or by grouping the candidates at a higher level. In addition, it includes the ability to download and import business roles and approval policies. For more information, see Understanding Role Hierarchy with Role Mining and Downloading and Importing Business Roles and Approval Policies in the Identity Governance User and Administration Guide.

1.8 Technical Role Enhancements

This release includes the following enhancements:

For more information about technical roles, see Creating and Managing Technical Roles in the Identity Governance User and Administration Guide.

1.9 Separation of Duties (SoD) Policies Enhancements

This release adds Business Roles as an option when creating Separation of Duties (SoD) policies, which provides more granular control over access and SoD enforcement based upon those business roles. It also includes the ability to import and export SoD policies. For more information, see Creating and Managing Separation of Duties Policiesin the Identity Governance User and Administration Guide.

1.10 Cloud Bridge Supported Only in Identity Governance as a Service Deployments

Micro Focus now offers Identity Governance software as a hosted solution to customers interested in a cloud solution. The IGA hybrid solution includes Cloud Bridge that enables Identity Governance as a Service to collect identity and application data from on-premises data centers.

For more information about Cloud Bridge, see Understanding Cloud Bridge in the Identity Governance User and Administration Guide. For more information about the IGA hybrid solution, see Identity Governance as a Service Quick Start.

1.11 Miscellaneous Enhancements

In addition to the above new features and enhancements, this release also includes:

3.1 Installing Identity Governance

If you have not previously installed Identity Governance or want to create a new environment, see Planning to Install Identity Governance in the Identity Governance 3.6 Installation and Configuration Guide.

3.2 Upgrading from a Previous Version

Existing customers can upgrade to this version after preparing their current environment for a successful migration of data to the new version. For information about the upgrade process, see “Upgrading Identity Governance” in the Identity Governance 3.6 Installation and Configuration Guide.

3.3 Installing the Custom Collector SDK

The NetIQ Custom Collector SDK helps with custom collector and fulfillment template creation and maintenance. The Custom Collector SDK is available as a separate download package on the Identity Governance download page.

4.1 Upgrading Will Enable Collector and Fulfillment Target Templates Disabled in a Prior Version

4.2 Upgrading Will Remove Currency setting

4.3 Review Items Criteria is Not Displaying Properly When the Review is Imported

4.4 “Remove Technical Role Assignment” Appears as an Unsupported Fulfillment Type

4.5 Permissions, Technical Roles, and Applications Will Not Show Authorized by Business Role

The Identity Governance catalog will not display authorized by details for permissions, technical roles, or applications assigned to a business role when the business role does not have members.

4.6 Installation Program Displays Unreadable Text

Use the following steps to configure the proper fonts file:

4.7 Compensating Request Cannot be Sent through an Automated Fulfillment Process

When compensating revoke requests are issued, they cannot be sent through any automated fulfillment process. The system will not have enough information about the permission assignment to determine the path upon which to fulfill the request. Revoke requests will be sent to the configured manual fall back for that type of request.

4.8 Moving a User from One Business Role to Another Using Curation Makes User Lose Authorized Permissions

This is possible because after curation, separate detections are triggered for BR1 and BR2, instead of a single detection that does both together. If detection is first done on BR1 (the role the user lost membership in) followed by BR2 (the role the user gained membership in), Identity Governance would issue an auto-revoke, followed by a compensating auto-grant. If detection is first done on BR2 followed by BR1, auto-revoke or auto-grant request will not be issued. Based on your fulfillment approach (manual, workflow, automatic, custom), in the case where detection first occurs on BR1 and then BR2, causing an auto-revoke request and compensating auto-grant request to be issued, the user could lose the permission between the fulfillment of the auto-revoke request and the fulfillment of the compensating auto-grant request.

4.9 Installing on RHEL Might Require Additional Files

4.10 OSP Installer Hangs in GUI Mode When Using ssh X11 Forwarding

If you run a GUI-mode installer using ssh -Y, and the installer appears to hang, then either run the installer in console mode, or try a different client machine.

4.11 Browser Can Inadvertently Change the Credentials for the Identity Manager Connection

You can observe this issue in Administration > Identity Manager System Connection Information. When the browser replaces the values for Identity Manager username and password, Identity Governance erroneously enables the save icon.

4.12 Cannot Recognize Date Values that Are Not in Default Java Format

4.13 Restart Identity Governance after Restarting the Database Server

After you restart the server for the Identity Governance database, you must restart Identity Governance. Otherwise, Identity Governance might fail to complete processes such as data source publication. For more information, see Starting and Stopping Apache Tomcat in the Identity Governance 3.6 Installation and Configuration Guide.

4.14 Oracle Error Unable to Extend Table

ORA-01653: unable to extend table ARDCS.BASIC_COLLECTED_ENTITY by 1024 in tablespace USERS

The problem is the tablespace that Identity Governance uses for schemas has run out of space. (Bug 989425)

SQL> connect sys/oracle as SYSDBA
Connected.

SQL> alter session set container=pdborcl;

After issuing the commands, then you can alter the tablespace by adding data files.

4.15 Inconsistent Behavior When Using Wildcards

This issue will be fixed in a future release of the product. For more information, see Supported Wildcards and Handling Wildcards as Literal Characters in Identity Governance User and Administration Guide.

4.16 NullPointerException (NPE) Can Occur When Starting and Canceling a Review

In some cases, if you start a review and then cancel the review as it starts, a stack trace containing a NullPointerException could be output to the server console or logs by the Quartz third-party library.

4.17 Unresponsive Script Error in Firefox Can Occur When Clicking a User in the Certification Policy Violation Popup Window

4.18 Identity Manager Permissions that Have Dynamic Bound Entitlement Values are Not Available for Selection in SoDs, Technical Roles, and Business Roles

Identity Governance does not currently support selection of Resources/dynamic bound entitlements in SoDs, Technical Roles, and Business Roles within Identity Governance. This issue will be fixed in a future release of the product.

4.19 Incorrect Change Request Types Appear When Configuring Application Setup for Fulfillment

If you configure Application Setup for Fulfillment, and select Supported Change Request Types, the following two request types appear:

These change request types are not application specific and should not appear.

4.20 The Shortcut Drop-Down List of a Select Box Component Does Not Render Correctly

.form-group.formio-component-select.formio-component-shortcut {
 margin-right: 0;
}

.form-group.formio-component-select.formio-component-shortcut .choices.form-group[data-type*='select-one'] {
  margin-right: 0;
}

.form-group.formio-component-select.formio-component-shortcut .choices.form-group[data-type*='select-one'] .choices__button {
  margin-right: 18px;
}

For more information about custom.css file see, Customizing the Identity Governance Style Sheet in the Identity Governance 3.6 Installation and Configuration Guide

4.21 Forms Comparison Displays Incorrectly When Using Inline Scripts

In the Form Builder, one can create inline scripts that can be used as helper functions. Be aware, however, that since these inline scripts are published to the global javascript context, unexpected results may occur. One example of this is in the compare to draft to published area, where one has two forms up at the same time. In this case, both forms will end up sharing the same inline function, even if the definition of the function was different between the draft and published form.

4.22 In Custom Forms, Text on Some Tabs Cannot be Localized

In the Form Builder, text that appears on the following component tabs cannot be localized, because Form.io does not currently support localization for this text:

Click here for more information.

4.23 In Custom Forms, Text on the Data Tab of the Password Component is not Localized

In the Form Builder, text on the Data tab of the Password Component appears in English, regardless of the selected language. The issue lies with Form.io, who is aware of the issue. You can check the Form.io status of the issue here.

4.24 The Form Builder User Interface is not Fully Localized

The Form Builder user interface is not fully localized for languages, other than English, that Identity Governance and Identity Reporting support. Full localization support is planned for an upcoming Form Builder release. This issue affects the following Form Builder components that, unless otherwise indicated, are accessible by clicking the Form Builder icon on the Form Builder left navigation pane:

4.25 Items in the Form Builder Editing Pane are Partially Localized

When creating or editing a form in Form Builder, some field and button labels in the Editing pane appear in English, rather than language selected for localization. The completed form will be correctly localized, however. You can click the Preview icon on the left navigation to verify that the form is correctly localized.

4.26 The Form Builder Address Form Component Does Not Function in Identity Governance

The Address Form component in the Form Builder does not function, because it requires the Form.io Server, which Form Builder does not utilize within Identity Governance. The Address Form component is scheduled for removal in a future release.

4.27 Custom Forms Do Not Display Request Item Description in Bold Italics By Default

Though we support markdown for permission and application description, currently we do not have a markdown viewer for request forms. Because of this, any markdown syntax in an application or permission form will display as it is instead of being rendered as expected.

4.28 In Custom Forms, Approval Address Component Does Not Receive Information from Request When Using a Custom Default Value Field

When creating a custom form, the Approval Address field accepts values from the request address field only if using the Calculate Value. The Approval Address field does not receive information if using the Custom Default Value. The issue lies with Form.io, who is aware of the issue and is working toward a solution.

4.29 In Custom Forms, Validate On: Blur Does Not Function as Expected

Validations are not triggered if the ValidateOn property of a component is set to Validate on Blur, but will, instead, validate on change. The issue lies with Form.io, who is aware of the issue and is working toward a solution. You can check the Form.io status of the issues here and here.

4.30 In Custom Forms, Action Type Properties Can Appear When They Are Not Applicable

When adding a layout component to a form and configuring Action Types, Value appears as an option, but this option is not applicable for a layout component. The issue lies with Form.io, who is aware of the issue and is working toward a solution.

4.31 In Custom Forms, Online Help Does Not Exist for Tree Component

When you click Help while adding a tree component to the layout of a custom form, an error appears. The issue lies with Form.io, who is a aware of the issue and is working toward a solution.

4.32 In Custom Forms, Date/Time Values Appear as Invalid in Firefox

If you use Mozilla Firefox as your browser, and you create a custom form in which you incorporate a Date/Time component and then use the Modal Edit options, the date is shown to be invalid. The issue lies with Form.io, who is aware of the issue and is working toward a solution.

4.33 In Custom Forms, Applied Tag Attributes Are Not Set

Tag attributes configured for a custom form are applied, but not set. The issue lies with Form.io, who is a aware of the issue and is working toward a solution.

4.34 A Custom Form Configured for Multiple Phone Numbers Displays A Single Phone Number Field

If you create a form with a phone number component, and select Multiple Values, the Form Renderer displays only a single phone number entry field. The issue lies with Form.io, who is aware of the issue and is working toward a solution.

4.35 In Custom Forms, Shortcuts Do Not Function as Expected

If you create a form and add a component that allows you to configure a keyboard shortcut, the shortcut does not function unless you first manually interact with the component. The issue lies with Form.io, who is aware of the issue and is working toward a solution.

4.36 In Custom Forms, the Default Value is not Retained When “Multiple Values” and “Clear Value on Refresh” Options Are Selected

If you add a field to a form and configure Multiple Values and Clear Value on Refresh for the field component, the field is not set back to the default value when you refresh the component. The issue lies with Form.io, who is aware of the issue and is working toward a solution.

4.37 In Custom Forms, Setting a Check Box to be Selected as a Default does not Function as Expected

If you use the JS editor to set the custom default value for a check box component to be selected, the check box does not appear selected. The issue lies with Form.io, who is aware of the issue and is working toward a solution.

4.38 On the Custom Forms Logic Tab, Event Trigger Types with the “Hidden” Property Set, Do Not Hide the Configured Component

If you configure a component to be hidden by setting the following properties:

Clicking the button does not hide the component as configured. This behavior is observed for the following components:

The issue lies with Form.io, who is aware of the issue and is working toward a solution.

4.39 Navigating Away from Unchanged Page Might Result in Erroneous Prompt to Save Changes

5.1 Fact Publication to Vertica Configuration Does Not Have a Schema Name Field

This release resolves the issue by allowing you to explicitly specify the schema name when you create or edit an Archive Destination.

5.2 Comparing Two Application Data Sources Collection Activities Can Erroneously Report Differences

5.3 My Approval Page Does Not Render Fully