The most commonly encountered issues when connecting with the Cisco Secure Client can be fixed by altering your browser settings. If you are having problems please see the following notes:
In these notes the term "Security Gateway" refers to the Cisco device to which the Cisco Secure Client connects. Examples of Security Gateways include the Adaptive Security Appliance 5500 and Catalyst 6000.
The complete release notes for this product cover additional issues and are available from Cisco's website.
SSL uses certificates to identify peers in a connection. The Security Gateway has a certificate installed that is used to establish its identity. This certificate may be issued from a widely trusted source, such as Verisign or Thawte, that your computer is already configured to trust, or it may be a self-signed certificate that your computer will not trust automatically. This results in the Security warnings during connection establishment.
This section explains how to install a self-signed certificate as a trusted root certificate on a client in response to the browser alert windows.
In Response to Firefox "Certified by an Unknown Authority" WindowInstall the certificate as a trusted root certificate as follows:
Install the certificate as a trusted root certificate as follows:
Any browser that supports the Java plugin should work for Cisco Secure Client’s web launch. On Linux, the Java plugin is 64-bit only; this means that only 64-bit browsers are supported. Firefox support the Java plugin; however, Chrome is a 32-bit only browser and does not run Java. For this reason, Cisco Secure Client’s web launch functionality will not run in Chrome and will need to be downloaded manually.
By default, Firefox blocks execution of Java applets. In order to grant the necessary permissions to web sites running Cisco Secure Client’s web launch., we must enable Java applet's on Firefox Add-ons.
This will allow Cisco Secure Client Java applet to execute.