Cisco AnyConnect VPN Client Administrator Guide, Release 2.2
About This Guide
Downloads: This chapterpdf (PDF - 142.0KB) The complete bookPDF (PDF - 4.6MB) | Feedback

About This Guide

Table Of Contents

About This Guide

Document Objectives

Audience

Related Documentation

Document Organization

Document Conventions

Obtaining Documentation, Obtaining Support, and Security Guidelines

Notices

OpenSSL/Open SSL Project

License Issues

Trademarks and Copyrights Acknowledgements


About This Guide


OL-16159-01

This preface introduces the Cisco AnyConnect VPN Client Administrator Guide, Release 2.2, and includes the following sections:

Document Objectives

Audience

Related Documentation

Document Organization

Document Conventions

Obtaining Documentation, Obtaining Support, and Security Guidelines

Notices

Document Objectives

The purpose of this guide is to help you configure the Cisco AnyConnect VPN Client parameters on the security appliance. This guide does not cover every feature, but describes only the most common configuration scenarios.

You can configure and monitor the security appliance by using either the command-line interface or ASDM, a web-based GUI application. ASDM includes configuration wizards to guide you through some common configuration scenarios, and online Help for less common scenarios. For more information, see: http://www.cisco.com/univercd/cc/td/doc/product/netsec/secmgmt/asdm/index.htm

This guide applies to the Cisco ASA 5500 series security appliances (ASA 5505 and higher). Throughout this guide, the term "security appliance" applies generically to all supported models, unless specified otherwise. The PIX family of security appliances is not supported.

Audience

This guide is for network managers who perform any of the following tasks:

Manage network security

Install and configuresecurity appliances

Configure VPNs

Related Documentation

For more information, refer to the following documentation:

Cisco ASA 5500 Series Adaptive Security Appliance Getting Started Guide

Cisco ASA 5500 Series Release Notes

Cisco ASDM Release Notes

Cisco ASDM Online Help

Release Notes for Cisco AnyConnect VPN Client, Release 2.0

Cisco Security Appliance Command Reference

Cisco Security Appliance Logging Configuration and System Log Messages

Cisco Secure Desktop Configuration Guide for Cisco ASA 5500 Series Administrators

For Open Source License information for this product, please see the following link: http://www.cisco.com/en/US/docs/security/asa/asa80/license/opensrce.html#wp50053.

Document Organization

This guide includes the chapters and appendixes described in Table 1.

Table 1 Document Organization 

Chapter/Appendix
Definition

Chapter 1 "Introduction"

Provides a high-level overview of the Cisco Anyconnect VPN Client.

Chapter 2 "Configuring AnyConnect Features Using ASDM"

Describes how to use ASDM to configure the various features of the Cisco AnyConnect VPN Client on the security appliance.

Chapter 3 "Configuring AnyConnect Features Using CLI"

Describes how to use ASDM to configure the various features of the Cisco AnyConnect VPN Client on the security appliance.

Chapter 1 "Configuring and Using AnyConnect Client Operating Modes and User Profiles"

Describes how to configure and use AnyConnect client operating modes and XML users profiles.

Chapter 5 "Customizing and Localizing the AnyConnect Client and Installer"

Describes how to customize and localize the end-user interface of the Cisco AnyConnect VPN Client.

Chapter 6 "Monitoring and Maintaining the AnyConnect Client"

Describes how to monitor and maintain the Cisco AnyConnect VPN Client using the security appliance

"Sample AnyConnect Profile and XML Schema"

Provides a sample AnyConnect user XML profile and an XML schema that you can use to validate the user profiles you create.

"Using Microsoft Active Directory to Add the Security Appliance to the List of Internet Explorer Trusted Sites for Domain Users"

Describes in detail how an Active Directory Domain Administrator can push to remote users a group policy that adds the security appliance to the list of trusted sites in Internet Explorer.


Document Conventions

Command descriptions use these conventions:

Braces ({ }) indicate a required choice.

Square brackets ([ ]) indicate optional elements.

Vertical bars ( | ) separate alternative, mutually exclusive elements.

Right-pointing angle brackets (>) indicate a sequence in a path.

Boldface indicates commands and keywords that are entered literally as shown.

Italics indicate arguments for which you supply values.

Examples use these conventions:

Examples depict screen displays and the command line in screen font.

Information you need to enter in examples is shown in boldface screen font.

Variables for which you must supply a value are shown in italic screen font.


Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual.


Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Notices

The following notices pertain to this software license.

OpenSSL/Open SSL Project

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

This product includes software written by Tim Hudson (tjh@cryptsoft.com).

License Issues

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.

OpenSSL License:

Copyright © 1998-2007 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay License:

Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).

The implementation was written so as to conform with Netscapes SSL.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".

The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)".

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].

Trademarks and Copyrights Acknowledgements