Configuring The Secure Http Server - Cisco Catalyst 2360 Software Configuration Manual

Configuring the Switch for Secure Socket Layer HTTP
Command
Step 4
crypto key generate rsa
Step 5 crypto ca trustpoint name
Step 6 enrollment url url
Step 7
enrollment http-proxy host-name
port-number
Step 8
crl query url
Step 9
primary
Step 10 exit
Step 11 crypto ca authentication name
Step 12 crypto ca enroll name
Step 13 end
Step 14 show crypto ca trustpoints
Step 15
copy running-config startup-config
Use the no crypto ca trustpoint name global configuration command to delete all identity information
and certificates associated with the CA.

Configuring the Secure HTTP Server

If you are using a certificate authority for certification, you should use the previous procedure to
configure the CA trustpoint on the switch before enabling the HTTP server. If you have not configured
a CA trustpoint, a self-signed certificate is generated the first time that you enable the secure 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
Step 1 show ip http server status
Step 2 configure terminal
Catalyst 2360 Switch Software Configuration Guide
7-40
Purpose
(Optional) Generate an RSA key pair. RSA key pairs are required before
you can obtain a certificate for the switch. RSA key pairs are generated
automatically. You can use this command to regenerate the keys, if
needed.
Specify a local configuration name for the CA trustpoint and enter CA
trustpoint configuration mode.
Specify the URL to which the switch should send certificate requests.
(Optional) Configure the switch to obtain certificates from the CA
through an HTTP proxy server.
Configure the switch to request a certificate revocation list (CRL) to
ensure that the certificate of the peer has not been revoked.
(Optional) Specify that the trustpoint should be used as the primary
(default) trustpoint for CA requests.
Exit CA trustpoint configuration mode and return to global configuration
mode.
Authenticate the CA by getting the public key of the CA. Use the same
name used in Step 5.
Obtain the certificate from the specified CA trustpoint. This command
requests a signed certificate for each RSA key pair.
Return to privileged EXEC mode.
Verify the configuration.
(Optional) Save your entries in the configuration file.
Purpose
(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
Enter global configuration mode.
Chapter 7 Configuring Switch-Based Authentication
OL-19808-01