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 6
After upgrading to iManager 2.7.7 Patch 6, 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 6 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 6, 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 6.
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 6 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.