7-46
Cisco Catalyst Switch Module 3110 and 3012 for IBM BladeCenter Software Configuration Guide
OL-12189-01
Chapter 7 Configuring Switch-Based Authentication
Configuring the Switch for Secure Socket Layer HTTP
server. After you have configured the server, you can configure options (path, access list to apply,
maximum number of connections, or timeout policy) that apply to both standard and secure HTTP
servers.
Beginning in privileged EXEC mode, follow these steps to configure a secure HTTP server:
Command Purpose
Step 1
show ip http server status (Optional) Display the status of the HTTP server to determine if the secure
HTTP server feature is supported in the software. You should see one of
these lines in the output:
HTTP secure server capability: Present
or
HTTP secure server capability: Not present
Step 2
configure terminal Enter global configuration mode.
Step 3
ip http secure-server Enable the HTTPS server if it has been disabled. The HTTPS server is
enabled by default.
Step 4
ip http secure-port port-number (Optional) Specify the port number to be used for the HTTPS server. The
default port number is 443. Valid options are 443 or any number in the
range 1025 to 65535.
Step 5
ip http secure-ciphersuite
{[3des-ede-cbc-sha] [rc4-128-md5]
[rc4-128-sha] [des-cbc-sha]}
(Optional) Specify the CipherSuites (encryption algorithms) to be used
for encryption over the HTTPS connection. If you do not have a reason to
specify a particularly CipherSuite, you should allow the server and client
to negotiate a CipherSuite that they both support. This is the default.
Step 6
ip http secure-client-auth (Optional) Configure the HTTP server to request an X.509v3 certificate
from the client for authentication during the connection process. The
default is for the client to request a certificate from the server, but the
server does not attempt to authenticate the client.
Step 7
ip http secure-trustpoint name Specify the CA trustpoint to use to get an X.509v3 security certificate and
to authenticate the client certificate connection.
Note Use of this command assumes you have already configured a CA
trustpoint according to the previous procedure.
Step 8
ip http path path-name (Optional) Set a base HTTP path for HTML files. The path specifies the
location of the HTTP server files on the local system (usually located in
system flash memory).
Step 9
ip http access-class access-list-number (Optional) Specify an access list to use to allow access to the HTTP server.
Step 10
ip http max-connections value (Optional) Set the maximum number of concurrent connections that are
allowed to the HTTP server. The range is 1 to 16; the default value is 5.
Step 11
ip http timeout-policy idle seconds life
seconds requests value
(Optional) Specify how long a connection to the HTTP server can remain
open under the defined circumstances:
• idle—the maximum time period when no data is received or response
data cannot be sent. The range is 1 to 600 seconds. The default is
180 seconds (3 minutes).
• life—the maximum time period from the time that the connection is
established. The range is 1 to 86400 seconds (24 hours). The default
is 180 seconds.
• requests—the maximum number of requests processed on a
persistent connection. The maximum value is 86400. The default is 1.
