Novell Identity Manager 3.6 Readme

July 23, 2008

This document contains the known issues for Novell® Identity Manager version 3.6.

1.0 Documentation

This Readme contains the known issues for Identity Manager version 3.6. In addition to this Readme, separate Readmes are available for Designer 3.0 and the User Application Roles Based Provisioning Module:

Additional documentation resources are also available for the following:

2.0 Known Issues

The following sections provide information for known issues at the time of the product release.

2.1 Installation

The following sections describe issues you might encounter during installation of the Identity Manager Metadirectory engine and drivers.

2.1.1 Installation fails on Red Hat 5.0

When installing to a Red Hat* 5.0 server, the Installation program might exit without finishing and give the following console message:

/tmp/install.dir.3693/Linux/resource/jre/bin/java: symbol lookup
error: /tmp/lib/ undefined symbol: DDCDuplicateContext

This is a one-time error. Rerun the Installation program.

2.1.2 Maintenance level 5300-04 required when installing on AIX 5L version 5.3

When installing to AIX* 5L version 5.3 with eDirectory™ 8.8.3, the only supported AIX maintenance level is 5300-04. Newer or older maintenance levels are not supported.

2.1.3 Upgrading Identity Manager requires the correct Administrator account to avoid losing Challenge Response answers

When upgrading from an earlier version of Identity Manager on the Windows* platform, you should use the same Administrator account that was used to install eDirectory. For example, if a domain Administrator account was used to install eDirectory, you should use the domain Administrator account again when installing Identity Manager and not use a local Administrator account.

If you do not use the same Administrator account, users’ answers for their Challenge Response questions are no longer accessible. This occurs because the tree key is re-created during the installation (because of the different Administrator account) and the new tree key does not provide the correct access to the stored answers. Users are prompted for new Challenge Response answers when they log in.

2.2 Remote Loader

The following section describes issues you might encounter as you use the Remote Loader.

2.2.1 Updates to the trace screen on Windows 2008 cause a pop-up window to display

When you use the Remote Loader on Windows 2008, if the trace screen is updated, a pop-up window that requires your interaction is displayed.There is no solution to turn off the pop-up window. To avoid this situation, use a trace file instead of the trace screen.

2.2.2 Lotus Notes Driver with Remote Loader 64-bit on Windows Server 2003 SP2 64-bit is not supported

2.2.3 Old configuration files disappear after upgrading Remote Loader from IDM 3.5.1 to IDM 3.6 on Windows Server 2003 64-bit

When you upgrade Remote Loader from 32-bit (IDM 3.5.1) to 64-bit (IDM 3.6) on Windows Server 2003 64-bit, old configuration files disappear from the Remote Loader Console utility.

Work around: Use the command line version of Remote Loader to start the instances:

dirxml_remote.exe -config xxxxx-Config.txt -setpasswords yyyyy zzzzzdirxml_remote.exe -config xxxxx-Config.txt


  • xxxxx-Config.txt is the Remote Loader instance configuration file which is present in the Remote Loader installation folder.
  • yyyyy is the Remote Loader instance password.
  • zzzzz is the driver object password.

For more information on Remote Loader command line options, see usage.html file which exists in the Remote Loader installation folder.

2.2.4 On Linux 64-bit, JVM load operation fails when you start IDM 3.6 Remote Loader

When you start IDM 3.6 Remote Loader on Linux 64-bit, JVM load operation fails displaying the following error message:

rdxml.bin: error: Unable to load JVM

Work around:

  1. Go to /opt/novell/eDirectory/lib/nds-modules.

  2. Type the following command.

    ls -lrt jre

    If the jre directory is present, go to step 3. Otherwise go to step 5.

  3. Move all the jar files from jre/lib/ext to/opt/novell/eDirectory/lib64/nds-modules/jre/lib/ext by doing the following:

    1. Go to /jre/lib/ext.

    2. Type the following command:

      mv *.jar /opt/novell/eDirectory/lib64/nds-modules/jre/lib/ext

    Make sure that there are no files remaining in the jre/lib/ext directory.

  4. Delete the jre directory from /opt/novell/eDirectory/lib/nds-modules.

  5. Type the following command to make sure that you are in the /opt/novell/eDirectory/lib/nds-modules directory.


    Now create a symbolic link to /opt/novell/eDirectory/lib64/nds-modules/jre1.6.0_06 by typing the following command:

    ln -s /opt/novell/eDirectory/lib64/nds-modules/jre1.6.0_06 jre

  6. Start the Remote Loader.

2.3 Drivers

The following section describes issues you might encounter as you use the Identity Manager drivers.

2.3.1 Active Directory driver uses negotiate as the default authentication method

When the Active Directory driver’s basic configuration file is imported to create a new driver, the authentication method is set to negotiate by default. If you want to use simple authentication, change the authentication setting on the driver’s property page after the driver is created.

2.4 iManager

The following sections describe issues you might encounter as you use iManager.

2.4.1 Internet Explorer 7 prompts continually for access to the Clipboard

When you are in iManager, particularly the Policy Builder, Internet Explorer* 7 continually prompts you for access to the Clipboard. To disable prompting:

  1. Click Tools > Internet Options.

  2. Click the Security tab, then click Custom Level.

  3. Click Scripting > Allow programmatic clipboard access, then select Enable.

    After you restart Internet Explorer, the prompting stops.

2.4.2 iManager plug-in dependency for the NDS-to-NDS Driver Certificates Wizard

If you want to use the NDS-to-NDS Driver Certificates Wizard, you must download and install the iManager plug-in for Novell Certificate Server™.

2.5 eDirectory

The following sections describe issues you might encounter related to eDirectory:

2.5.1 Larger eDirectory stack size required on AIX systems

When running Identity Manager on AIX with eDirectory 8.8.3, you need to increase the eDirectory stack size.

  1. Stop ndsd.

  2. Increase the stack size:

    ldedit -b maxstack=0x10000000 /opt/novell/eDirectory/sbin/ndsd
  3. Restart ndsd.

2.5.2 NICI segfault when installing on 64-bit AMD quad core processors

When installing 32-bit eDirectory 8.8.3 on servers that use AMD Opteron* (X86_64) processors, the installation generates a segmentation fault during installation of NICI (Novell International Cryptographic Infrastructure) and NICI is not installed properly.

Novell Support can provide a patch to fix this issue. For information, see Technical Information Document 7000979.

2.5.3 IDM 3.6 does not work after upgrading from OES 2 to OES 2 SP1

When you upgrade OES 2 64-bit to OES 2 SP1 64-bit, eDirectory 8.8.2 32-bit, which was installed with OES 2, is upgraded to eDirectory 8.8.4 64-bit. Because IDM 3.6 does not support 64-bit eDirectory, it does not work after the OES upgrade.

3.0 Documentation Conventions

In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.

A trademark symbol (®, ™, etc.) denotes a Novell® trademark; an asterisk (*) denotes a third-party trademark.

4.0 Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 2008 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

Novell, Inc. has 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 of the U.S. patents listed on the Novell Legal Patents Web page and one or more additional patents or pending patent applications in the U.S. and in other countries.

For Novell trademarks, see the Novell Trademark and Service Mark list.

All third-party trademarks are the property of their respective owners.