iManager 2.7.7 Patch 5 includes enhancements, 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 inputs. We hope you continue to help us ensure our products meet all your needs.
For a full list of all issues resolved in NetIQ iManager 2.7, including all patches and service packs, refer to TID 7010166, “History of Issues Resolved in NetIQ iManager 2.7”.
For more information about this release and for the latest Release Notes, see the iManager Documentation Web site.
For the list of software fixes and enhancements in the previous releases, see iManager 2.7.7 Patch 4 Release Notes.
To download this product, see the NetIQ Downloads Web site.
iManager 2.7.7 Patch 5 provides the following updates and fixes in this release:
In addition to the platforms introduced in the previous iManager releases, this release adds support for the following platforms:
SLES 11 SP4 (SUSE Linux Enterprise Server)
RHEL 6.7 (Red Hat Enterprise Linux)
RHEL 7.1
Windows 2008 and Windows 2008 R2
Windows 2012
This release adds support for Java 1.8.0_60.
This release adds support to the following browsers, in addition to the browsers introduced in iManager 2.7.7 Patch 4 or earlier releases:
Mozilla Firefox 40
Google Chrome 44, 45
Microsoft Edge (from Windows 10)
This release includes software fixes that resolve several previous issues.
Issue: The upgrade process resets the configuration settings to their default values. (Bug 843774)
Fix: This patch updates the upgrade code to preserve the configuration settings of iManager.
Issue: iManager cannot display the full length of the fully distinguished name (FDN) of a member due to the fixed size of the RBS window. (Bug 919285)
Fix: This patch provides you the facility to adjust the size of the RBS window to view the complete user context.
Issue: If you search a user by last name, it does not return the correct user object because the search escapes the Polish or special characters into its HTML numerical code. (Bug 867631)
Fix: With this patch, the advanced selection filter returns the user objects whose name contains Polish or special characters.
For information on system requirements, see the NetIQ iManager Installation Guide.
Log in to the NetIQ Downloads page and follow the link that allows you to download the software. Ensure that you are currently on any one of the following iManager versions, before upgrading to iManager 2.7.7 Patch 5:
2.7.7
2.7.7 Patch 1
2.7.7 Patch 2
2.7.7 Patch 3
2.7.7 Patch 4
For information about upgrading iManager, see Upgrading iManager in the NetIQ iManager Installation Guide.
NetIQ Corporation strives to ensure 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, contact Technical Support.
Section 4.1, Identity Manager Plug-in Returns Java Script Error
Section 4.3, Cannot Start iManager Workstation on an openSUSE Computer
Section 4.8, Unsupported Platform Error on RHEL 6.5 and RHEL 5.10
Section 4.9, iManager Dependency on Novell Client with NMAS Support - iManager
Section 4.10, Newly Added Members to a Dynamic Group Are Not Displayed in the Corresponding Fields
Section 4.11, Groups Plug-in Does Not Handle Unspecified Addresses in ldapInterfaces
Section 4.12, Novell Logo Appears in the iManager Login Page After Upgrading to NetIQ iManager 2.7.7
Section 4.13, Base Content is Displayed After Upgrading to iManager 2.7.7 on Windows Platform
Section 4.14, iManager Login Fails if NICI 2.7.6 is Installed On Windows Workstation
Section 4.15, Plug-ins Selected from Local Disk are Not Listed in the Installation Summary
Section 4.16, Identity Manager Plug-in Does Not Work in iManager 2.7.7
Section 4.19, Identity Manager Plug-ins Do Not Work After Upgrading to iManager 2.7.7 Patch 5
After upgrading to iManager 2.7.7 Patch 5, when you use the Identity Manager plug-in to manage your driver sets or drivers, you receive a Javascript warning. If you navigate to another location, such as View Objects, you immediately return to the login screen.
This issue occurs when your browser caches iManager information that does not have the necessary tokens. To resolve this issue, clear your browser cache, and then log back in to iManager. (Bug 816973)
After upgrading to iManager 2.7.7 Patch 5 on a Windows Server 2012 computer, the Tomcat service might not restart automatically. You must manually restart the service.
To run iManager Workstation on a computer running version 12.2 or 12.3 of the OpenSUSE operating system, ensure the following OpenSUSE packages are installed:
libgtk-2_0-0-32bit
libXt6-32bit
libgthread-2_0-0-32bit
libXtst6-32bit
The following IPv6-related issues are present in iManager 2.7.7:
Symantec Network Threat Protection conflicts with IPv6 addresses. To use IPv6 addresses in iManager 2.7.7, you must disable Network Threat Protection.
To use IPv6 addresses in iManager 2.7.7, you can use the Firefox 32 browser.
If your iManager installation uses IPv4 addresses, and you use the Import Convert Export Wizard to connect to an eDirectory installation that uses IPv6 addresses, the wizard fails to connect and displays the following error:
Unable to connect to the requested server. Verify the name/address and port.
To configure iManager to handle IPv6 addresses, complete the following steps:
Open the catalina.properties file, and comment out the following lines:
java.net.preferIPv4Stack=false
java.net.preferIPv4Addresses=true
NOTE:The java.net.preferIPv4Stack property applies to communication between iManager and eDirectory. The java.net.preferIPv4Addresses property applies to communication between browsers and iManager.
Restart Tomcat.
In iManager, click Roles and Tasks.
Click LDAP > LDAP Options, and then select the View LDAP Servers tab.
Select the LDAP server you want to configure and click the Connections tab.
Under LDAP Server, add LDAP interfaces for the IPv6-format addresses, including the port numbers, as follows:
ldap://[xx::xx]:389 ldaps://[xx::xx]:636
Click OK.
Configure the Role-Based Services, then log out from the session and log in again.
The following issues in the Tree tab of the Object View are present in iManager 2.7.7:
The Tree view does not save its state, including the current position within the tree, when you switch between the Tree view and the Browse/Search tabs.
When you click View objects, you cannot perform any pop-up related operations in Tree view, Browse, and Search tabs.
To workaround this issue, launch Internet Explorer 10 in compatibility mode.
iManager 2.7.7 does not support metro user interface view for Internet Explorer 10.0 in Windows 7.0 and 8.0 versions.
While installing the latest eDirectory plug-in on RHEL 5.8 (64-bit), iManager returns the following exception message:
File not found exception message
To workaround this issue, restart Tomcat.
While installing iManager 2.7.7 on RHEL Server release 6.5 and RHEL Server release version 5.10, the installer displays a warning message stating that the platform is unsupported.
To workaround this issue, include Redhat Enterprise Linux Server release 6.5 and Redhat Enterprise Linux Server release 5.10 in the platforms.xml file. For more information about installing iManager on unsupported platforms, see Installing iManager on Unsupported Platforms in the NetIQ iManager Installation Guide.
iManager requires NMAS support to be installed on the Windows system on which iManager is installed. It does not require the Novell Client. If you are going to use the Novell Client, iManager requires a version with NMAS support.
When you access iManager by using an IPv6 address and then add new members to a dynamic group, the members are not displayed in the Included Members and All Members fields.
To work around this issue, you can configure LDAP by using iManager or the eDirectory command prompt.
To configure LDAP by using iManager, complete the following steps:
Install eDirectory 8.8 SP8.
In iManager, go to Roles and Tasks list, and then click LDAP > LDAP options.
Click the View LDAP Servers tab, then select the appropriate server.
On the LDAP Server page, click the Connections tab, add a new LDAP server (for example, ldaps: [ipv6_address]:LDAP_SSL_PORT) in the LDAP Interfaces field, then click OK.
Click Apply, then click OK.
To determine whether LDAP is configured for IPv6, enter the ldapconfig get command in the eDirectory command prompt. The following values are listed in the result if LDAP is configured:
ldapInterfaces: ldaps://[ipv6_address]:LDAP_SSL_PORT
Require TLS for Simple Binds with Password: yes
If LDAP is not configured, enter the following command to configure it:
ldapconfig set "ldapInterfaces= ldaps://[ipv6_address]:LDAP_SSL_PORT"
The Groups plug-in reports an error if there are unspecified addresses in the ldapInterfaces attribute of the LDAP server.
During installation or configuration, eDirectory automatically configures the LDAP server to listen on all available interfaces by adding ldap://:389 and ldaps://:636 to the ldapInterfaces attribute. The plug-in interprets these values incorrectly and tries to connect to the LDAPS port on the iManager server computer. The connection fails, and the Groups plug-in displays the following error messages:
Unable to obtain a valid LDAP context.
Creating secure SSL LDAP context failed: localhost:636
To work around this issue, remove unspecified addresses and add specific IP addresses to ldapInterfaces.
Novell logo appears in the iManager Login page after upgrading it from previous versions to iManager 2.7.7.
To workaround this issue, clear the browser cache and relaunch iManager.
When iManager 2.7.6 is upgraded to iManager 2.7.7, iManager Base Content is displayed in the Available NetIQ Plug-in Modules list. Though it appears in the list of available plug-ins, the Base Content is installed during the upgrade process.
It is safe to ignore it and continue working on iManager because it does not affect the iManager functionality in any way. However, if you do not want the Base Content to display in the list, select iManager Base Content, click Install, and then restart Tomcat.
iManager 2.7.7 fails to login and displays the following error message, if you have installed NICI 2.7.6:
Unable to create AdminNamespace.java.lang.NoClassDefFoundError: Could not initialize class novell.jclient.JClient
To workaround this issue, remove NICI 2.7.6 using the Add or Remove Programs option in Control Panel and then install NICI 2.7.7, which is available in the iManager 2.7.7 build.
While installing iManager 2.7.7 plug-ins, the ones selected from the local disk are not listed in the Installation Summary page, whereas the plug-ins selected from the NetIQ download page are listed.
However, the plug-ins selected from the local disk are installed even though they are not listed in the Installation Summary page.
The Identity Manager plug-in does not work in iManager 2.7.7 if you have selected both Identity Manager plug-in and SecretStore plug-in options during iManager installation.
To workaround this issue, select only Identity Manager plug-in during iManager installation. Alternatively, use the iManager UI to install the Identity Manager plug-in and then separately install the SecretStore plug-in.
To workaround this issue, uncomment the appender that you want to enable. For example, to enable Novell Audit appender uncomment the following line:
<appender-ref ref="NAUDIT_APPENDER"/>
After this, restart Tomcat.
After installing iManager 2.7.7 Patch 5, the configuration file changes and this stops iManager from sending the audit events.
To workaround this issue do the following steps:
Install iManager 2.7.7 patch 4.
Uncomment the following line in the /var/opt/novell/iManager/nps/WEB-INF/imanager_logging.xml file:<appender-ref ref="NAUDIT_APPENDER"/>
Restart Tomcat.
Issue: The Identity Manager plug-ins do not work in iManager 2.7.7 Patch 5 if you have not selected the Identity Manager plug-in option during iManager installation.
Workaround: To install the Identity Manager plug-ins, use one of the following methods:
Select the Identity Manager plug-in option during iManager installation.
Use the iManager Plug-in installer to install the Identity Manager plug-ins. For more information, see Downloading and Installing Plug-in Modules in the NetIQ iManager Administration Guide.
NetIQ Corporation, and its affiliates, have intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more U.S. patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU.
For purposes of clarity, any module, adapter or other similar material (“Module”) is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions.
This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data.
This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time.
U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R. 227.7202-4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (for non-DOD acquisitions), the government's rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement.
© 2015 NetIQ Corporation. All Rights Reserved.
For information about NetIQ trademarks, see http://www.netiq.com/company/legal/.