8.5 Troubleshooting NURM

NOTE:Beginning with OES 24.4, OES User Rights Map (NURM) is deprecated and removed from OES.

8.5.1 Unable to Map eDirectory Users in NURM

User mapping fails if the organization unit (ou) name in NURM contains the following special characters:

\ % # / ; , < > ?

However, the following special characters in ou name will not result in any user mapping failure:

}{[] | _- "': !@$^&*()

8.5.2 Volumes are not Listed in the View Rights and Map Rights Pages

NURM uses CIFS to fetch the volume information. The volumes do not get listed in the View Rights and Map Rights pages under the following conditions:

  • When a user who is not universal password enabled accesses NURM, the volumes do not get listed under the View Rights and Map Rights pages. To resolve this issue, ensure to set the Universal Password Policy for the user who is accessing NURM. For more information on enabling Universal Password Policy, see CIFS and Universal Password in the OES CIFS for Linux Administration Guide.

  • When the CIFS user context is not configured for the eDirectory user who is accessing NURM. For more information, see Configuring a CIFS User Context in the OES CIFS for Linux Administration Guide.

  • When the user, who is accessing NURM, does not have adequate rights on /_admin/Manage_NSS/manage.cmd.

8.5.3 Active Directory User Names With Special Characters are Ignored

While creating a user in AD, if it contains any special characters (/\[]:;|=,+*?<>@"), it is replaced with an underscore (_) in the SAM account name after a warning; whereas, the user name continues to have the special character. For example, if you want to create a user named "tom*adm", the SAM account name will be "tom_adm", and the user name will be "tom*adm".

When you use IDM to synchronize the identity sources (eDirectory and Active Directory), IDM creates a user in eDirectory with the name "tom*adm". In this scenario, if you use NURM to map and apply rights, it ignores the identities with special characters.

8.5.4 View Rights Option Does Not Work in NURM When There are 200K Users

"Error: Error in Communication."

When you try to view the rights of 200,000+ users, NURM displays the error as mentioned above. This happens due to Java memory issues.

To increase the Java memory:

  1. Edit /etc/opt/novell/tomcat/conf/novell-tomcat.conf and update the JAVA_OPTS entry as follows:

    JAVA_OPTS="-Djava.library.path=/opt/novell/eDirectory/lib64:/var/opt/novell/tomcat/lib:/usr/lib64 -Xms1024m -Xmx2048m"

  2. Restart the OES instance of tomcat using the rcnovell-tomcat restart.