Version 6.2 65 February 2011
SIP User's Manual 3. Web-Based Management
3.3.1.5.2 Client Certificates
By default, Web servers using SSL provide one-way authentication. The client is certain
that the information provided by the Web server is authentic. When an organizational PKI is
used, two-way authentication may be desired: both client and server should be
authenticated using X.509 certificates. This is achieved by installing a client certificate on
the managing PC, and loading the same certificate (in base64-encoded X.509 format) to
the device's Trusted Root Certificate Store. The Trusted Root Certificate file should contain
both the certificate of the authorized user and the certificate of the CA.
Since X.509 certificates have an expiration date and time, the device must be configured to
use NTP (see ''Simple Network Time Protocol Support'' on page 315) to obtai
n the current
date and time. Without the correct date and time, client certificates cannot work.
¾ To enable two-way client certificates:
1. Set the parameter 'Secured Web Connection (HTTPS)' to 'HTTPS Only' (0) in
''Configuring Web Security Settings'' on page 69 to ensure yo
u have a method of
accessing the device in case the client certificate doesn’t work. Restore the previous
setting after testing the configuration.
2. Open the ‘Certificates Signing Request' page (see ''Server Certificate Replacement''
on page 62).
3. In the 'Certificates Files' group, click the Browse button corresponding to 'Send
"Trusted Root Certificate Store" file ...', navigate to the file, and then click Send File.
4. When the operation is complete, set the HTTPSRequireClientCertificate ini file
parameter to 1.
5. Save the configuration (see ''Saving Configuration'' on page 169), and then re
start the
device.
When a user connects to the secured Web server:
îš„ If the user has a client certificate from a CA that is listed in the Trusted Root Certificate
file, the connection is accepted and the user is prompted for the system password.
îš„ If both the CA certificate and the client certificate appear in the Trusted Root
Certificate file, the user is not prompted for a password (thus, providing a single-sign-
on experience - the authentication is performed using the X.509 digital signature).
 If the user doesn’t have a client certificate from a listed CA, or doesn’t have a client
certificate at all, the connection is rejected.
Notes:
• The process of installing a client certificate on your PC is beyond the
scope of this document. For more information, refer to your Web browser
or operating system documentation, and/or consult your security
administrator.
• The root certificate can also be loaded via ini file using the parameter
HTTPSRootFileName.
• You can enable Online Certificate Status Protocol (OCSP) on the device
to check whether a peer's certificate has been revoked by an OCSP
server. For further information, refer to the Product Reference Manual.
To Next Page
Loading...
Need help?
General
