Accessing the C-Web Interface through Secure HTTP
Before you configure access to the C-Web interface through HTTPS, obtain a digital security certificate on the system.
See Chapter 21, Managing Security Digital Certificates.
To make the C-Web interface accessible to remote users through secure HTTP:
- From configuration mode, access the hierarchy level for web-management HTTPS.
[edit]user@host#edit system services web-management https
- Specify which TCP port is to receive incoming connection requests for the C-Web interface.
[edit system services web-management https]user@host#set port
port
The default port for HTTPS 443.
- Specify the interface to be used for Web browser connections to the C-Web interface.
[edit system services web-management https]user@host#set interface
interface
You can specify an interface for SRC installations on Solaris platforms as well as on C-series platforms. On a C-series platform, use eth0; you can use eth2 or eth3 if installed.
On C-series platforms, specifying an interface is important if your C-series platform has eth2 and eth3 interfaces and you want to restrict C-Web interface access to one or both of these interfaces.
- Specify the name of the certificate on the local system.
[edit system services web-management https]user@host#set local-certificate
local-certificate
- Configure logging for the C-Web interface.
See SRC-PE Monitoring and Troubleshooting Guide, Chapter 3, Configuring Logging for SRC Components with the CLI.
Users who have privileges to log in to the SRC CLI also have privileges to log in to the C-Web interface.