The 25.1 (v4.5) version of OpenText Identity Governance and Administration solution includes new features, improves usability, 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. You can post feedback in the OpenText Identity Governance and Administration forum on the communities website, our online community that also includes product information, blogs, and links to helpful resources.
For more information about this release, see the OpenText Identity Governance Documentation website.
This release provides functional, infrastructure, and performance-related fixes and enhancements. It includes:
Ability to add Authorization Owner as a reviewer in the Business Role Authorization Review definition
Ability to detect attribute changes using data policies
Ability to reset calculated user risk scores to collected risk scores
New technical role related data policies to monitor technical role attributes such as name, description, cost, and risk
Improvements to collection and publication process to automatically disable publication when you change data source parameters after collection and before publication
Ability to import and export Review definitions, Business Role policy, Business Role Approval policy, and Fulfillment Catalog Update Setup configurations as SQLite files
Ability to view events that triggered the full business role recalculation
Ability to customize Insight Query collection and scheduling delay time after modifying queries or upgrading application
New Business Role Definition History - CSV report
Continued improvements for enhanced accessibility, user experience, and localization
Miscellaneous infrastructure, security, and performance improvements such as improved data policy calculations
The following features have either been removed or have been deprecated and will be removed in a future release:
The ability to import Coverage Map CSV file is now obsolete. Use the Coverage Map capability in the user interface to create coverage maps and export and import coverage maps as JSON files.
Starting with Identity Governance 4.2, fulfillment to BMC Remedy was deprecated. It will be removed in a future release.
For more information about browser requirements and supported components for this release of OpenText Identity Governance, and additional supported drivers and packages for accounts and permissions collection from the OpenText Identity Manager environment, see the OpenText Identity Governance and Administration Quick Start Guide.
We strive 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.
No review items found when Application Administrator is used as the filter
Governance dashboard widget tooltips show incorrect times when collection time is noon or later
An unexpected error occurs when a sorting members of a business role by supervisor
Unable to request the removal of business roles using Access Request
SCIM driver fails to update IDM entitlement fulfillment status
Custom forms do not display request item description in bold italics by default
Issue: In Account, Account Access, or User Access reviews, when you select application as the review criteria and filter by administrator, OpenText Identity Governance does not display any review items.
Workaround: Select Application Owner as the filter criteria.
Issue: Time of activities such as metric collection is shown in the database correctly. However, time shown on Governance dashboard widget tooltips might appear as AM even if the collection time was PM.
Issue: When you create a business role with a membership expression, such as Title matches Software Engineer, then click Show Matching Users to view the matching users and add supervisor as a column to sort the users, you might see a message: Encountered unexpected error. Clicking View Members on a Business Role Membership tab also results in an unexpected error.
Issue: In Access Request, users can request business roles but might not be able to request their removal.
Issue: Even if a change request, such as adding a user to a group in SAP application, is fulfilled successfully, OpenText Identity Governance displays the status as Pending Verification. This occurs because the SCIM Driver fails RFC 7644 pagination specifications and returns only limited entitlements to OpenText Identity Governance. This issue will be fixed in a future release.
Issue: If two business roles (BR1 and BR2) authorize the same permissions and specify auto-grant and auto-revoke on those permissions, and a manual or bulk data update (also known as curation) moves a user from BR1 to BR2, the user could lose the permission for a period of time between the fulfillment of the auto-revoke request and the fulfillment of the compensating auto-grant request.
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), OpenText 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.
Workaround: It is recommended that you do not utilize curation if you have business roles with overlapping permissions that are enabled for auto grants and auto revocation. If data update occurs, check business role detections (Policy > Business Roles > Business Role Detections) to verify that a compensating grant request was issued, and if not, detect inconsistencies (Policy > Business Roles > Manage Auto Requests) and issue a grant request.
Issue: Notification template tokens that are created in the Workflow Administration Console cannot be inserted in the template’s message section.
Workaround: Copy the token with the dollar sign $, for example, $Test token$ and paste it in the message body and save the template.
Issue: When multiple values are mapped using flowdata.getObject(), all the values are populated in a single field. For example, in the Workflow Administration Console, create a form that requires multiple values, such as text field, email, and phone number. Create a workflow with two approval activities and attach the form with the activities. In the pre-activity data mapping of the second approval activity, map the fields with multiple values from the first approval activity’s form using the flowdata.getObject(). In OpenText Identity Governance, request that workflow. Navigate to > Approvals > Workflow Approvals and select Approve or Deny to launch the approval form of the workflow. Type the values for the requested fields and launch the next approval form. The data mapped from the previous form using flowdata.getObject() displays all data in a single field.
This issue will be fixed in a future release.
Issue: Inability to publish workflows when the Request Content field in the Rest Activity contains the slash slash (//) expression in a comment.
Workaround: To save and publish the workflow, use the slash-star (/*) star-slash (*/) while adding a comment.
Though OpenText Identity Governance supports markdown for permission and application descriptions, currently it does not have a markdown viewer for request forms. As a result, any markdown syntax in an application or permission form will display as it is instead of being rendered as expected.
Some known issues lie within third-party applications that are integrated with OpenText Identity Governance. The following known issues can be tracked with the third-party vendor. We provide links to those issues where available.
In the Form Builder, text that appears on some of the component tabs cannot be localized, because Form.io does not support localization for this texts. This will be fixed in a future release.
Issue: If Form Builder was used from the Workflow console to create an approval workflow that requires two approval activities, and you provided two or more phone numbers during the first approval activity, those phone numbers will not appear in the second approval activity. The issue lies with Form.io, who is aware of the issue and is working toward a solution.
Workaround: Click Add Another under the Phone Number field to make the provided phone numbers appear.
If Form Builder was used from the Workflow console to create an approval workflow that requires two approval activities, and multiple values were supplied during the first approval activity, those values will duplicate in the subsequent approval activity if you click the Add Another button. The issue lies with Form.io, who is aware of the issue and is working toward a solution.
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.
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.
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.
Online help does not exist for the tree component. The issue lies with Form.io, who is aware of the issue and is working toward a solution.
Some event trigger types with the “Hidden” property set do not hide the configured component. The issue lies with Form.io, who is aware of the issue and is working toward a solution.
This issue has been fixed. Manual or bulk editing (curation) will now result in only one effective record for accounts and permissions.
This issue has been fixed. All permissions and accounts are routed correctly when the assigned reviewer is the permission owner.
This issue has been fixed. The report does not have duplicate remove account actions.
This issue has been fixed. When copying or importing review definitions, schedule will be deactivated and the review will not start automatically.
This issue has been fixed. Users should no longer see errors such as Group with ID: 100 was not found when reviewing items during Business Role Definition review runs.
This issue has been fixed. OpenText Identity Governance correctly validates the selected criteria based on Coverage Map type.
The following issues have been fixed:
Policy owner name does not resolve in Insight Query Results email
Account categories are not displayed correctly in Insight Query results
Errors accessing, creating, or modifying Insight Queries after upgrading
The greetings in the Insight Query Results email resolve correctly, account category is displayed correctly, and users can access, create, or modify Insight Queries after upgrading without errors.
Issues related to Entity Change data policies that specify Add or Remove operations have been fixed.
Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@microfocus.com. We value your input and look forward to hearing from you.
For support, visit the CyberRes by OpenText Support Website or email cyberressupport@microfocus.com.
For interactive conversations with your peers and experts, become an active member of our community. The online community provides product information, useful links to helpful resources, blogs, and social media channels.
The only warranties for products and services of Open Text and its affiliates and licensors (“Open Text”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Open Text shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.
Copyright 2025 Open Text.