client certificates must therefore also be specified as a CA certificate on the virtual SSL
server.
In addition, the virtual SSL server checks if the client certificate should be revoked, by
comparing the serial number of the presented client certificate with entries in the certificate
revocation list.
The following steps demonstrate how to configure a virtual SSL server to require client
certificates for authentication purposes.
1. Display information about current virtual SSL servers.
This command displays information about all virtual SSL servers on the VPN
Gateway, including installed certificate. Based on the information displayed, decide
which virtual SSL server to configure for client authentication.
>> Main#
cfg/cur ssl
2. Configure the chosen virtual SSL server to require client certificates.
The client must send its client certificate to the virtual SSL server during the SSL
handshake. If the client does not have a certificate, the client will respond with a
NoCertificateAlert message. At that point, the session will be terminated.
>> SSL#
server 1
>> Server 1#
ssl
>> SSL Settings#
verify
Current value: none
Certificate verification (none/optional/require):
require
3. Specify which CA certificates to use for client authentication.
Specify which CA certificates you want the virtual SSL server to use for
authenticating client certificates. Only those client certificates that are issued by a
certificate authority whose CA certificate you specify, will be accepted. Note that
the CA certificates you specify by index number must be available on the VPN
Gateway itself.
To authenticate client certificates issued within your own organization, the CA
certificate used for generating the issued client certificates must be specified as a
CA certificate.
>> SSL Settings#
cacerts
Current value:
""
Enter certificate numbers (separated by comma):
<CA certificates
by index number>
Certificates and Client Authentication
102 User Guide
April 2013
Comments? infodev@avaya.com
Summary of Contents for 3050-VM
Page 1: ...User Guide Avaya VPN Gateway Release 9 0 NN46120 104 Issue 04 04 April 2013 ...
Page 4: ...4 User Guide April 2013 Comments infodev avaya com ...
Page 12: ...12 User Guide April 2013 ...
Page 20: ...New in this release 20 User Guide April 2013 Comments infodev avaya com ...
Page 30: ...Introducing the VPN Gateway 30 User Guide April 2013 Comments infodev avaya com ...
Page 36: ...Introducing the ASA 310 FIPS 36 User Guide April 2013 Comments infodev avaya com ...
Page 74: ...Upgrading the AVG Software 74 User Guide April 2013 Comments infodev avaya com ...
Page 86: ...Managing Users and Groups 86 User Guide April 2013 Comments infodev avaya com ...
Page 130: ...The Command Line Interface 130 User Guide April 2013 Comments infodev avaya com ...
Page 162: ...Supported Ciphers 162 User Guide April 2013 Comments infodev avaya com ...
Page 212: ...Syslog Messages 212 User Guide April 2013 Comments infodev avaya com ...
Page 242: ...Definition of Key Codes 242 User Guide April 2013 Comments infodev avaya com ...
Page 259: ...Creating a Port Forwarder Authenticator User Guide April 2013 259 ...
Page 266: ...Using the Port Forwarder API 266 User Guide April 2013 Comments infodev avaya com ...
Page 274: ...X 509 274 User Guide April 2013 Comments infodev avaya com ...