Users Guide

NOTE: You also have an option to view the certicate information and export the certicate that is being used in the
Base64–encoded format, which can be imported by other web services.
• Import certicate chain — Allows you to import the certicate chain (in PKCS#7 format) signed by a trusted CA. The
certicate can be in DER or Base64-encoded format.
• Import a PKCS12 Keystore — Allows you to import a PKCS#12 keystore that replaces the private key and certicate used in
Server Administrator web server. PKCS#12 is public keystore that contains a private key and the certicate for a web server.
Server Administrator uses the Java KeyStore (JKS) format to store the SSL certicates and its private key. Importing a PKCS#12
keystore to Server Administrator deletes the keystore entries, and imports a private key and certicate entries to the Server
Administrator JKS.
NOTE: An error message is displayed if you either select an invalid PKCS le or when you type an incorrect password.
SSL Server Certicates
Server Administrator Web server is congured to use the industry-standard SSL security protocol to transfer encrypted data over a
network. Built on an asymmetric encryption technology, SSL is widely accepted for providing authenticated and encrypted
communication between clients and servers to prevent eavesdropping across a network.
An SSL-enabled system can perform the following tasks:
• Authenticate itself to an SSL-enabled client
• Allow the two systems to establish an encrypted connection
The encryption process provides a high level of data protection. Server Administrator uses the most secure form of encryption
generally available for Internet browsers in North America.
Server Administrator Web server has a self-signed unique SSL digital certicate by default. You can replace the default SSL
certicate with a certicate signed by a well-known Certicate Authority (CA). A Certicate Authority is a business entity that is
recognized in the Information Technology industry for meeting high standards of reliable screening, identication, and other
important security criteria. Examples of CAs include Thawte and VeriSign. To initiate the process of obtaining a CA-signed certicate,
use the Server Administrator Web interface to generate a Certicate Signing Request (CSR) with your company’s information. Then,
submit the generated CSR to a CA such as VeriSign or Thawte. The CA can be a root CA or an intermediate CA. After you receive
the CA-signed SSL certicate, upload the certicate to Server Administrator.
For each Server Administrator to be trusted by the management station, the SSL certicate of that Server Administrator must be
placed in the certicate store of the management station. After the SSL certicate is installed on the management stations,
supported browsers can access Server Administrator without certicate warnings.
Server Administrator Web Server Action Tabs
The following are the action tabs that are displayed when you log in to manage the Server Administrator web server:
• Properties
• Shutdown
• Logs
• Alert Management
• Session Management
Upgrading web server
CAUTION: Factory reset is not possible after a web server update. For a factory reset, reinstall the Server Administrator.
You can upgrade the Apache Tomcat web server, whenever required, using the omwsupdateutility, without aecting the Server
Administrator functionality. The utility allows upgrade to a minor version of web server, but does not support upgrade to a major
version. For example, upgrade from version A.x to A.y is supported, but not A.x to B.x or B.y. Also, using the utility you can move the
version of the web server to an earlier version, provided it is a minor version. The utility is saved to the following default location
during web server installation:
• On systems running a Windows operating system: C:\Program Files\Dell\SysMgt\omsa\wsupdate
• On systems running a Linux operating system: /opt/dell/srvadmin/lib64/openmanage/wsupdate
32