Novell IMANAGER 2.7.3 - README 8-26-2010 User manual

iManager 2.7.3 Field Patch (FTF) 4 Readme 1
novdocx (en) 16 April 2010
Novell®
iManager 2.7.3 Field Patch (FTF) 4
Readme
August 26, 2010
This readme contains the following sections:
Section 1, “What is New,” on page 1
Section 2, “Downloading and Installing iManager Support Pack,” on page 2
Section 3, “Issues Resolved in iManager 2.7.3,” on page 4
Section 4, “Known Issues,” on page 5
Section 5, “Additional Readme Information,” on page 18
Section 6, “Legal Notices,” on page 19
1 What is New
iManager 2.7.3 includes the following product enhancements:
Section 1.1, “Newly Supported Platforms and Browser,” on page 1
Section 1.2, ““Hide” and “Show Hidden” Buttons in the Available Novell Modules Page,” on
page 1
Section 1.3, “Preferred Object Selection Method for a Task of a Property Book,” on page 2
Section 1.4, “Ability to Add Organizational Role to the Authorized Users and Groups List,” on
page 2
Section 1.5, “iManager Caches Login Information for Faster Login,” on page 2
Section 1.6, “Ability to Configure the Proxy by using DNS,” on page 2
1.1 Newly Supported Platforms and Browser
In addition to the existing platforms and Web browsers, iManager 2.7.3 FTF 4 supports Windows 7
(32-bit and 64-bit), Windows 2008 R2 platforms, and Internet Explorer 8 (IE 8).
For more information on the supported platforms, refer to the iManager 2.7.3 Installation Guide
(http://www.novell.com/documentation/imanager27).
1.2 “Hide” and “Show Hidden” Buttons in the Available Novell
Modules Page
The following two buttons are newly available in the Available Novell Plug-in Modules page:
Hide: Clicking this button hides the selected Novell plug-in modules. You can also hide all the
plug-in modules so that the Home page doesn't display the
New iManager NPMs are
available to install
notice.
Show Hidden: Clicking this button displays the list of the hidden Novell plug-in modules. You
can unhide the hidden plug-in modules.

2iManager 2.7.3 Field Patch (FTF) 4 Readme
novdocx (en) 16 April 2010
1.3 Preferred Object Selection Method for a Task of a Property
Book
In the Property Book page, the user can now define/modify a preferred object selection method for
an existing task. For this, a new feature, Target Chooser Mode has been added to the Actions list.
1.4 Ability to Add Organizational Role to the Authorized Users
and Groups List
In the Security page of the Configure iManager window, the user can now add an Organizational
Role to the Authorized Users and Groups list so that all the members (users and groups) of the
organization become authorized users.
1.5 iManager Caches Login Information for Faster Login
iManager now caches the first-time-login information with the tree name and uses that information
in the subsequent logins. This process makes the logins fast.
1.6 Ability to Configure the Proxy by using DNS
The user can now configure a proxy also by using DNS names. The proxy host field now accepts
DNS names also.
2 Downloading and Installing iManager Support
Pack
IMPORTANT: iManager support packs do not make a backup of files replaced. The only way to
roll back to a previous state is to backup all modified files before applying the support pack and then
manually restoring the backed up files.
Also, iManager support packs must be installed on all iManager servers in your environment.
Support packs do not automatically replicate other iManager servers in your tree.
NOTE: After you install the iManager support pack, iManager will be non-functional until you
restart Tomcat.
To download and install an iManager support pack:
By Using Novell Download Site
1Download
iman273_FTF4.npm file from the Novell download site to your local machine.
2Log in to iManager.
3Click Configure >Plug-in Installation > Available Novell Plug-in Modules.
4Click Add and browse to the
iman273_FTF4.npm file, then click OK.
5Verify that the module is
iman273_FTF4.npm and the description reads Field Patch 4 for
iManager 2.7.3
.
6Select the check box next to the field patch file
iman273_FTF4.npm and click Install.

iManager 2.7.3 Field Patch (FTF) 4 Readme 3
novdocx (en) 16 April 2010
The installation takes a few minutes.
NOTE: Internet Explorer might append a .zip extension to the .npm when it is downloaded.
The browser might actually remove the
.npm extension, and replace it with .zip . The
extension must be .npm . Otherwise, the installation does not upload the file.
7Click Close and Restart Tomcat.
NOTE: Tomcat sometimes requires several minutes to fully initialize. Wait a few minutes
before trying to log into iManager after restarting Tomcat.
Table 1 Restart Tomcat
8Verify that the new support pack has been installed.
Log in to iManager, then check whether the home page displays the new version (2.7.3
FTF 4).
Check the log file located in webapps/nps/WEB-INF/changelog .
Click Novell iManager in the upper-left corner of the iManager application window to
view the iManager information page.
By Using iManager
1Log in to iManager.
2Click Configure >Plug-in Installation > Available Novell Plug-in Modules.
3Select the check box next to the support pack plug-in and click Install.
The installation takes a few minutes.
4Follow Step 7 in “By Using Novell Download Site” on page 2.
5Follow Step 8 in “By Using Novell Download Site” on page 2.
NOTE: When you install iManager plug-ins, sometimes either the installation hangs or the plug-ins
are not properly installed. To troubleshoot the issue, see “iManager Plug-in Installation Hangs or
Plug-ins Are Not Properly Installed” in the iManager 2.7.3 Administration Guide.
PLATFORM RESTART COMMAND
NetWare 6.5 Enter TC5STOP . Wait at least a minute, then enter TOMCAT5
to start the service again.
Windows Stop and start the Tomcat service.
Linux Enter /etc/init.d/novell-tomcat5 stop, then enter /etc/init.d/
novell-tomcat5 start.
Mobile iManager Close Mobile iManager and re-open Mobile iManager.

4iManager 2.7.3 Field Patch (FTF) 4 Readme
novdocx (en) 16 April 2010
3 Issues Resolved in iManager 2.7.3
The following issues are resolved in the iManager 2.7.3 FTF 4 release:
iManager 2.7.3 FTF 3 installation hangs if earlier FTF installation files have not been
uninstalled.
Security Vulnerability - iManager stack buffer overflow - Creating a class name with more than
32 characters by using other scripts (perl / python).
Security Vulnerability - iManager off-by-one DoS - If login request is sent with a Tree field
length of 256 characters.
Security Vulnerability - CVE-2009-3555 - OpenSSL Handshake renegotiation of the existing
connections.
Privileged User can instigate a DoS under the context of the service. (No Trace) - Providing
Auditing and logs while authorized users upload the npm files.
The following are the issues resolved in the iManager 2.7.3 FTF 3 release:
Delay in the next login attempt after a login failure.
The Case Ignore List adding multiple attribute values to a single attribute.
Unauthenticated files that get uploaded onto Access Manager.
The following are the issues resolved in the iManager 2.7.3 FTF 2 release:
The security vulnerability issue faced during installation of external plug-ins.
The following are the issues resolved in the iManager 2.7.3 FTF 1 release:
The Others tab while modifying user is empty with iManager 2.7.3.
Cannot browse/select objects from IE 8 browser.
In IE 8, the iManager Tree view option was not listing.
iManager plugin fails to uninstall cleanly.
Objects created with alternate naming attribute in some cases.
The following issues are resolved in iManager 2.7.3:
Error message for deleting object is not localized.
Configure iManager task is not displayed for the member of a nested group which is an
Authorized user.
Plug-ins are not removed when you select Select all plug-ins option in the Available Novell
Plug-in Modules page, deselect one or more plug-ins in the list, and click Remove.
iManager (2.7 with Tomcat 5.5) login screen, by default, has Autocomplete enabled which
results in security vulnerability.
Replace option under the Identification tab of the Modify User page does not work.
Large number of XSS vulnerabilities exist in iManager 2.7.
iManager 2.7.2 removes RBS collection ownership for a user when the user is added to /
removed from a group object.
Plug-in allows inconsistency of group and group membership.

iManager 2.7.3 Field Patch (FTF) 4 Readme 5
novdocx (en) 16 April 2010
A user, who has logged in to iManager through Internet Explorer, as a t1 trustee user cannot
view the property pages.
Plug-in download does not function when you add a plug-in with name same as that of one of
the existing plug-ins, and rename the exiting plug-in of the same name.
Plug-ins are not displayed because of clash between .jar files.
Uniqueness scan does not work if a tree has more than 7000 users.
Login script that is created with Novell client appears blank in iManager.
iManager tree view filter does not work when you use scandinavian characters.
4 Known Issues
The following issues exist in the iManager 2.7 environment:
Section 4.1, “Security Message Appears while Using IE 8,” on page 7
Section 4.2, “Tree View Issues,” on page 7
Section 4.3, “Invalid RBS Member Association can Cause Java Exception,” on page 7
Section 4.4, “Authentication Error with SLES 9,” on page 7
Section 4.5, “Plug-In Compatibility,” on page 8
Section 4.6, “iManager Login Page Issues,” on page 8
Section 4.7, “International Characters Might Not Display Correctly During Install,” on page 8
Section 4.8, “(Windows Servers Only) Installing eDirectory and iManager on the Same
Machine,” on page 9
Section 4.9, “(Windows Servers Only) iManager Doesn't Work after Installing Groupwise 7.0
WebAccess,” on page 9
Section 4.10, “Blank Screen or Missing Roles and Tasks,” on page 9
Section 4.11, “Time Out Setting for Dynamic Groups Returns an Error Message when the Time
Out Is Set to a Value That Can Be Exceeded,” on page 9
Section 4.12, “Special Characters,” on page 9
Section 4.13, “Two Instances Do Not Maintain Connections to Two Different Trees,” on
page 10
Section 4.14, “javaw.exe Application Error when Closing iManager Workstation or SDK,” on
page 10
Section 4.15, “Control Characters in Login Script,” on page 10
Section 4.16, “Translation Errors in InstallAnywhere Installer,” on page 11
Section 4.17, “eDirectory Error Messages Language Settings,” on page 11
Section 4.18, “Link Disappears or Unable to View All the Options,” on page 11
Section 4.19, “Null Pointer Exception Trying to Load iManager Login Page,” on page 11
Section 4.20, “(NetWare only) Plug-In Install Does Not Proceed without Mouse,” on page 11
Section 4.21, “(NetWare only) On a non-English Server Install, iManager 2.6 Is Displayed
Instead of iManager 2.7,” on page 12
Section 4.22, “After Installation of iManager 2.7 on NetWare 6.5 sp7, the Login Page Might
Not Appear,” on page 12

6iManager 2.7.3 Field Patch (FTF) 4 Readme
novdocx (en) 16 April 2010
Section 4.23, “Unable to Create AdminNamespace.java.lang.NoClassDefFoundError,” on
page 12
Section 4.24, “Issue with Internet Explorer while Opening Data Table Elements in a New
Window or a New Tab,” on page 12
Section 4.25, “Tomcat Restart after Installing a Plug-In,” on page 13
Section 4.26, “iManager mvStringEditor Tag Exhibits Strange Behavior,” on page 13
Section 4.27, “Admin Allows Only “AllUsers” as the Authorized User of eDirectory to Access
iManager,” on page 13
Section 4.28, “Security Alert Warning Message Is Displayed Many Times on iManager
Workstation,” on page 13
Section 4.29, “iManager Workstation (Windows) Sometimes Does Not Display Information,”
on page 14
Section 4.30, “Objects Are Not Available in History, Group Member, and Group Membership
Property Book Pages,” on page 14
Section 4.31, “When You Make a Group as Nested and Dynamic, It Might Not Properly
Function,” on page 14
Section 4.32, “Precedence of the Methods for Changing the Page Order of a Property Book,”
on page 15
Section 4.33, “508 Testing-Valued or Unvalued Attributes Cannot Be Edited using Keyboard,”
on page 15
Section 4.34, “Some of the DSFW Objects Are Defined as Unknown Type in iManager,” on
page 15
Section 4.35, “DSFW Administrator Cannot Configure RBS in iManager,” on page 15
Section 4.36, “The Custom Plug-Ins Which Were Installed before iManager 2.7.2 Are
Displayed as “X” under the “Installed” Column in the Plug-In Studio Page,” on page 15
Section 4.37, “Newly added Property Book pages such as Nested Settings, Group Member, and
Group Memberships Do Not Appear while Modifying a Group.,” on page 16
Section 4.38, “iManager User Cannot Log In to a Child Server that Holds the Replica of a
Partition when the Master Server is Down,” on page 16
Section 4.39, “iManager Plug-In Uninstallation Does Not Properly Happen on Windows
Vista,” on page 16
Section 4.40, “iManager Installation in Portuguese-Brazilian Locale Corrupts the
gettingstarted.html File,” on page 17
Section 4.41, “Uninstallation of iManager Plug-In Does Not Happen Properly,” on page 17
Section 4.42, “Tomcat Crashes while Creating a Custom Plug-In,” on page 17
Section 4.43, “NDS Login Hangs during Invalid Login,” on page 18
Section 4.44, “Java Exception in PKI Plug-In due to the dependency on Compat RPM,” on
page 18
Section 4.45, “Authentication Error with SLES 10 SP3,” on page 18

iManager 2.7.3 Field Patch (FTF) 4 Readme 7
novdocx (en) 16 April 2010
4.1 Security Message Appears while Using IE 8
While working with iManager through IE 8 browser and when you click the View Objects tab, a
security warning message appears. It is the security provided by IE 8 that mentions
Do you want
to view only the webpage content that was delivered securely
.
To block this message from appearing, perform the following in the IE 8 browser:
1Click Tools > Internet options.
The Internet Options window is displayed.
2Click the Security tab. By default, the Internet option is selected.
3Click Custom Level.
The Security Settings window is displayed.
4In the Miscellaneous section, enable “Display mixed content” (select the Enable option
corresponding to Display mixed content).
5Click OK.
4.2 Tree View Issues
The following issues exist in the new Tree tab of the Object View:
4.2.1 Navigation Frame Object List Does Not Update
In the Object View’s Tree tab, the effects of container actions are not immediately reflected in the
Navigation frame’s object list. For example, adding a container, or changing an existing container’s
name, is not reflected in the Navigation frame until you manually refresh the view by leaving the
Tree view and then re-opening it.
4.2.2 Tree View Does Not Save State Information
Tree View does not currently save its state, including current position within the tree, when
switching between Tree View and the Browse/Search tabs.
4.3 Invalid RBS Member Association can Cause Java
Exception
If you inadvertently specify an invalid user name or scope when creating RBS Member
Associations, when you try to save the changes iManager displays the following error:
The system encountered an unknown error. Please contact Novell Support.
This error prevents a successful save operation for any valid data that you might have entered. To
avoid this problem, use the Object Selector to locate valid objects and scopes when configuring
iManager RBS.
4.4 Authentication Error with SLES 9
You might encounter the following error while authenticating iManager on a Server with SLES 9
SP3 or later version:

8iManager 2.7.3 Field Patch (FTF) 4 Readme
novdocx (en) 16 April 2010
Unable to create AdminNamespace. java.lang.NoClassDefFoundError when
authenticating on SLES 9.
Work around: Install compat-libstdc++-33-3.2.3-61.i386.rpm before installing iManager 2.7.
4.5 Plug-In Compatibility
Because of changes to class structure and organization, iManager plug-ins must be recompiled to
work with iManager 2.7. The iManager 2.7 Web site contains all currently available plug-ins, and
will be regularly updated with additional plug-ins when they are available. If you add an older plug-
in using Add Plug-in link, it does not display an error even though the plug-in is not added. You can
view specific error information in the debug log.
Similarly, the OES 2 download includes the currently available iManager 2.7 plug-ins.
NOTE: iManager 2.7 does not allow the user to install old plug-ins that iManager 2.6 supported.
4.6 iManager Login Page Issues
Be aware of the following login-related issues with iManager 2.7:
4.6.1 iChain Single Sign-On (SSO)
The iChain Single Sign-On functionality (including Forward authentication, OLAC, and Form Fill)
does not work in a multi-tree environment. iManager 2.7 requires a user name, password, and tree
name for login, whereas iChain requires only user name and password.
Form Fill from iChain also fails because the Exit button in the iManager toolbar directs you back to
the initial login form. When Form Fill is active, you are simply logged back in to iManager.
In a single server environment, it is possible to use the iManager default settings and iChain will
work correctly.
4.6.2 NetIdentity Login
For the same reasons as iChain SSO, NetIdentity can cause problems with iManager login.
When using iManager 2.7 on a NetWare 6.5 SP3 server that was previously running iManager 2.x
and Virtual Office, NetIdentity clients see a NetIdentity login dialog box that only requires user
name and password, instead of the iManager login dialog box that requires user name, password,
and tree name.
4.7 International Characters Might Not Display Correctly
During Install
If, during the installation, there are problems with the display of the characters, you might need to
change the system's character encoding to UTF-8.
Installing remotely through an ssh client might also require UTF-8 character encoding on the client
to display characters properly.
For example, set the system variable LC_ALL=de_DE.utf8, then try running the install again.

iManager 2.7.3 Field Patch (FTF) 4 Readme 9
novdocx (en) 16 April 2010
4.8 (Windows Servers Only) Installing eDirectory and iManager
on the Same Machine
If you want to install eDirectory and iManager on the same physical machine, you must install
eDirectory before you install iManager. This allows eDirectory to perform the initial system
configuration as required.
4.9 (Windows Servers Only) iManager Doesn't Work after
Installing Groupwise 7.0 WebAccess
On Windows 2000 and 2003 Server with IIS 5 or 6, installing Groupwise®7.0 WebAccess to IIS
automatically installs Tomcat 5.5.
As the iManager installation begins, the iManager installer program detects that IIS and Tomcat are
available for use. The installer reports the inability to stop the iisadmin service. Near the end of the
install, the installer reports the inability to start Tomcat.
After the install is completed, GroupWise WebAccess still works, but iManager does not (HTTP
404: Page not found).
Work around: Do not install iManager and GroupWise on the same Windows server.
4.10 Blank Screen or Missing Roles and Tasks
This most commonly occurs when accessing different versions of iManager with the same browser.
Resolve this problem by clearing the browser's stored cookies and cache and restarting the browser.
4.11 Time Out Setting for Dynamic Groups Returns an Error
Message when the Time Out Is Set to a Value That Can Be
Exceeded
When this occurs, the following message appears: Unknown meaning for error number -
6016; Please call a Novell provider
, but the value is saved. When you access Dynamic
Groups, another error message appears:
The system encountered an unknown error. Please
contact Novell support.
The workaround is to give the Time Out setting an adequate and reasonable value.
4.12 Special Characters
iManager does not escape special characters automatically. Using a special character in an object
name will cause an error unless you manually escape the character. More information is available in
the iManager documentation (http://www.novell.com/documentation/imanager27/
imanager_admin_27/data/bovjgnu.html).

10 iManager 2.7.3 Field Patch (FTF) 4 Readme
novdocx (en) 16 April 2010
4.12.1 Plug-In Studio Can't Find the RBS Collection When Trying to Install an Edited
Plug-In.
Plug-In Studio can't find RBS Collections that have special characters in their names, so attempting
to edit a plug-in that has been previously installed into an RBS Collection with special characters in
its name causes the install to fail.
4.12.2 Using Special Characters When Creating a Property Book
Creating a Property Book, and naming it using special characters might cause a DNS Error 603
message. For more information about naming a Property Book, see “Creating a New Property
Book” in the iManager documentation (http://www.novell.com/documentation/imanager27/
imanager_admin_27/data/bypd8g8.html).
4.12.3 iManager Framework Does Not Support Special Characters in Plug-In IDs.
To create a plug-in ID that includes extended characters, create the plug-in using standard
characters, then use Advanced Properties to change the plug-in display name after it has been
created.
4.13 Two Instances Do Not Maintain Connections to Two
Different Trees
Two instances in Firefox and Internet Explorer 8 tabbed views do not maintain connections to two
different trees. Internet Explorer 6 maintains one session per instance, while Firefox uses the same
session for all instances that use the same profile.
This difference in Web browser behavior gives the appearance that Firefox cannot support two
different sessions and that connection information is crossing over. iManager can maintain a
connection to two different trees at the same time in the Firefox browser, but only if each instance is
using a different profile.
To work different sessions simultaneously, modify your profile using Firefox's Profile Manager
(http://www.mozilla.org/support/firefox/profile). In Firefox 2.0 and 3.0, you can use the
-no-
remote
option when launching Firefox to run multiple profiles simultaneously.
4.14 javaw.exe Application Error when Closing iManager
Workstation or SDK
When closing iManager Workstation or SDK, you might encounter a javaw.exe Application Error.
The error is benign and does not indicate any system problems or instabilities. You can safely close
the error message box and continue working normally.
4.15 Control Characters in Login Script
Using ASCII control characters in a login script might cause an Unhandled Exception Error in
iManager. For this reason, Novell recommends using only the standard ASCII character set when
creating login scripts.

iManager 2.7.3 Field Patch (FTF) 4 Readme 11
novdocx (en) 16 April 2010
4.16 Translation Errors in InstallAnywhere Installer
iManager leverages Macrovision* InstallAnywhere* for its installation routine. Because of this,
some of the language translation for the installation routine is provided by Macrovision. Novell has
encountered a few errors in these Macrovision translations that it cannot access to correct. For
example, when you are prompted to select a language for the installation, the language selection
“Slovak” is translated to “Anglictina”, which means English rather than Slovak.
Novell is working with Macrovision to get these translation errors corrected.
4.17 eDirectory Error Messages Language Settings
The iManager Language Preferences setting does not change the language of eDirectory error
messages, even though the language of iManager Web interface is changed.
To work around this issue, change the operating system default language on the eDirectory server
that iManager is using.
4.18 Link Disappears or Unable to View All the Options
Novell iManager might not display the links or third row of options in the Property Book, if the
window size is minimized.
To work around this issue, expand the window or consider using a resolution greater than 1024 x
768.
4.19 Null Pointer Exception Trying to Load iManager Login
Page
When you try to access iManager from a browser, sometimes the Login page fails to load, and
displays the following error message:
exception java.lang.NullPointerException
com.novell.emframe.fw.servlet.AuthenticatorServlet.service(AuthenticatorServl
et.java:334) javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
The browser cookies might be corrupted.
Work around: Clear the browser cookies, then try to access iManager.
4.20 (NetWare only) Plug-In Install Does Not Proceed without
Mouse
During iManager 2.7 installation, you may not be able to change focus to the dialog that asks if you
want to install iManager 2.7 plug-ins without using a mouse. This may prevent you to proceed with
the install.

12 iManager 2.7.3 Field Patch (FTF) 4 Readme
novdocx (en) 16 April 2010
4.21 (NetWare only) On a non-English Server Install, iManager
2.6 Is Displayed Instead of iManager 2.7
If you perform a non-English install of NetWare 6.5 SP7, iManager 2.6 is displayed as the product in
multiple places during the install. Also, the list of installed products will display a product of
iManager 2.6 with a version of 2.7.0. Even though iManager 2.6 is displayed as the product,
iManager 2.7 is the version that is installed.
4.22 After Installation of iManager 2.7 on NetWare 6.5 sp7, the
Login Page Might Not Appear
This is the result of the iManager 2.0.2 uninstall not removing the line Include sys:/tomcat/4/
conf/nps-Apache.conf
from SYS:\Apache2\conf\httpd.conf . You will also see a Apache2
startup error in
SYS:\Apache2\logs\startup.err .
As a workaround, you must:
1. Edit SYS:\Apache2\conf\httpd.conf .
2. Remove the line
Include sys:/tomcat/4/conf/nps-Apache.conf from the bottom
of the file.
3. Save the changes.
4. Start Apache2, ap2webup.
4.23 Unable to Create
AdminNamespace.java.lang.NoClassDefFoundError
You might encounter the above error when authenticating to eDirectory with iManager 2.7
Workstation or SDK on SLED 10. This indicates the problem while updating NICI. You might
notice a message that prime NICI was unsuccessful when you updated NICI.
NICI 2.7.0 is installed with SLED 10 and the Open Desktop Edition add-on (ODE). iManager 2.7
requires NICI 2.7.3 and prompts you to install when you run iManager 2.7 Workstation or SDK for
the first time. The issue is because NICI 2.7.0 is not successfully upgraded to NICI 2.7.3. During the
update, you get a message that prime NICI was not successful.
Work around: Remove both versions of NICI on the system, ignoring any dependencies. For
example, the ODE add-on itself has a dependency on NICI. So, remove NICI by telling the Software
Management to ignore the dependency. Re-install NICI 2.7.3 that you got with iManager 2.7
Workstation. Before you install NICI 2.7.3, make sure that you delete the
/var/novell/nici
directory.
4.24 Issue with Internet Explorer while Opening Data Table
Elements in a New Window or a New Tab
While doing RBS Configuration in Internet Explorer, if you try to open a Data Table Element in a
new window or a new tab, you cannot get the desired result. Instead, you should directly click the
links.

iManager 2.7.3 Field Patch (FTF) 4 Readme 13
novdocx (en) 16 April 2010
4.25 Tomcat Restart after Installing a Plug-In
After installing a plug-in such as, service pack, if you immediately (without waiting at least for 3
Seconds) click Close, a blank page appears. Now you should restart Tomcat:
For Windows: Restart tomcat services from Control Panel->Administrative Tools->Services.
For Linux: /etc/init.d/novell-tomcat5 restart
For NetWare:
1.
TC5STOP
2. TOMCAT5
4.26 iManager mvStringEditor Tag Exhibits Strange Behavior
Internet Explorer 6.0 does not display tooltips for the items in a list. So, the iManager
mvStringEditor tag does not show tooltips for the values it contains. This is fixed in Internet
Explorer 7.0 or later and it shows tooltips for the values in the iManager
mvStringEditor tag.
4.27 Admin Allows Only “AllUsers” as the Authorized User of
eDirectory to Access iManager
If the Admin wants to allow all the eDirectory users to access iManager, he should add AllUsers
(case sensitive) to the Authorized User list in the Configure page.
If the Admin adds an invalid user, for example, Allusers to the list, then he cannot modify the
Configure page next time when he visits the page. A message,
Current logged in user is not
authorized to configure iManager
is displayed.
Work around: In Configiman.properties file, modify the corresponding line as AllUser=true.
4.28 Security Alert Warning Message Is Displayed Many Times
on iManager Workstation
After authentication on iManager 2.7 workstation, the following Security Warning message is
displayed:
The information you have entered is to be sent over an unencrypted connection
and could easily be read by a third party. Are you sure you want to continue
sending this information?
The message is also displayed many times when you go to the tree view, and the other parts of
iManager.
Work around:
1. Open the
security-prefs.js file from <imanager workstation folder>/bin/
windows/mozilla/greprefs.
(for Windows)
Open the security-prefs.js file from <imanager workstation folder>/bin/linux/
mozilla/greprefs.
(for Linux)
2. Modify the following settings from true to false as:

14 iManager 2.7.3 Field Patch (FTF) 4 Readme
novdocx (en) 16 April 2010
pref("security.warn_entering_secure", false);
pref("security.warn_leaving_secure", false);
pref("security.warn_submit_insecure", false);
New downloads of Linux workstation have these flags set to false , by default.
4.29 iManager Workstation (Windows) Sometimes Does Not
Display Information
iManager workstation might not display error messages, pop-ups, and load pages like Tree View,
Object Browse, and Create Objects. This happens when the XULRunner browser cache contains old
data of the previous build of iManager 2.7 workstation.
As a workaround, you must manually clear the data from browser cache:
1. Exit iManager.
2. Go to:
Windows:
C:\Users\<username>\AppData\<Profile>\Mozilla\eclipse\Cache
(Windows XP)
C:\Users\<username>\AppData\Roaming\Mozilla\eclipse\Cache (Windows 7/Vista)
Linux:
/home/<username>/.mozilla/eclipse/Cache
3. Delete the data in the Cache directory.
4. Restart iManager.
4.30 Objects Are Not Available in History, Group Member, and
Group Membership Property Book Pages
The Object Selector icons in the Group Member and Group Membership property book pages allow
you to select the objects that have auxiliary class nestedGroupAux in their Object Class attributes.
However, the design for adding such objects to the history requires nestedGroupAux to be an object
type. Therefore, these objects are not added to the history.
4.31 When You Make a Group as Nested and Dynamic, It Might
Not Properly Function
You can make a Nested Group also a Dynamic Group and vice versa by using the Object Extension
task under Schema role. However, as long as eDirectory allows the auxiliary classes to be added to
the objects by using the Object Extension task, iManager does not check them. Therefore, if you
make a group as nested and dynamic, it might not properly function.

iManager 2.7.3 Field Patch (FTF) 4 Readme 15
novdocx (en) 16 April 2010
4.32 Precedence of the Methods for Changing the Page Order
of a Property Book
Changes done to the page order of a Property Book through Preferences have higher precedence
than reordering the Page List for the same Property Book while modifying the Role Based
Collection through Role Based Services. This is because the latter modifies the Property Book object
in the eDirectory, whereas the former is specific to a particular Property Book on particular
iManager server.
4.33 508 Testing-Valued or Unvalued Attributes Cannot Be
Edited using Keyboard
The user cannot select valued or unvalued attributes select boxes by using keyboard.
Work around: In Firefox 3, press Scroll Lock + Up/Down arrow or Shift + Ctrl + Up/Down
arrow
.
In Internet Explorer 7, press Scroll Lock + Up/Down arrow .
4.34 Some of the DSFW Objects Are Defined as Unknown Type
in iManager
When you log in to iManager that is connected to eDirectory, where DSFW server is installed, as
Administrator, and try to modify the objects under a container, for example blr.novell.com, a few
objects of type Users, Configuration, Computers, and so on appear as undefined. A “?” is displayed
against the object types.
4.35 DSFW Administrator Cannot Configure RBS in iManager
DSFW administrator cannot configure RBS in iManager. He/she fails to do while modifying ACL
value. This is because the rights for the DSFW administrator are limited that he/she has the
supervisor rights only on the domain and subdomains which he/she manages. But he/she does not
have all rights as the Tree administrator.
4.36 The Custom Plug-Ins Which Were Installed before
iManager 2.7.2 Are Displayed as “X” under the “Installed”
Column in the Plug-In Studio Page
After upgrading the iManager version to 2.7.2, the custom plug-ins that are installed prior to 2.7.2,
are shown as Xunder Installed column in the Plug-in Studio page.
As a workaround, select the plug-in, then click Edit > Install. The plug-ins are installed with the
features of iManager 2.7.2.

16 iManager 2.7.3 Field Patch (FTF) 4 Readme
novdocx (en) 16 April 2010
4.37 Newly added Property Book pages such as Nested
Settings, Group Member, and Group Memberships Do Not
Appear while Modifying a Group.
After upgrading the iManager version to 2.7.2, newly added Property Book pages such as Nested
Settings, Group Member, and Group Memberships do not appear while modifying a group by using
the Modify Group task.
Work around: You should manually assign the pages to the Modify Group property book for the
RBS Collection being used, or create a new RBS Collection.
To manually assign the pages to the Modify Group property book:
1. Click the Configure tab.
2. Click Role Based Services > RBS Configuration. The RBS Configuration page is displayed.
3. Click the existing RBS Collection. The Collection: <RBS Collection> page is displayed.
4. Click the Property Book tab, then select the Modify Group, and then click Actions > Page List.
The Edit Page List page is displayed.
5. From the Available Pages: list, select Group Member, Group Memberships, and Nested
Settings, then click the Right Arrow so that the selected items are moved to the Assigned
Pages: list, and then click OK. The message,
The property book was successfully
modified
is displayed.
To create a new RBS Collection:
1. Click the Configure tab.
2. Click Role Based Services > RBS Configuration. The RBS Configuration page is displayed.
3. Click New > Collection and Setup. RBS Configuration Wizard is invoked. This guides you to
create a new RBS Collection with the newly added pages.
4.38 iManager User Cannot Log In to a Child Server that Holds
the Replica of a Partition when the Master Server is Down
When the master or parent server is down, the iManager user cannot find the tree root because the
information of the tree root is available only with the master/parent server. Because the user cannot
find the tree root, he/she cannot log in to the child server which has the replica.
4.39 iManager Plug-In Uninstallation Does Not Properly
Happen on Windows Vista
When you uninstall iManager plug-ins on Windows Vista, the uninstallation does not properly
happen. Even though you get an uninstallation successful message, you can still view the plug-ins as
installed in the Installed Novell Plug-in Modules list.
Work around: The problem occurs because
.com.zerog.registry.xml file that is required for
uninstallation might be hidden. You should make the file available for uninstallation by making it
visible:
1. Click Start > My Computer. The My Computer page is displayed.

iManager 2.7.3 Field Patch (FTF) 4 Readme 17
novdocx (en) 16 April 2010
2. Click Tools > Folder Options. The Folder Options dialog box is displayed.
3. Click View.
4. Under Advanced settings:, select Show hidden files and folders.
4.40 iManager Installation in Portuguese-Brazilian Locale
Corrupts the gettingstarted.html File
When installing iManager (of any language) in Portuguese-Brazilian locale, if you set the LANG
environment variable to
pt_BR.UTF-8 , pt_BR.utf8 , or pt_BR , the installer corrupts the
gettingstarted.html file of the particular language.
As a workaround, before starting the iManager installation, set the LANG environment variable to
pt_PT.UTF-8 by entering the following command at the terminal:
export LANG=pt_PT.UTF-8
4.41 Uninstallation of iManager Plug-In Does Not Happen
Properly
If you have installed a plug-in through iManager 2.7.2 or earlier versions and if you try to uninstall
this plug-in through iManager 2.7.3 or later version, the plug-in does not get uninstalled properly.
In this case, you must manually uninstall the plug-in by removing the following directories:
 \<Tomcat>\work\Catalina\localhost\nps\org\apache\jsp\portal\modules\<plugin_
name_dir>
 \<TOMCAT>\webapps\nps\portal\modules\<plugin_name_dir>
 \<TOMCAT>\webapps\nps\WEB-INF\modules\<plugin_name_dir> (The MANIFEST.MF
file is present in this directory and must be deleted)
 \<TOMCAT>\webapps\nps\WEB-INF\lib\<plugin_jar_file>
 \<TOMCAT>\webapps\nps\WEB-
INF\classes\com\novell\nps\modules\<plugin_name_dir>
You must also delete the UninstallerData directory for the plug-in that you want to delete. The
UninstallerData directory is present in the following path:
NetWare:
SYS:\tomcat\5.0\webapps\nps\UninstallerData\Uninstall_<plugin_name>
Windows: C:\Program
Files\Novell\Tomcat\webapps\nps\UninstallerData\Uninstall_<plugin_name>
Linux: /var/opt/novell/tomcat5/webapps/nps/UninstallerData/
Uninstall_<plugin_name>
4.42 Tomcat Crashes while Creating a Custom Plug-In
On Netware 6.5 SP8, while editing an existing Custom task in plug-in studio or creating a new
Custom plug, if you click Preview, tomcat5 crashes and a Service Unavailable message appears.

18 iManager 2.7.3 Field Patch (FTF) 4 Readme
novdocx (en) 16 April 2010
4.43 NDS Login Hangs during Invalid Login
Nds Login hangs for sometime (10-15 minutes) while trying to login using invalid user authetication
such as as
o=novell or =novell .
To avoid this issue, you must copy and place the latest NMAS library:
Linux: Place the libnmasclnt.so file in the /var/opt/novell/iManager/nps/WEB-INF/bin/
linux
directory.
Windows: Place the nmas.dll and nmasmsg.dll files in the /tomcat/webapps/nps/WEB-INF/
bin/windows
directory.
4.44 Java Exception in PKI Plug-In due to the dependency on
Compat RPM
While trying to access the tasks of Novell Certificate Server or Novell Certificate Access through
iManager, iManager throws a java exception error (
java.lang.NullPointerException\n at
com.novell.admin.PKI.certificate.eDir.eDirCertificateManagerVariables.getNati
veAPIVersion
). This is because the Novell Certificate Server Plug-ins for iManager (PKI) has a
dependency on the libstdc++-libc6.2-2.so.3 library.
To avoid getting this error, you must install the following RPMs on the iManager server:
For SLES 10
32-bit: compat (compat-2006.1.25-11.2)
64-bit: compat-32bit (compat-32bit-2006.1.25-11.2)
For SLES 11
32-bit: compat (compat-2009.1.19-2.1)
64-bit: compat-32bit (compat-32bit-2009.1.19-2.1)
4.45 Authentication Error with SLES 10 SP3
You might encounter the following error while authenticating iManager on a Server with SLES 10
SP3 (64-bit):
Unable to create AdminNamespace. java.lang.NoClassDefFoundError when
authenticating on SLES 10 SP3.
Work around: Install libstdc++33-32bit-3.3.3-7.8.1 before installing iManager 2.7.
5 Additional Readme Information
For information on iManager 2.7 issues following this release, see Novell iManger 2.x Readme
Addendum (http://www.novell.com/support/viewContent.do?externalId=7006099) in the Novell
Knowledge Base.

iManager 2.7.3 Field Patch (FTF) 4 Readme 19
novdocx (en) 16 April 2010
6 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. Please
refer to the Novell International Trade Services Web page (http://www.novell.com/info/exports/) for
more information on exporting Novell software. Novell assumes no responsibility for your failure to
obtain any necessary export approvals.
Copyright © 2010 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.
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/
company/legal/trademarks/tmlist.html).
All third-party trademarks are the property of their respective owners.