Server Administrator provides security through role-based access control (RBAC),
authentication, and encryption for both the Web-based and command line
interfaces.
Role-Based Access Control
RBAC manages security by determining
the operations that can be executed by persons in particular roles. Each user is assigned one or
more roles, and each role is assigned one or more user privileges that are permitted
to users in that role. With RBAC, security administration corresponds closely to an organization's structure.
Server Administrator grants different access rights based on the user's
assigned group privileges.
Server Administrator grants read-only access to users logged in with User
privileges,
read and write
access to users logged in with Power User privileges, and read, write, and admin
access to users logged in with Admin privileges.
Access Type
User Privileges
Admin
Write
Read
User
X
Power User
X
X
Admin
X
X
X
Read access allows viewing of data reported by Server Administrator. Read
access does not allow changing or setting values on the managed system.
Write access allows values to be changed or set on the managed system.
Admin access allows shutdown of the managed system.
Authentication
The
Server Administrator authentication scheme ensures that the correct access types
are assigned to the correct user privileges. Additionally, when the command line
interface (CLI) is invoked, the Server Administrator authentication scheme
validates the context within which the current process is running. This authentication scheme
ensures that all Server Administrator functions, whether accessed through the
Server Administrator home page or CLI, are properly authenticated.
Microsoft� Windows� Authentication
For supported Microsoft Windows operating systems, Server Administrator
authentication is based on the operating system's user authentication system
using Windows NT� LAN Manager (NTLM) modules to authenticate.
This underlying authentication system allows Server Administrator security to be
incorporated in an overall security scheme for your network.
Red Hat Linux Authentication
For supported Red Hat Linux operating systems, Server Administrator
authentication is based on the Red Hat Linux Pluggable Authentication Modules (PAM) library. This
documented library of functions allows an administrator to determine how
individual applications authenticate users.
Novell� NetWare� Authentication
For supported Novell NetWare operating systems, Server Administrator
authentication is based on the Novell Directory Service (NDS) library. This documented library of functions
allows an administrator to determine how individual applications authenticate
users.
Encryption
Server Administrator is accessed over a secure HTTPS
connection using secure socket layer (SSL) technology to ensure and protect the
identity of the system being managed. Java Secure Socket Extension (JSSE)
is used by supported Microsoft Windows, Red Hat Linux, and certain Novell
NetWare operating systems to
protect the user credentials and other sensitive data that is transmitted over
the socket connection when a user accesses the Server Administrator home page. Supported Novell NetWare
operating systems use operating system native Java SSL and Secure Authentication
Services (SAS)-NetWare International Cryptographic Infrastructure (NICI).
You must properly assign user privileges to all Server Administrator users
before installing Server Administrator in order to ensure critical system component security.
NOTICE: You must assign a password to
every user account that can access Server Administrator in order to protect
access to your critical system components.
NOTICE: You should disable guest accounts
for supported Microsoft Windows operating systems in order to protect
access to your critical system components. See "Disabling Guest
and Anonymous Accounts"
for instructions.
Creating Server Administrator Users for Supported Windows Operating
Systems
NOTE: You must be logged in with Admin
privileges to
perform these procedures.
Creating Users and Assigning User Privileges in Supported Windows 2000 Operating Systems
NOTE: For questions about creating users and
assigning user group privileges or for more detailed instructions, see
your operating system documentation.
Right-click My Computer and point to Manage.
In the console tree, expand Local Users and Groups and click Users.
Click Action, and then click New User.
Type the appropriate information in the dialog box, select or clear the
appropriate check boxes, and click Create.
NOTICE: You must assign a password to
every user account that can access Server Administrator in order to protect
access to your critical system components.
In the console tree, under Local Users and Groups, click Groups.
Click the group to which you want to add the new user: Users, Power
Users, or Administrators.
Click Action, and then click Properties.
Click Add.
Click the name of the user you want to add and click Add.
Click
Check Names to validate the user name that you are adding.
Click OK.
New users can log into Server Administrator with the user
privileges for their assigned group.
Adding Users to a Domain in Supported Windows 2000
Operating Systems
NOTE: For questions about creating users and
assigning user group privileges or for more detailed instructions, see
your operating system documentation.
NOTE: You must have Active Directory
installed on your system to perform the following procedures.
Click the Start button and point to Programs�>
Administrative Tools�> Active Directory Users and Computers.
In the console tree, right-click Users or right-click the container
in which you want to add the new user and point to New�> User.
Type the appropriate user name information in the dialog box and click Next.
Type the appropriate password information in the dialog box and click Next.
NOTICE: You must assign a password to
every user account that can access Server Administrator in order to protect
access to your critical system components.
Click Next, and then click Finish.
Double-click the icon representing the user you just created.
Click the Member of tab.
Click Add.
Select the appropriate group and click Add.
Click OK, and then click OK again.
New users can log into Server Administrator with the user
privileges for their assigned group and domain.
Creating Users and Assigning User Privileges in Supported
Windows NT
Operating Systems
NOTE: For questions about creating users and
assigning user group privileges or for more detailed instructions, see
your operating system documentation.
Click the Start button and point to Programs�>
Administrative Tools�> User Manager.
Click User, and then click New User.
Type the appropriate information in the dialog box, select or clear the
appropriate check boxes, and click Add.
NOTICE: You must assign a password to
every user account that can access Server Administrator in order to protect
access to your critical system components.
In the console tree under Local Users and Groups, click Groups.
Click the group to which you want to add the new user: Users, Power
Users, or Administrators.
Click OK.
Click Add.
New users can log into Server Administrator with the user
privileges for their assigned group.
Adding Users to a Domain in Supported
Windows NT
Operating Systems
NOTE: For questions about creating users and
assigning user group privileges or for more detailed instructions, see
your operating system documentation.
Click the Start button and point to Programs�>
Administrative Tools�> User Manager for Domains.
Click User, and then click New User.
Type the appropriate information in the dialog box, select or clear the
appropriate check boxes, and click Add.
NOTICE: You must assign a password to
every user account that can access Server Administrator in order to protect
access to your critical system components.
In the console tree, under Local Users and Groups, click Groups.
Click the group to which you want to add the new user: Users, Power
Users, or Administrators.
Click OK.
Click Add.
New users can log into Server Administrator with the user
privileges for their assigned group and domain.
Creating Server Administrator Users for Supported Red Hat Linux Operating
Systems
Admin access privileges are assigned to the user logged in as root. To
create users with User and Power User privileges, perform the following steps.
NOTE: You must have the linuxconf utility
installed on your system to
perform these procedures.
NOTE: You must be logged in as root to
perform these procedures.
NOTE: For questions about creating users and
assigning user group privileges or for more detailed instructions, see
your operating system documentation.
Creating Users With User Privileges
Start a system running X Windows.
Type linuxconf and press <Enter>.
Under the Config tab, expand User accounts and then
expand Normal.
Click User accounts.
The User accounts window appears.
Click Add.
Complete the required fields under the User account creation tab
and add the new user to the users group.
NOTICE: You must assign a password to
every user account that can access Server Administrator in order to protect
access to your critical system components.
Click OK.
New users can now log into Server Administrator with User
privileges.
Creating Users With Power User Privileges
Start a system running X Windows.
Type linuxconf and press <Enter>.
Under the Config tab, expand User accounts and then
expand Normal.
Click User accounts.
The User accounts window appears.
Click Add.
Complete the required fields under the User account creation tab
and add the new user to the root group.
NOTICE: You must assign a password to
every user account that can access Server Administrator in order to protect
access to your critical system components.
Click OK.
New users can now log into Server Administrator with Power User
privileges.
Creating Server Administrator Users for Supported NetWare Operating Systems
NOTE: For questions about creating users and
assigning user group privileges or for more detailed instructions, see
your operating system documentation.
Creating Users With User Privileges
Log in with Admin privileges.
Right-click the container in which a user account
is to be created.
Click NEW and select USER.
Complete the required fields and click OK.
NOTICE: You must assign a password to
every user account that can access Server Administrator in order to protect
access to your critical system components.
An icon labeled with the new user name appears in the current
container.
Right-click the icon labeled with the new user name and click Trustees
of this Object.
Select username.contextName and click Assigned Rights.
By default there are three entries in the Assigned Rights category: Login
Script, Print Job Configuration, and [All Attribute Rights].
Select Login Script, and enable the Read and Add
Self fields.
Select Print Job Configuration, and enable the Read and Add
Self fields.
Select [All Attribute Rights], and enable the Read and Add
Self fields.
New users can now log into Server Administrator with User privileges.
Creating Users With Power User Privileges
Log in with Admin privileges.
Right-click the container in which a user account
is to be created.
Click NEW and select USER.
Complete the required fields and click OK.
NOTICE: You must assign a password to
every user account that can access Server Administrator in order to protect
access to your critical system components.
An icon labeled with the new user name appears in the current
container.
Right-click the icon labeled with the new user name and click Properties.
Click NDS Rights.
Select username.contextName and click Assigned Rights.
Click Add Property.
Select ACL and click OK.
Enable the Read and Write fields by putting a check mark in the
check box.
Click OK.
New users can now log into Server Administrator with Power User privileges.
Creating Users With Admin Privileges
Log in with Admin privileges.
Right-click the container in which a user account
is to be created.
Click NEW and point to USER.
Complete the required fields and click OK.
NOTICE: You must assign a password to
every user account that can access Server Administrator in order to protect
access to your critical system components.
An icon labeled with the new user name appears in the current
container.
Right-click the icon labeled with the new user name and click Trustees
of this Object.
Select username.contextName and click Assigned Rights.
By default there are three entries in the Assigned Rights category: Login
Script, Print Job Configuration, and [All Attribute Rights].
Select Login Script, and enable the Read, Write, Add
Self, and Supervisor fields.
Select Print Job Configuration, and enable the Read, Write,
Add
Self, and Supervisor fields.
Select [All Attribute Rights], and enable the Read, Write,
Add
Self, and Supervisor fields.
New users can now log into Server Administrator with Admin
privileges.
Server Administrator
supports the Simple Network Management Protocol (SNMP) systems management standard
on all supported operating systems. In most cases, SNMP is installed as part of your operating system
installation. An installed supported systems management protocol
standard, such as SNMP, is required
before installing Server Administrator. See "Installation
Requirements" for more information.
You can configure the
SNMP agent to change the community name, enable Set operations,
and send traps to a management station. To configure your SNMP agent for proper
interaction with management applications such as the Dell OpenManage IT
Assistant and Array Manager, perform the procedures described in the following
sections.
The following procedures provide step-by-step instructions for configuring
the SNMP agent for each supported
operating system:
Server Administrator uses the SNMP services provided by the Windows SNMP agent.
You can configure the
SNMP agent to change the community name, enable Set operations,
and send traps to a management station. To configure your SNMP agent for proper
interaction with management applications such as IT
Assistant and Array Manager, perform the procedures described in the following
sections.
NOTE: See your operating system
documentation for additional details on SNMP configuration.
Changing the SNMP
Community Name
Configuring the SNMP community names determines which systems are
able to manage your system through SNMP. The SNMP community name used by
management applications must match an SNMP community name configured on the Server Administrator
system so that the management applications can retrieve
management information from Server Administrator.
Changing the SNMP Community Name on
Systems Running Supported Windows NT Operating Systems
Click the Start button and point to Settings�> Control
Panel.
The Control Panel window appears.
Double-click the Network icon for
networking configuration.
The Network window appears.
Click the Services tab in
the Network window.
Click SNMP Service in the menu of services and then click Properties.
The Microsoft SNMP Properties window appears.
Click the Security tab to add or edit a community name.
To add a community name, click Add.
The Service Configuration window appears.
Type the community names of the systems that are
able to manage your system (the default is public) in the Community Names text
box and click Add.
The Microsoft SNMP Properties window appears.
To change a community name, select a community name in the Accepted Community Names list and
click Edit.
The Service Configuration window appears.
Make all necessary edits
to the community name of the system that is able to manage your system in the
Community Names text box, and click OK.
Click OK in the Microsoft SNMP Properties
window to save the changes.
Restart the SNMP service from the services control
panel to make the configuration changes active.
Changing the SNMP Community Name
on Systems Running Supported Windows 2000 Operating Systems
Click the Start button and
point to Settings�> Control Panel.
The Control Panel window appears.
Double-click the Administrative Tools icon.
The Administrative Tools window appears.
Double-click the Computer Management icon.
The Computer Management window appears.
Expand the Computer Management icon in the window, if necessary.
Expand
the Services and Applications icon and click Services.
Scroll down the list of
services until you find SNMP Service, right-click SNMP Service, and click Properties.
The SNMP Service Properties window appears.
Click the Security tab
to add or edit a community name.
To add a community name, click Add.
The SNMP Service Configuration window appears.
Type the community names of the systems that are
able to manage your system (the default is public) in the Community Names text
box and click Add.
The SNMP Service Properties window appears.
To change a community name, select a community name in the Accepted Community Names list and
click Edit.
The SNMP Service Configuration window appears.
Make all necessary edits
to the community name of the system that is able to manage your system in the
Community Names text box and click OK.
The SNMP Service Properties
window appears.
Click OK to save the changes.
Restart the SNMP service from the services control panel to make the configuration changes active.
Enabling SNMP
Set Operations
SNMP Set operations must be enabled on the Server Administrator system in
order to change Server Administrator attributes using IT Assistant.
Enabling Set
Operations on Systems Running Supported Windows NT Operating Systems
Click the Start button and point to Settings�> Control
Panel.
The Control Panel window appears.
Double-click the Network icon for
networking configuration.
The Network window appears.
Click the Services tab in
the Network window.
Click SNMP Service in the menu of services and then click Properties.
The Microsoft SNMP Properties window appears.
Click the Security tab to change the access rights for a
community.
Select a community name in the Accepted Community Names list and
click Edit.
The Service Configuration window appears.
Set the Community Rights
to READ WRITE or READ CREATE, and click OK.
The Microsoft SNMP Properties window
appears.
Click OK to save the changes.
Restart the SNMP service from the services control panel to make the configuration changes active.
Enabling Set
Operations on Systems Running Supported Windows 2000 Operating Systems
Click the Start button and
point to Settings�> Control Panel.
The Control Panel window appears.
Double-click the Administrative Tools icon.
The Administrative Tools window appears.
Double-click the Computer Management icon.
The Computer Management window appears.
Expand the Computer Management icon in the window, if necessary.
Expand
the Services and Applications icon and click Services.
Scroll down the list of
services until you find SNMP Service, right-click SNMP Service, and click Properties.
The SNMP Service Properties window appears.
Click the Security tab to change the access
rights for a community.
Select a community name in the Accepted Community Names
list and click Edit.
The SNMP Service Configuration window appears.
Set the
Community Rights to READ WRITE or READ CREATE, and click OK.
The SNMP Service
Properties window appears.
Click OK to save the changes.
Restart the SNMP
service from the services control panel to make the configuration changes
active.
Configuring Your System to Send SNMP Traps to a Management Station
Server Administrator
generates SNMP traps in response to changes in the status of
sensors and other monitored parameters. You must configure one or more trap destinations
on the Server Administrator system for SNMP traps to be sent to a management
station.
Configuring a System Running Supported Windows NT Operating
Systems to Send SNMP Traps to a Management Station
Click the Start
button and point to Settings�> Control Panel.
The Control Panel window
appears.
Double-click the Network icon for networking configuration.
The Network
window appears.
Click the Services tab in the Network window.
Click SNMP Service
in the menu of services and then click Properties.
The Microsoft SNMP Properties
window appears.
Click the Traps tab to add a community for traps or to add a
trap destination for a trap community.
To add a community for traps, type the
community name in the Community Name box and click Add located next to the
Community Name box.
To add a trap destination for a trap community, select the community name from
the Community Name drop-down box and click Add located under the
Trap
Destinations box.
The Service Configuration window appears.
Type in the trap
destination and click Add.
The Microsoft SNMP Properties window appears.
Click OK to save the changes.
Restart the SNMP service from the services control panel
to make the configuration changes active.
Configuring a System Running Supported Windows 2000 Operating
Systems to Send SNMP Traps to a Management Station
Click the Start button and
point to Settings�> Control Panel.
The Control Panel window appears.
Double-click the Administrative Tools icon.
The Administrative Tools window appears.
Double-click the Computer Management icon.
The Computer Management window appears.
Expand the Computer Management icon in the window, if necessary.
Expand
the Services and Applications icon and click Services.
Scroll down the list of
services until you find SNMP Service, right-click SNMP Service, and click Properties.
The SNMP Service Properties window appears.
Click the Traps tab to
add a community for traps or to add a trap destination for a trap community.
To
add a community for traps, type the community name in the Community Name box and
click Add to list, which is located next to the Community Name box.
To add a trap destination
for a trap community, select the community name from the Community Name
drop-down box and click Add under the Trap Destinations box.
The SNMP
Service Configuration window appears.
Type in the trap destination and click
Add.
The SNMP Service Properties window appears.
Click OK to save the changes.
Restart the SNMP service from the services control panel to make the
configuration changes active.
Server Administrator uses the SNMP services provided by the ucd-snmp SNMP agent.
You can configure the
SNMP agent to change the community name, enable Set operations,
and send traps to a management station. To configure your SNMP agent for proper
interaction with management applications such as IT
Assistant and Array Manager, perform the procedures described in the following
sections.
NOTE:
See your operating system
documentation for additional details on SNMP configuration.
Changing the SNMP
Community Name
Configuring the SNMP community names determines which systems are
able to manage your system through SNMP. The SNMP community name used by
management applications must match an SNMP community name configured on the Server Administrator
system so that the management applications can retrieve
management information from Server Administrator.
To change the SNMP community name used for retrieving management information
from a system running Server Administrator, edit the SNMP agent configuration file, /etc/snmp/snmpd.conf,
and perform the following steps:
Find the line that reads:
com2sec publicsec default public
or
com2sec notConfigUser default public
Edit this line, replacing public with the new SNMP
community name. When edited, the new line should read:
com2sec publicsec default community_name
or
com2sec notConfigUser default community_name
To enable SNMP configuration changes, restart the SNMP agent by
typing:
service snmpd restart
Enabling SNMP
Set Operations
SNMP Set operations must be enabled on the system running Server Administrator in
order to change Server Administrator attributes using IT Assistant.
To enable SNMP Set operations on the system running Server Administrator, edit the
SNMP agent configuration file, /etc/snmp/snmpd.conf, and perform the
following steps:
Find the line that reads:
access publicgroup "" any noauth exact all none none
or
access notConfigGroup "" any noauth exact all none none
Edit this line, replacing the first none with all. When edited, the new
line should read:
access publicgroup "" any noauth exact all all none
or
access notConfigGroup "" any noauth exact all all none
To enable SNMP configuration changes, restart the SNMP agent by
typing:
service snmpd restart
Configuring Your System to Send Traps to a Management Station
Server Administrator generates SNMP traps in response to changes in the
status of sensors and other monitored parameters. One or more trap
destinations must be configured on the system running Server Administrator for SNMP
traps to be sent to a management station.
To configure your system running Server Administrator to send traps to a
management station, edit the SNMP agent configuration file, /etc/snmp/snmpd.conf,
and perform the following steps:
Add the following line to the file:
trapsink IP_addresscommunity_name
where IP_address is the IP address of the management station and
community_name is the
SNMP community name
To enable SNMP configuration changes, restart the SNMP agent by
typing:
This section explains how to configure the SNMP agent to change the community name, enable Set
operations, and send traps to a management station.
Server Administrator uses the SNMP services provided by the NetWare SNMP agent.
You can configure the
SNMP agent to change the community name, enable Set
operations, and send traps to a management station. To configure your SNMP agent
for proper interaction with management station applications such as IT Assistant
and Array Manager, perform the following
tasks.
NOTE: See your operating system
documentation for additional details on SNMP configuration.
Changing the SNMP
Community Name
The SNMP community name used by management applications must match an SNMP
community name configured on the system running Server Administrator so that the
management station applications can retrieve management information from Server
Administrator.
To change the SNMP community name used for retrieving management information
from a Server Administrator system, perform the following steps:
At the NetWare command line console, type load inetcfg and press
<Enter>.
The Internetworking Configuration menu appears.
Select the Manage Configuration menu item.
The Manage Configuration menu appears.
Select the Configure SNMP Parameters menu item.
The SNMP Parameters menu appears.
Select the Monitor State menu item to configure monitor community
handling.
The Monitor Community Handling menu choices are Any Community May
Read, Leave as Default Setting, No Community May Read, and Specified
Community May Read.
NOTE: Press <F1> for more information
about the Monitor State menu item. Press <Esc> to clear the
help window.
Press <Esc> to exit the SNMP Parameters menu.
A message box appears, prompting you to save changes.
Select Yes.
The Manage Configuration menu appears.
Press <Esc> to exit the Manage Configuration menu.
The Internetworking Configuration menu appears.
Select the Reinitialize System menu item to make the configuration
changes active.
Enabling SNMP
Set Operations
SNMP Set operations must be enabled on the system running Server Administrator in
order to change Server Administrator attributes using a management station
application.
To enable SNMP Set operations on the system running Server Administrator, perform the following
steps:
At the NetWare command line console, type load inetcfg and press <Enter>.
The Internetworking Configuration menu appears.
Select the Manage Configuration menu item.
The Manage Configuration menu appears.
Select the Configure SNMP Parameters menu item.
The SNMP Parameters menu appears.
Select the Control State menu item to configure control community handling.
The Control Community Handling menu choices are Any Community May
Write, Leave
as Default Setting, No Community May Write, and Specified Community May
Write.
NOTE: Press <F1> for more information about the
Control State menu
item. Press <Esc> to clear the help window.
Press <Esc> to exit the SNMP Parameters menu.
A message box appears, prompting you to save changes.
Select Yes.
The Manage Configuration menu appears.
Press <Esc> to exit the Manage Configuration menu.
The Internetworking Configuration menu appears.
Select the Reinitialize System menu item to make the configuration changes
active.
Configuring Your System to Send SNMP Traps to a Management Station
Server Administrator generates SNMP traps in response to changes in the status of
sensors and other monitored parameters. One or more trap destinations must be
configured on the system running Server Administrator for SNMP traps to be sent to a management
station.
To configure a system running Server Administrator to send SNMP traps to a management
station, perform the following steps:
At the NetWare command line console, type load inetcfg and press <Enter>.
The Internetworking Configuration menu appears.
Select the Manage Configuration menu item.
The Manage Configuration menu appears.
Select the Configure SNMP Parameters menu item.
The SNMP Parameters menu appears.
Select the Trap State menu item to configure trap community handling.
The Trap Handling menu choices are Do Not Send Traps, Leave as Default
Setting,
and Send Traps With Specified Community.
NOTE: Press <F1> for more information about the Trap State
menu
item. Press <Esc> to clear the help window.
Press <Esc> to exit the SNMP Parameters menu.
A message box appears, prompting you to save changes.
Select Yes.
The Manage Configuration menu appears.
Press <Esc> to exit the Manage Configuration menu.
The Internetworking Configuration menu appears.
Select the Protocols menu item.
The Protocol Configuration menu appears.
Select the TCP/IP menu item.
The TCP/IP Protocol Configuration menu appears.
Select one of the following SNMP Manager Table menu items:
Press <Ins> to add SNMP trap destinations.
Press <Enter> to modify SNMP trap destinations.
Press <Del> to delete SNMP trap destinations.
NOTE: Press <F1> for more information about the SNMP Manager Table
menu
item. Press <Esc> to clear the help window.
Press <Esc> to exit the SNMP Manager Table menu.
A message box appears, prompting you to update the database.
Select Yes.
The TCP/IP Protocol Configuration menu appears.
Press <Esc> twice to exit the TCP/IP Protocol Configuration menu.
The Internetworking Configuration menu appears.
Restart your system to make the configuration changes active.
Web certificates are necessary to ensure the identity of a remote system and
to ensure that information exchanged with the remote system cannot be viewed or
changed by others.
This section explains the administrative prerequisites for ensuring your
ability to generate a new X.509
certificate, reuse an existing X.509 certificate, or import a root certificate
or certificate chain from Certification Authority (CA) on each supported operating system.
The X.509 certificate management is provided through the Server Administrator
home page for the following operating systems. The operating systems do not
have any certificate
management prerequisites.
Microsoft Windows NT Server 4.0 (Service Pack 5 or later)
Microsoft Windows 2000 Server Family (includes Windows 2000 Server,
Windows 2000 Advanced Server, and Windows Small Business Server
[SBS] 2000)
Red Hat Linux version 7.1 or later
Novell NetWare version 6.0 or later
Prerequisites for Systems Running NetWare Version 5.1
The X.509 certificate management for systems running NetWare version 5.1 (Service Pack
3 or
later) requires that the
following procedures be performed before installing Server Administrator:
At the NetWare command line console, type load nwconfig and press
<Enter>.
Select Product Options.
Select View/Configure/Remove Installed options.
Verify that PKIS (Novell Public Key Infrastructure Services) is installed.
Verify that SAS (Secure Authentication Services) is installed.
Verify that NICI (NetWare International Cryptographic Infrastructure) is installed.
NOTE: PKIS, SAS, and NICI are installed by default. If any of these products
are not currently installed, you must install the product from your Novell
NetWare 5.1 operating system CD. After installation, you must reapply the correct support patch.
After installing Server Administrator, go to "Web Server and Security Setup" to complete the X.509 certificate management
procedures.
