Cisco Systems 3750E Configuring the Secure Http Client, Ip http timeout-policy idle seconds life

Chapter 9 Configuring Switch-Based Authentication

Configuring the Switch for Secure Socket Layer HTTP

	Command	Purpose
Step 11
	ip http timeout-policy idle seconds life	(Optional) Specify how long a connection to the HTTP server can remain
	seconds requests value	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.
Step 12
	end	Return to privileged EXEC mode.
Step 13
	show ip http server secure status	Display the status of the HTTP secure server to verify the configuration.
Step 14
	copy running-config startup-config	(Optional) Save your entries in the configuration file.

Use the no ip http server global configuration command to disable the standard HTTP server. Use the no ip http secure-serverglobal configuration command to disable the secure HTTP server. Use the no ip http secure-portand the no ip http secure-ciphersuiteglobal configuration commands to return to the default settings. Use the no ip http secure-client-authglobal configuration command to remove the requirement for client authentication.

To verify the secure HTTP connection by using a Web browser, enter https://URL, where the URL is the IP address or hostname of the server switch. If you configure a port other than the default port, you must also specify the port number after the URL. For example:

https://209.165.129:1026

or

https://host.domain.com:1026

Configuring the Secure HTTP Client

The standard HTTP client and secure HTTP client are always enabled. A certificate authority is required for secure HTTP client certification. This procedure assumes that you have previously configured a CA trustpoint on the switch. If a CA trustpoint is not configured and the remote HTTPS server requires client authentication, connections to the secure HTTP client fail.

Beginning in privileged EXEC mode, follow these steps to configure a secure HTTP client:

	Command	Purpose
Step 1
	configure terminal	Enter global configuration mode.
Step 2
	ip http client secure-trustpoint name	(Optional) Specify the CA trustpoint to be used if the remote HTTP server
		requests client authentication. Using this command assumes that you have
		already configured a CA trustpoint by using the previous procedure. The
		command is optional if client authentication is not needed or if a primary
		trustpoint has been configured.

Catalyst 3750-E and 3560-E Switch Software Configuration Guide

OL-9775-02 9-47