How to setup LUM on SLED 10.
This document (3994289) is provided subject to the disclaimer at the end of this document.
Novell Linux User Management (LUM) lets administrators configure Linux workstations and servers on the network so users can log in to them using user login information stored in Novell eDirectory instead of using user login information stored on each computer.
Step-by-Step instructions on how to setup LUM on SLED 10.0
Important Note: Currently a bug has been found with LUM on SLED 10.0. It will affect whether your CD-ROM or Plug-n-Play devices are detected and work. Novell Technical Suppport is working diligently to resolve this issue.
- The following rpm versions or newer are required for LUM athentication.
- Determine which of the needed modules are already installed on the workstation.
- The version numbers above may be different than the ones listed on your workstation.
- Usage: rpm -q
- #rpm -q novell-lum novell-NLDAPbase-dyn novell-NLDAPsdk-dyn
package novell-lum is not installed
package novell-NLDAP is not installed
- Install the rpm modules currently not installed on the workstation.
- Usage: yast -i
- # yast -i novell-lum# yast -i novell-NLDAPbase-dyn# yast -i novell-NLDAPsdk-dyn
- Redirect Linux authentication to eDirectory using LUM.
- Configure LUM to authenticate to a secure eDirectory LDAP server using namconfig.
- Usage: namconfig add -a
-p -r -w -S :389 -l 636 -R backup_server1:389,backup_server2:389
- Note: You can leave off the -p and wait for the password prompt if desired.
uid=603(joelum) gid=602(lumgroup) groups=602(lumgroup)
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:3994289
- Creation Date:15-MAR-07
- Modified Date:26-APR-12
- SUSESUSE Linux Enterprise Desktop
Did this document solve your problem? Provide Feedback