-
This documentation has been moved
-
Overview: Secure Connectivity
-
Internet Key Exchange for IPsec VPNs
-
Configuring Internet Key Exchange for IPsec VPNs
-
Call Admission Control for IKE
-
Certificate to ISAKMP Profile Mapping
-
Encrypted Preshared Key
-
Fragmentation of IKE Packets
-
IKE Responder-Only Mode
-
Distinguished Name Based Crypto Maps
-
IPsec and Quality of Service
-
VRF-Aware IPsec
-
IKE: Initiate Aggressive Mode (12.2(8)T FM)
-
Configuring Internet Key Exchange Version 2 (IKEv2)
-
-
Security for VPNs with IPsec
-
Configuring Security for VPNs with IPsec
-
IPsec Virtual Tunnel Interface
-
L2TP-IPsec Support for NAT and PAT Windows Clients
-
SafeNet IPsec VPN Client Support
-
Ability to Disable Extended Authentication for Static IPsec Peers
-
Sharing IPsec with Tunnel Protection
-
Crypto Conditional Debug Support
-
VPN Acceleration Module (VAM)
-
Option to Disable Hardware Crypto Engine Failover to Software Crypto Engine
-
- VPN Availability
-
IPsec Data Plane
-
IPsec Anti-Replay Window: Expanding and Disabling
-
Pre-Fragmentation for IPsec VPNs
-
Invalid Security Parameter Index Recovery
-
IPsec Dead Peer Detection Periodic Message Option
-
IPsec NAT Transparency
-
DF Bit Override Functionality with IPsec Tunnels
-
Crypto Access Check on Clear-Text Packets
-
IPsec Security Association Idle Timers
-
Low Latency Queueing (LLQ) for IPsec Encryption Engines
-
- IPsec Management
-
Public Key Infrastructure (PKI)
-
Implementing and Managing PKI Features Roadmap
-
Cisco IOS PKI Overview: Understanding and Planning a PKI
-
Deploying RSA Keys Within a PKI
-
Configuring Authorization and Revocation of Certificates in a PKI
-
Configuring Certificate Enrollment for a PKI
-
Setting Up Secure Device Provisioning (SDP) for Enrollment in a PKI
-
Configuring and Managing a Cisco IOS Certificate Server for PKI Deployment
-
Storing PKI Credentials
-
Source Interface Selection for Outgoing Traffic with Certificate Authority (CA)
-
IOS PKI Performance Monitoring and Optimization
-
- Dynamic Multipoint VPN (DMVPN)
- Easy VPN
-
Cisco Group Encrypted Transport VPN
- SSL VPN
-
Feedback
Table Of Contents
Single SignOn Netegrity Cookie Support
Thin Client Control List Support
Features Not Supported on the Cisco IOS SSL VPN
SSL VPN Client-Side Certificate-Based Authentication
Full-Tunnel Cisco Express Forwarding Support
Netegrity Cookie-Based Single SignOn Support
Stateless High Availability with Hot Standby Router Protocol
TCP Port Forwarding and Thin Client
License String Support for the 7900 VPN Client
Cisco AnyConnect VPN Client Full Tunnel Support
How to Configure SSL VPN Services on a Router
Configuring an SSL VPN Gateway
Configuring a Generic SSL VPN Gateway
Configuring an SSL VPN Context
Configuring an SSL VPN Policy Group
Configuring Local AAA Authentication for SSL VPN User Sessions
Configuring AAA for SSL VPN Users Using a Secure Access Control Server
Configuring RADIUS Accounting for SSL VPN User Sessions
Monitoring and Maintaining RADIUS Accounting for an SSL VPN Session
Configuring RADIUS Attribute Support for SSL VPN
Configuring a URL List for Clientless Remote Access
Configuring Microsoft File Shares for Clientless Remote Access
Configuring Citrix Application Support for Clientless Remote Access
Configuring Application Port Forwarding
Configuring the SSL VPN Gateway to Distribute CSD and Cisco AnyConnect VPN Client Package Files
Configuring Cisco Secure Desktop Support
Configuring Cisco AnyConnect VPN Client Full Tunnel Support
Configuring Advanced SSL VPN Tunnel Features
Configuring VRF Virtualization
Associating an ACL Attribute with a Policy Group
Monitoring and Maintaining ACLs
Configuring SSO Netegrity Cookie Support for a Virtual Context
Associating an SSO Server with a Policy Group
Configuring URL Obfuscation (Masking)
Adding a CIFS Server URL List to an SSL VPN Context and Attaching It to a Policy Group
Configuring User-Level Bookmarks
Disabling Full-Tunnel Cisco Express Forwarding
Configuring Automatic Authentication and Authorization
Configuring SSL VPN Client-Side Certificate-Based Authentication
Configuring a URL Rewrite Splitter
Configuring a Backend HTTP Proxy
Configuring Stateless High Availability with HSRP for SSL VPN
Configuring Internationalization
Generating the Template Browser Attribute File
Importing the Browser Attribute File
Verifying That the Browser Attribute File Was Imported Correctly
Verifying That the Language File Was Imported Correctly
Importing the File into the URL List and Binding It to a Policy Group
Verifying That the URL List File Was Bound Correctly to the Policy Group
Configuring a Virtual Template
Configuring SSLVPN DVTI Support
Configuring per-Tunnel Virtual Templates
Configuring per-Context Virtual Templates
Configuring SSL VPN Phase-4 Features
Configuring the Start Before Logon Functionality
Configuring IP NetMask Functionality
Verifying SSL VPN Configurations
Configuration Examples for SSL VPN
Example: Configuring a Generic SSL VPN Gateway
Example: Configuring HTTP Proxy
Example: Configuring Microsoft File Shares for Clientless Remote Access
Example: Configuring Citrix Application Support for Clientless Remote Access
Example: Configuring Application Port Forwarding
Example: Configuring VRF Virtualization
Example: RADIUS Accounting for SSL VPN Sessions
Example: URL Obfuscation (Masking)
Example: Adding a CIFS Server URL List and Attaching It to a Policy List
Example: Typical SSL VPN Configuration
Example: Cisco Express Forwarding-Processed Packets
Example: Multiple AnyConnect VPN Client Package Files
Example: Stateless High Availability with HSRP
Examples: Internationalization
Example: Generated Browser Attribute Template
Example: Copying the Browser Attribute File to Another PC for Editing
Example: Copying the Edited File to flash
Example: Output Showing That the Edited File Was Imported
Example: Copying the Language File to Another PC for Editing
Example: Copying the Edited Language File to the Storage Device
Example: Language Template Created
Examples: SSL VPN DVTI Support
Examples: Configuring per-Tunnel Virtual Templates
Example: Configuring per-Context Virtual Templates
Examples: SSL VPN Phase-4 Features
Example: Configuring the Start Before Logon Functionality
Example: Configuring Split ACL Support
Example: Configuring IP NetMask Functionality
Examples: Debug Command Output
Example: show webvpn context name
Example: show webvpn gateway name
Example: show webvpn install file
Example: show webvpn install package svc
Example: show webvpn install status svc
Example: show webvpn nbns context all
Example: show webvpn policy (with NTLM Disabled)
Example: show webvpn session user
Example: show webvpn stats sso
Example: FVRF show Command Output
Feature Information for SSL VPN
SSL VPN
First Published: February 27, 2006Last Updated: October 5, 2011The SSL VPN feature (also known as WebVPN) provides support, in Cisco IOS software, for remote user access to enterprise networks from anywhere on the Internet. Remote access is provided through a Secure Socket Layer (SSL)-enabled SSL VPN gateway. The SSL VPN gateway allows remote users to establish a secure VPN tunnel using a web browser. This feature provides a comprehensive solution that allows easy access to a broad range of web resources and web-enabled applications using native HTTP over SSL (HTTPS) browser support. SSL VPN delivers three modes of SSL VPN access: clientless, thin-client, and full-tunnel client support.
This document is primarily for system administrators. If you are a remote user, see the document SSL VPN Remote User Guide.
Note
The Cisco AnyConnect VPN Client is introduced in Cisco IOS Release 12.4(15)T. This feature is the next-generation SSL VPN Client. If you are using Cisco software earlier than Cisco IOS Release 12.4(15)T, you should be using SSL VPN Client and see GUI for the SSL VPN Client when you are web browsing. However, if you are using Cisco Release 12.4(15)T or a later release, you should be using Cisco AnyConnect VPN Client and see GUI for Cisco AnyConnect VPN Client when you are web browsing.
For "What's New" information about SSL VPN features by release, see the section "Finding Feature Information"
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for SSL VPN" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
•
•
Prerequisites for SSL VPN
•
–
–
–
Note
•
•
•
•
–
Note
•
•
•
•
•
•
ACL Support
•
Single SignOn Netegrity Cookie Support
•
Licensing
•
Restrictions for SSL VPN
•
•
Cisco AnyConnect VPN Client
•
The Cisco AnyConnect VPN Client does not support the following:
•
•
•
•
•
•
•
•
Thin Client Control List Support
•
HTTP Proxy
•
•
Features Not Supported on the Cisco IOS SSL VPN
The following features are not supported on the Cisco IOS SSL VPN:
•
•
•
•
•
•
•
•
•
•
•
•
–
–
–
–
–
–
–
–
•
Note
Information About SSL VPN
SSL VPN Overview
Cisco IOS SSL VPN provides SSL VPN remote-access connectivity from almost any Internet-enabled location using only a web browser that natively supports SSL encryption. This feature allows your company to extend access to its secure enterprise network to any authorized user by providing remote-access connectivity to corporate resources from any Internet-enabled location.
Cisco IOS SSL VPN can also support access from noncorporate-owned machines, including home computers, Internet kiosks, and wireless hot spots. These locations are difficult places to deploy and manage VPN client software and the remote configuration required to support IPsec VPN connections.
Figure 1 shows how a mobile worker (the lawyer at the courthouse) can access protected resources from the main office and branch offices. Site-to-site IPsec connectivity between the main and remote sites is unaltered. The mobile worker needs only Internet access and supported software (web browser and operating system) to securely access the corporate network.
Figure 1 Secure SSL VPN Access Model
SSL VPN delivers the following three modes of SSL VPN access:
•
•
•
SSL VPN application accessibility is somewhat constrained relative to IPsec VPNs; however, SSL-based VPNs provide access to a growing set of common software applications, including web page access, web-enabled services such as file access, e-mail, and TCP-based applications (by way of a downloadable thin-client applet). SSL-based VPN requires slight changes to user workflow because some applications are presented through a web browser interface, not through their native GUI. The advantage for SSL VPN comes from accessibility from almost any Internet-connected system without needing to install additional desktop software.
Licensing
Starting from Cisco IOS Release 15.0(1)M, the SSL VPN gateway is a seat-counted licensing feature on the Cisco 880, Cisco 890, Cisco 1900, Cisco 2900, and Cisco 3900 platforms. A license count is associated with each counted license and the count indicates the instances of the feature available for use in the system. In the case of SSL VPN, a seat refers to the maximum number of sessions allowed at a time.
You can get the license at http://www.cisco.com/go/license.
For instructions on installing a license using Cisco License Manager (CLM), see the User Guide for Cisco License Manager, Release 2.2 at http://www.cisco.com/en/US/docs/net_mgmt/license_manager/lm_2_2/2.2_user_guide/clm_book.html.
For instructions on installing a license using Cisco CLI, see the "Cisco IOS Software Activation Tasks and Commands" chapter of the Software Activation Configuration Guide at http://www.cisco.com/en/US/docs/ios/csa/configuration/guide/csa_commands_ps6441_TSD_Products_Configuration_Guide_Chapter.html.
SSL VPN supports the following types of licenses:
•
•
•
•
For all the license types, except the evaluation license, a EULA has to be accepted during the license installation. This means that all the license types except the evaluation license are activated after installation. In the case of an evaluation license, a EULA is presented during an SSL VPN gateway configuration or an SSL VPN context configuration.
An SSL VPN session corresponds to a successful login to the SSL VPN service. An SSL VPN session is created when a valid license is installed and the user credentials are successfully validated. On a successful user validation, a request is made to the licensing module to get a seat. An SSL VPN session is created only when the request is successful. If a valid license is not installed, the SSL VPN gateway configuration and SSL VPN context configurations are successful, but the user cannot login successfully. When multiple gateways and contexts are configured, the total number of sessions are equal to the total sessions allowed by the license.
The same user can create multiple sessions and for each session a seat count is reserved. The seat reservation does not happen in the following cases:
•
•
•
•
When the total active sessions are equal to the maximum license count of the current active license, no more new sessions are allowed.
The reserved seat count or session is released when
•
•
•
•
•
•
•
You can use the show webvpn license command to display the available count and the current usage. To display the current license type and time period left in case of a nonpermanent license, use the show license command. To get information related to license operations, events, and errors, use the debug webvpn license command.
For migrating from any Cisco IOS 12.4T Release to Cisco IOS 15.x Release, use the license migration tool at https://tools.cisco.com/SWIFT/Licensing/LicenseAdminServlet/migrateLicense.
New Cisco IOS SSL VPN licenses that are generated are cumulative. Therefore the old licenses become inactive when a new license is applied. For example, when you are upgrading your license from 10 counts to 20 counts (an increase of 10 counts on the current 10 counts), Cisco provides a single 20 count license. The old license for 10 counts is not required when a permanent license for a higher count is available. However, the old license will exist in an inactive state as there is no reliable method to clear the old license.
Modes of Remote Access
Remote Access Overview
End-user login and authentication is performed by the web browser to the secure gateway using an HTTP request. This process creates a session that is referenced by a cookie. After authentication, the remote user is shown a portal page that allows access to the SSL VPN networks. All requests sent by the browser include the authentication cookie. The portal page provides all the resources available on the internal networks. For example, the portal page could provide a link to allow the remote user to download and install a thin-client Java applet (for TCP port forwarding) or a tunneling client.
Figure 2 shows an overview of the remote access modes.
Figure 2 Modes of Remote Access Overview
Table 1 summarizes the level of SSL VPN support that is provided by each access mode.
Table 1 Access Mode Summary
Clientless Mode
In clientless mode, the remote user accesses the internal or corporate network using the web browser on the client machine. The PC of the remote user must run the Windows 2000, Windows XP, or Linux operating systems.
The following applications are supported in clientless mode:
•
•
–
–
–
–
–
–
–
–
–
–
–
Note
•
Thin-Client Mode
Thin-client mode, also called TCP port forwarding, assumes that the client application uses TCP to connect to a well-known server and port. In thin-client mode, the remote user downloads a Java applet by clicking the link provided on the portal page, or the Java applet is downloaded automatically (see the "Options for Configuring HTTP Proxy and the Portal Page" section and "Options for Configuring HTTP Proxy and the Portal Page" section). The Java applet acts as a TCP proxy on the client machine for the services that you configure on the gateway.
The applications that are supported in thin-client mode are mainly e-mail-based (SMTP, POP3, and Internet Map Access Protocol version 4 [IMAP4]) applications.
Note
The Java applet initiates an HTTP request from the remote user client to the SSL VPN gateway. The name and port number of the internal e-mail server is included in the HTTP request (POST or CONNECT). The SSL VPN gateway creates a TCP connection to that internal e-mail server and port.
The Java applet starts a new SSL connection for every client connection.
You should observe the following restrictions when using thin-client mode:
•
•
Note
Options for Configuring HTTP Proxy and the Portal Page
Effective with Cisco IOS Release 12.4(11)T, administrators have more options for configuring the HTTP proxy and the portal page. If HTTP proxy is enabled, the Java applet acts as the proxy for the browser of the user, thereby connecting the client workstation with the gateway. The home page of the user (as defined by the user group) is opened automatically or, if configured by the administrator, the user is directed to a new website.
HTTP proxy supports both HTTP and HTTPS.
Benefits of Configuring HTTP Proxy
HTTP supports all client-side web technologies (including HTML, Cascading Style Sheets [CSS], JavaScript, VBScript, ActiveX, Java, and flash), HTTP Digest authentication, and client certificate authentication. Remote users can use their own bookmarks, and there is no limit on cookies. Because there is no mangling involved and the client can cache the objects, performance is much improved over previous options for configuring the HTTP proxy and portal page.
Illustrations of Port Forwarding with and Without an HTTP Proxy Configuration
Figure 3 illustrates TCP port forwarding without HTTP proxy configured.
Figure 3 TCP Port Forwarding Without HTTP Proxy Configured
In Figure 3, the following steps must occur:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Figure 4 illustrates TCP port forwarding when HTTP proxy is configured.
Figure 4 HTTP Proxy
In Figure 4, the following steps occur:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Note
Tunnel Mode
In a typical clientless remote access scenario, remote users establish an SSL tunnel to move data to and from the internal networks at the application layer (for example, web and e-mail). In tunnel mode, remote users use an SSL tunnel to move data at the network (IP) layer. Therefore, tunnel mode supports most IP-based applications. Tunnel mode supports many popular corporate applications (for example, Microsoft Outlook, Microsoft Exchange, Lotus Notes E-mail, and Telnet).
The tunnel connection is determined by the group policy configuration. The Cisco AnyConnect VPN Client is downloaded and installed on the remote user PC, and the tunnel connection is established when the remote user logs into the SSL VPN gateway.
By default, the Cisco AnyConnect VPN Client is removed from the client PC after the connection is closed. However, you have the option to keep the Cisco AnyConnect VPN Client installed on the client PC.
SSL VPN Features
•
•
•
•
•
•
•
Access Control Enhancements
Effective with Cisco IOS Release 12.4(20)T, administrators can configure automatic authentication and authorization for users. Users provide their usernames and passwords via the gateway page URL and do not have to reenter their usernames and passwords from the login page. Authorization is enhanced to support more generic authorization, including local authorization. In previous releases, only RADIUS authorization was supported.
For information about configuring this feature, see the section "Configuring Automatic Authentication and Authorization."
SSL VPN Client-Side Certificate-Based Authentication
This feature enables SSL VPN to authenticate clients based on the client's AAA username and password and also supports WebVPN gateway authentication of clients using AAA certificates.
SSL VPN Client-Side Certificate-Based Authentication feature includes the following features:
•
•
•
•
Certificate-Only Authentication and Authorization Mode
Certificate-only authorization requires the user to provide a AAA authentication certificate as part of the WebVPN request, but does not require the username and password for authorization. The user requests WebVPN access with the AAA authentication certificate from the WebVPN gateway. The WebVPN gateway validates the identity of the client using the AAA authentication certificate presented to it. The WebVPN extracts the username from the AAA authentication certificate presented to it and uses it as the username in the AAA request. AAA authentication and AAA authorization are then completed with a hard-coded password. To configure certificate-only authorization use the authentication certificate command.
Two-Factor Authentication and Authorization Mode
Two-factor authorization requires the user to request WebVPN access and present a AAA authentication certificate. The AAA authentication certificate is validated and the client's identity is verified. The WebVPN gateway then presents the login page to the user. The user enters their username and password and WebVPN sends AAA authentication and AAA authorization requests to the AAA server. The AAA authentication list and the AAA authorization lists configured on the server are then used for authentication and authorization. To configure two-factor authentication and authorization mode use the authentication certificate aaa command.
Note
Identification of WebVPN Context at Runtime Using Certificate Map Match Rules
Certificate map match rules are used by SSL VPN to identify the WebVPN context at runtime. The WebVPN context is required for AAA authentication and authorization mode and trustpoint configuration. When the user does not provide the WebVPN context, the identification of the WebVPN context at runtime is possible using certificate map matching by matching the certificate presented by the client with the certificate map match rules. To configure certificate map matching in WebVPN use the match-certificate command.
Support for AnyConnect Client to Implement Certificate Matching Based on Client Profile Attributes
Cisco AnyConnect client has certificate match functionality allowing it to select a suitable certificate while initiating tunnel connection with SSL VPN. In the case of standalone mode, the certificate selection is made based on the certificate match. When selecting a certificate, Cisco AnyConnect client can select the appropriate certificate based on the AnyConnect client profile attributes. This requires SSL VPN to support AnyConnect client profiles. The profile file is imported after modification by the administrator using the svc profile command. To create an AnyConnect client profile use the template that appears after installing Cisco AnyConnect in this location: \Documents and Settings\All Users\Application Data\Cisco\ CiscoAnyConnectVPNClient\Profile\AnyConnectProfile.tmpl.
The following are the certificate match types available with Cisco AnyConnect client:
Certificate Key Usage Matching
Certificate key usage matching offers a set of constraints based on the broad types of operations that can be performed with a given certificate.
Extended Certificate Key Usage Matching
This matching allows an administrator to limit the certificates that can be used by the client based on the Extended Key Usage fields.
Certificate Distinguished Name Mapping
This certificate matching capability allows an administrator to limit the certificates that can be used by the client to those matching the specified criteria and criteria match conditions. This includes the ability to specify that a certificate must or must not have a specified string and also if wild carding for the string should be allowed.
AnyConnect Client Support
Effective with Cisco IOS Release 12.4(20)T, AnyConnect Client support is added for several client-side platforms, such as Microsoft Windows, Apple-Mac, and Linux. The ability to install AnyConnect in a standalone mode is also added. In addition, the Release 12.4(20)T allows you to install multiple AnyConnect VPN client packages to a gateway. For information on configuring multiple packages, see the section "Configuring the SSL VPN Gateway to Distribute CSD and Cisco AnyConnect VPN Client Package Files."
Application ACL Support
Effective with Cisco IOS Release 12.4(11)T, the Application ACL Support feature provides administrators with the flexibility to fine-tune access control at the application layer level, for example, on the basis of a URL.
For information about configuring this feature, see the sections "Configuring ACL Rules" and "Associating an ACL Attribute with a Policy Group."
Automatic Applet Download
Effective with Cisco IOS Release 12.4(9)T, administrators have the option of automatically downloading the port-forwarding Java applet. The Automatic Applet Download feature must be configured on a group policy basis.
Note
To configure the automatic download, see the section "Configuring an SSL VPN Policy Group" section.
Backend HTTP Proxy
The Backend HTTP Proxy feature, added in Cisco IOS Release 12.4(20)T, allows administrators to route user requests through a backend HTTP proxy, providing more flexibility and control than routing requests through internal web servers. This feature adds the following new AAA attributes:
http-proxy-serverhttp-proxy-server-portFor information about configuring this feature, see the section "Configuring a Backend HTTP Proxy."
Front-Door VRF Support
Effective with Cisco IOS Release 12.4(15)T, front-door virtual routing and forwarding (FVRF) support, coupled with the already supported internal virtual routing and forwarding (IVRF), provides for increased security. The feature allows the SSL VPN gateway to be fully integrated into a Multiprotocol Label Switching (MPLS) or non-MPLS network (wherever the VRFs are deployed). The virtual gateway can be placed into a VRF that is separate from the Internet to avoid internal MPLS and IP network exposure. This placement reduces the vulnerability of the router by separating the Internet routes or the global routing table. Clients can now reach the gateway by way of the FVRF, which can be separate from the global VRF. The backend, or IVRF, functionality remains the same.
This FVRF feature provides for overlapping IP addresses.
Figure 5 is a scenario in which FVRF has been applied.
Figure 5 Scenario in Which FVRF Has Been Applied
To configure FVRF, see the "Configuring FVRF" section.
Full-Tunnel Cisco Express Forwarding Support
Effective with Cisco IOS Release 12.4(20)T, Full-Tunnel Cisco Express Forwarding support is added for better throughput performance than in earlier releases. This feature is enabled by default. To turn off full-tunnel Cisco Express Forwarding support, use the no webvpn cef command.
Note
For sample output showing Cisco Express Forwarding-processed packets, see the
"Example: Cisco Express Forwarding-Processed Packets" section.Network Address Translation (NAT) configuration is sometimes used to forward TCP port 443 traffic destined to the WAN interface of a router through an internal webserver.
There are two methods of implementing Cisco IOS SSL VPN on a preexisting NAT configuration. The Cisco-recommended method is to use the WebVPN gateway IP address as the secondary address on the WAN interface. This method helps improve the WebVPN throughput performance. The following is a sample configuration of the recommended method on Cisco IOS SSL VPN:
interface GigabitEthernet 0/0ip address 10.1.1.1 255.255.255.0ip address 10.1.1.2 255.255.255.0 secondary !webvpn gateway ssl_vpnip address 10.1.1.2 port 443
In the second method the WebVPN gateway uses a private IP address configured on a loopback interface and performs a NAT operation to convert the private IP address to a publically routable address. The following configuration is not supported on Cisco IOS SSL VPN because this configuration causes packets to become process-switched instead of being Cisco Express Forwarding-switched:
interface Loopback 10ip address 192.0.2.1 255.255.255.0!interface GigabitEthernet 0/0description WAN interfaceip address 10.1.1.1 255.0.0.0!ip nat inside source static 192.0.2.1 10.1.1.2 !webvpn gateway ssl_vpnip address 192.0.2.1 port 443GUI Enhancements
In Cisco IOS Release 12.4(15)T, ergonomic improvements are made to the GUI of the Cisco IOS SSL VPN gateway. The improved customization of the user interface provides for greater flexibility and the ability to tailor portal pages for individualized views. Enhancements are made to the following web screens:
•
•
Login Screen
Figure 6 is an example of a typical login screen.
Figure 6 Typical Login Screen
Banner
The banner is a small popup box (see Figure 7) that appears after the user is logged in and before the portal page appears.
The message in the popup box is configured using the banner command.
Figure 7 Banner
Customization of a Login Page
Login screens can be customized by an administrator. Figure 8 shows the fields that can be customized.
For information about setting various elements of the login page, see the document Cisco IOS Security Command Reference, Release 12.4T, for the color, logo, login-message, login-photo, secondary-color, text-color, title, title-color, and text-color commands.
Figure 8 Login Page with Callouts of the Fields That Can Be Customized
Portal Page
The portal page (see Figure 9) is the main page for the SSL VPN functionality. You can customize this page to contain the following:
•
•
•
•
•
Note
•
•
Note
•
Items that you have not configured are not displayed on the portal page.
Note
Figure 9 is an example of a typical portal page.
Figure 9 Typical Portal Page
Note
Customization of a Portal Page
Portal pages can be customized by an administrator. Figure 10 shows various fields, including the fields that can be customized by an administrator. The fields that can be customized by an administrator are as follows:
•
•
•
•
•
Figure 10 Portal Page with Callouts of Various Fields, Including Those That Can Be Customized
Table 2 provides information about various fields on the portal page. For information about setting elements such as color or titles, see command information in the Cisco IOS Security Command Reference, Release 12.4T, for the color, functions, hide-url-bar, logo, port-forward, title, title-color, secondary-color, secondary-text-color, and url-list commands.
Internationalization
The Internationalization feature provides multilanguage support for messages initiated by the headend for SSL VPN clients, such as Cisco Secure Desktop (CSD) and SSL VPN Client (SVC). With the Internationalization feature, administrators can import their own attribute files in an XML format so that other languages can be imported using an editor that supports multilanguages.
Figure 11 shows a portal page in English. Users can select any language you have imported for certain SSL VPN web pages (login message, title page, and URL lists).
Figure 11 Portal Page in English
Figure 12 shows that an administrator has imported files in Japanese. A user has selected Japanese as the language for certain SSL VPN web pages (login message, title, and URL lists).
Figure 12 Portal Page in Japanese
For information about configuring this feature, see the "Configuring Internationalization" section. For examples relating to this feature, see the "Examples: Internationalization" section.
Max-User Limit Message
A user that tries to log in to a Web VPN context when the maximum user limit has been reached receives a "Max-user limit reached" message.
Netegrity Cookie-Based Single SignOn Support
The Netegrity SiteMinder product provides a Single SignOn feature that allows a user to log in a single time for various web applications. The benefit of this feature is that users are prompted to log in only once. This feature is accomplished by setting a cookie in the browser of a user when the user initially logs in.
Effective with Cisco IOS Release 12.4(11)T, Netegrity cookie-based SSO is integrated with SSL VPN. It allows administrators to configure an SSO server that sets a SiteMinder cookie in the browser of a user when the user initially logs in. This cookie is validated by a SiteMinder agent on subsequent user requests to resources that are protected by a SiteMinder realm. The agent decrypts the cookie and verifies whether the user has already been authenticated.
For information about configuring SSO Netegrity Cookie Support and associating it with a policy group using the CLI, see the sections "Configuring SSO Netegrity Cookie Support for a Virtual Context" and "Associating an SSO Server with a Policy Group," respectively.
An SSO server can also be associated with a policy group using RADIUS attributes, as in the following example:
webvpn:sso-server-name=server1For a list of RADIUS attribute-value (AV) pairs that support SSL VPN, see the section "Configuring RADIUS Attribute Support for SSL VPN."
NTLM Authentication
NT LAN Manager (NTLM) is supported for SSL VPN effective with Cisco IOS Release 12.4(9)T. The feature is configured by default.
RADIUS Accounting
Effective with Cisco IOS Release 12.4(9)T, this feature provides for RADIUS accounting of SSL VPN user sessions.
For information about configuring SSL VPN RADIUS accounting for SSL VPN user sessions, see the section "Configuring RADIUS Accounting for SSL VPN User Sessions."
For more information about configuring RADIUS accounting, see the "Configuring RADIUS" module in the Cisco IOS Security Configuration Guide: Securing User Services.
For a list of RADIUS AV pairs that support SSL VPN, see the section "Configuring RADIUS Attribute Support for SSL VPN."
Stateless High Availability with Hot Standby Router Protocol
Hot Standby Router Protocol (HSRP) provides high network availability by routing IP traffic from hosts on Ethernet networks without having to rely on the availability of any single router. HSRP is particularly useful for hosts that do not support a router discovery protocol, such as ICMP Router Discovery Protocol (IRDP), and that do not have the functionality to switch to a new router when their selected router reloads or loses power. Without this functionality, a router that loses its default gateway because of a router failure is unable to communicate with the network.
HSRP is configurable on LAN interfaces using standby CLI. It is possible to use the standby IP address from an interface as the local IPsec identity, or local tunnel endpoint.
You can use the standby IP address as the SSL VPN gateway address to apply failover to VPN routers by using HSRP. Remote SSLVPN users connect to the local VPN gateway using the standby address that belongs to the active device in the HSRP group. In the event of failover, the standby device takes over ownership of the standby IP address and begins to service remote VPN users.
Using the Stateless High Availability with Hot Standby Router Protocol feature, the remote user has to be aware of only the HSRP standby address instead of a list of gateway addresses.
Figure 13 shows the enhanced HSRP functionality topology. Traffic is serviced by the active Router P, the active device in the standby group. In the event of failover, traffic is diverted to Router S, the original standby device. Router S assumes the role of the new active router and takes ownership of the standby IP address.
Figure 13 Stateless High Availability with HSRP for SSL VPN
For information about configuring Stateless High Availability with HSRP, see the "Configuring Stateless High Availability with HSRP for SSL VPN" section.
Note
TCP Port Forwarding and Thin Client
Note
Note
When the remote user clicks the Start button of the Thin Client Application (under "Application Access), a new window is displayed. This window initiates the downloading of a port-forwarding applet. Another window is then displayed. This window asks the remote user to verify the certificate with which this applet is signed. When the remote user accepts the certificate, the applet starts running, and port-forwarding entries are displayed (see Figure 14). The number of active connections and bytes that are sent and received is also listed on this window.
Note
You should have configured IP addresses, Domain Name System (DNS) names, and port numbers for the e-mail servers. The remote user can then launch the e-mail client, which is configured to contact the e-mail servers and send and receive e-mails. POP3, IMAP, and SMTP protocols are supported.
The window attempts to close automatically if the remote user is logged out using JavaScript. If the session terminated and a new port forwarding connection is established, the applet displays an error message.
Figure 14 TCP Port Forwarding Page
Caution
Table 3 lists remote system requirements for Thin Client.
Table 3 SSL VPN Remote System Thin-Client Requirements
Client applications installed.
—
Cookies enabled on browser.
—
Administrator privileges.
You must be the local administrator on your PC.
Sun Microsystems JRE version 1.4 or later installed.
SSL VPN automatically checks for JRE whenever the remote user starts Thin Client. If it is necessary to install JRE, a popup window displays directing remote users to a site where it is available.
Client applications configured, if necessary.
Note
To configure the client application, use the locally mapped IP address and port number of the server. To find this information, do the following:
•
•
•
Windows XP SP2 patch.
If you are running Windows XP SP2, you must install a patch from Microsoft that is available at the following address:
http://support.microsoft.com/?kbid=884020
This is a known Microsoft issue.
URL Obfuscation
The URL Obfuscation feature provides administrators with the ability to obfuscate, or mask, sensitive portions of an enterprise URL, such as IP addresses, hostnames, or part numbers. For example, if URL masking is configured for a user, the URL in the address bar could have the port and hostname portion garbled, as in this example:
https://slvpn-gateway.examplecompany.com/http/cF9HxnBjRmSFEzBWpDtfXfigzL559MQo51Qj/cgi-bin/submit.p
For information about configuring this feature, see the section "Associating an SSO Server with a Policy Group."
URL Rewrite Splitter
Effective with Cisco IOS Release 12.4(20)T, the URL Rewrite Splitter feature allows administrators to mangle selective URLs. Mangling is a CPU-intensive and time-consuming process, so mangling only selective URLs can result in a savings of memory and time.
For information about configuring this feature, see the section "Configuring a URL Rewrite Splitter."
User-Level Bookmarking
Effective with Cisco IOS Release 12.4(15)T, users can bookmark URLs while connected through an SSL VPN tunnel. Users can access the bookmarked URLs by clicking the URLs.
User-level bookmarking is turned by default. There is no way to turn it off. To set the storage location, administrators can use the user-profile location command. If the user-profile location command is not configured, the location flash:/webvpn/{context name}/ is used.
Virtual Templates
A virtual template enables SSL VPN to interoperate with IP features such as Network Address Translation (NAT), firewall, and policy-based routing.
For information about configuring this feature, see the section "Configuring a Virtual Template."
License String Support for the 7900 VPN Client
The Cisco IOS SSL VPN accepts license strings from Cisco IP Phones. Cisco IOS VPN concentrators support the VPN license type linksys-phone in order to support the Galactica VPN client on 79x2 and 79x5 phones.
In the case of a transformer platform, response to the license message (linksys-phone) will succeed if the license requirements are met. However, an Integrated Services Routers (ISR) router must always respond with a success message so that the Galactica VPN client can attempt to establish a VPN connection.
SSLVPN DVTI Support
The SSLVPN DVTI Support feature adds Dynamic Virtual Tunnel Interface (DVTI) support to the Secure Socket Layer Virtual Private Network (SSL VPN) and hence enables seamless interoperability with IP features such as Firewall, Network Address Translation (NAT), Access Control Lists (ACLs), and Virtual Routing and Forwarding (VRF). This feature also provides DVTI support, which allows IP feature configuration on a per-tunnel basis.
SSL VPN provides three modes to access a VPN: clientless, thin client, and full tunnel. The full tunnel mode uses an internal virtual interface to route the traffic to and from the SSL VPN tunnel. Before the SSL VPN DVTI Support feature was introduced, the virtual interface was created during the SSL VPN virtual interface configuration and users were not allowed to apply IP features to the SSL VPN traffic.
The SSLVPN DVTI Support feature uses a virtual template infrastructure to provide DVTI support for SSL VPN. IP features are configured in a virtual template that is associated with the SSL VPN or WebVPN context. The IP features configured in the virtual template are used to create a virtual access interface that is internally used to tunnel SSL VPN traffic. Virtual templates in a WebVPN context are applied in two ways: per-context and per-tunnel.
Note
Prerequisites for SSLVPN DVTI Support
•
•
•
•
Restrictions for SSLVPN DVTI Support
•
Virtual Template Infrastructure
A generic interface template service is required with features such as stackabilility, Virtual Private Dialup Network (VPDN), Multilink PPP (MLP), and virtual profiles. Virtual template interface service delivers a generic interface template service. The virtual template interface, command buffer, and virtual access interface functions enables you to populate a virtual-access interface using a pre-defined configuration that is stored in a virtual template interface and security servers such as TACACS+ and RADIUS.
For example, in stackablility, a virtual template interface is assigned to a stack group. Whenever a stack member needs a virtual interface, the virtual template interface service is called by a member to obtain a virtual access interface cloned with the same configuration as the configuration of the assigned virtual template interface.
In a virtual profile, the per-user configuration can be stored in a security server. That is, when the user dials in, the desired configuration can be cloned into the virtual access interface associated with the user. The virtual template service provides an application programming interface (API) for a virtual profile to clone a buffer of commands to a virtual access interface. The virtual profile does the actual interaction with the security server.
Note
SSL VPN Phase-4 Features
The SSL VPN Phase-4 Features feature provides the following enhancements to the Cisco IOS Secure Sockets Layer Virtual Private Network (SSL VPN):
•
•
•
•
"Start before logon" option for the Cisco IOS SSL VPN headend
Prerequisites for SSL VPN Phase-4 Features
You must use a valid K9 image to configure the SSL VPN Phase-4 Features.
Full Tunnel Package
When you instal the AnyConnect or SVC full tunnel package using the webvpn install svc command on the Cisco IOS headend, the package name gets renamed to svc_pkg_<number>. This renaming omits package information and Base Station Ethernet (BSE) operating system information, and thus makes you difficult to remove or uninstall the package. This functionality was modified in Cisco IOS Release 15.1(1)T to retain the name during installation of the package.
The limit on the filename size on the Cisco IOS file system (IFS) is 120 bytes. Unless the package name is greater than this limit, the package name does not change. If the filename exceeds this limit, then the installation fails. The following error message is displayed on the router console:
Error::Package name exceeds 120 charactersSSL VPN per-User Statistics
Per-user statistics functionality provides an option to filter the cumulative statistics on a per-user basis for the Cisco IOS SSL VPN sessions. Use the show webvpn session user command to enable this functionality. This command is applicable only for user session statistics and tunnel statistics. See Cisco Cisco IOS Security Command Reference for more information on the show webvpn session command.
Cisco AnyConnect VPN Client Full Tunnel Support
•
•
Remote Client Software from the SSL VPN Gateway
The Cisco AnyConnect VPN Client software package is pushed from the SSL VPN gateway to remote clients when support is needed. The remote user (PC or device) must have either the Java Runtime Environment for Windows (version 1.4 later), or the browser must support or be configured to permit Active X controls. In either scenario, the remote user must have local administrative privileges.
Address Pool
The address pool is first defined with the ip local pool command in global configuration mode. The standard configuration assumes that the IP addresses in the pool are reachable from a directly connected network.
Address Pools for Nondirectly Connected Networks
If you need to configure an address pool for IP addresses from a network that is not directly connected, perform the following steps:
1.
2.
3.
4.
Manual Entry to the IP Forwarding Table
If the SSL VPN software client is unable to update the IP forwarding table on the PC of the remote user, the following error message will be displayed in the router console or syslog:
Error : SSL VPN client was unable to Modify the IP forwarding table ......This error can occur if the remote client does not have a default route. You can work around this error by performing the following steps:
1.
2.
3.
C:\>route ADD 0.0.0.0 MASK 0.0.0.0 10.1.1.1Other SSL VPN Features
Table 4 lists the requirements for various SSL VPN features.
Table 4 SSL VPN Remote User System Requirements
Web Browsing
Usernames and passwords for protected websites
Users should log out on SSL VPN sessions when they are finished.
The look and feel of web browsing with SSL VPN might be different from what users are accustomed to. For example, when they are using SSL VPN, the following should be noted:
•
•
–
–
–
Also, depending on how a particular account was configured, the following might have occurred:
•
•
Network Browsing and File Management
File permissions configured for shared remote access
Only shared folders and files are accessible through SSL VPN.
Server name and passwords are necessary for protected file servers
—
Domain, workgroup, and server names where folders and files reside
A user might not be familiar with how to locate files through the network of an organization.
Note
Using e-mail:
Thin ClientSame requirements as for Thin Client (see the "TCP Port Forwarding and Thin Client" section)
To use e-mail, users must start Thin Client from the SSL VPN home page. The e-mail client is then available for use.
Note
Other Mail Clients
Microsoft Outlook Express versions 5.5 and 6.0 have been tested.
SSL VPN should support other SMTPS, POP3S, or IMAP4S e-mail programs, such as Netscape Mail, Lotus Notes, and Eudora, but they have not been verified.
Using e-mail:
Web AccessWeb-based e-mail product installed
Supported products are as follows:
•
Netscape, Mozilla, and Internet Explorer are supported with OWA 5.5 and 2000.
Internet Explorer 6.0 or a later version is required with OWA 2003. Netscape and Mozilla are supported with OWA 2003.
•
Operating system support:
Note
•
•
•
SSL VPN-supported browser:
The following browsers have been verified for SSL VPN. Other browsers might not fully support SSL VPN features.
Note
•
•
•
Other web-based e-mail products should also work, but they have not been verified.
Using the Cisco Tunnel Connection
—
To retrieve Tunnel Connection log messages using the Windows Event Viewer, go to Program Files > Administrative Tools > Event Viewer in Windows.
Using Secure Desktop Manager
A Secure Desktop Manager-supported browser
On Microsoft Windows:
•
•
On Linux:
•
Using Cache Cleaner or Secure Desktop
A Cisco Secure Desktop-supported browser
Any browser supported for Secure Desktop Manager.
Platform Support
For information about platform support for the SSL VPN feature, see the data sheet Cisco IOS SSL VPN ("Feature Availability" section).
How to Configure SSL VPN Services on a Router
Configuring and Enabling SSL VPN Services
•
•
•
•
Configuring AAA-Related Features for SSL VPN
•
•
•
•
•
•
Customizing and Enabling SSL VPN Features
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Monitoring and Maintaining SSL VPN Features
•
•
•
Configuring an SSL VPN Gateway
The SSL VPN gateway acts as a proxy for connections to protected resources. Protected resources are accessed through an SSL-encrypted connection between the gateway and a web-enabled browser on a remote device, such as a personal computer. Entering the webvpn gateway command places the router in SSL VPN gateway configuration mode. The following are accomplished in this task:
•
•
•
•
•
•
The SSL VPN provides remote-access connectivity from almost any Internet-enabled location using only a web browser and its native SSL encryption. The ssl encryption command is configured to restrict the encryption algorithms that SSL uses in Cisco IOS software.
Note
The configuration of the ssl trustpoint command is required only if you need to configure a specific certification authority (CA) certificate. A self-signed certificate is automatically generated when an SSL VPN gateway is put in service.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
DETAILED STEPS
What to Do Next
SSL VPN context and policy group configurations must be configured before an SSL VPN gateway can be operationally deployed. Proceed to the section "Configuring an SSL VPN Context" to see information on SSL VPN context configuration.
Configuring a Generic SSL VPN Gateway
To configure a generic SSL VPN gateway, perform the following steps in privileged EXEC mode.
Note
SUMMARY STEPS
1.
2.
DETAILED STEPS
Configuring an SSL VPN Context
The SSL VPN context defines the virtual configuration of the SSL VPN. Entering the webvpn context command places the router in SSL VPN configuration mode. The following are accomplished in this task:
•
•
•
•
•
•
The ssl authenticate verify all command is enabled by default when a context configuration is created. The context cannot be removed from the router configuration while an SSL VPN gateway is in an enabled state (in service).
A virtual hostname is specified when multiple virtual hosts are mapped to the same IP address on the SSL VPN gateway (similar to the operation of a canonical domain name). The virtual hostname differentiates host requests on the gateway. The host header in the HTTP message is modified to direct traffic to the virtual host. The virtual hostname is configured with the gateway command in WebVPN context configuration mode.
Prerequisites
The SSL VPN gateway configuration has been completed.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
webvpn context name
Example:Router(config)# webvpn context context1
Enters WebVPN context configuration mode to configure the SSL VPN context.
TipStep 4
aaa authentication {domain name | list name}
Example:Router(config-webvpn-context)# aaa authentication domain SERVER_GROUP
(Optional) Specifies a list or method for SSL VPN remote-user authentication.
TipStep 5
policy group name
Example:Router(config-webvpn-context)# policy group ONE
(Optional) Creates a policy group within the SSL VPN context and enters WebVPN group policy configuration mode.
•
Step 6
exit
Example:Router(config-webvpn-group)# exit
(Optional) Exits WebVPN group policy configuration mode.
Step 7
default-group-policy name
Example:Router(config-webvpn-context)# default-group-policy ONE
(Optional) Associates a group policy with an SSL VPN context configuration.
•
•
Step 8
exit
Example:Router(config-webvpn-context)# exit
(Optional) Exits WebVPN context configuration mode.
Step 9
gateway name [domain name | virtual-host name]
Example:Router(config-webvpn-context)# gateway GW_1 domain cisco.com
(Optional) Associates an SSL VPN gateway with an SSL VPN context.
•
Step 10
inservice
Example:Router(config-webvpn-gateway)# inservice
(Optional) Enables an SSL VPN context configuration.
•
Step 11
login-message [message-string]
Example:Router(config-webvpn-context)# login-message "Please enter your login credentials"
(Optional) Configures a message for the user login text box displayed on the login page.
Step 12
logo [file filename | none]
Example:Router(config-webvpn-context)# logo file flash:/mylogo.gif
(Optional) Configures a custom logo to be displayed on the login and portal pages of an SSL VPN.
•
•
•
Step 13
max-users number
Example:Router(config-webvpn-context)# max-users 500
(Optional) Limits the number of connections to an SSL VPN that will be permitted.
Step 14
secondary-color color
Example:Router(config-webvpn-context)# secondary-color darkseagreen(Optional) Configures the color of the secondary title bars on the login and portal pages of an SSL VPN.
•
–
–
–
•
Step 15
secondary-text-color {black | white}
Example:Router(config-webvpn-context)# secondary-text-color white
(Optional) Configures the color of the text on the secondary bars of an SSL VPN.
•
•
Step 16
title [title-string]
Example:Router(config-webvpn-context)# title "Secure Access: Unauthorized users prohibited"
(Optional) Configures the HTML title string that is shown in the browser title and on the title bar of an SSL VPN.
•
Step 17
title-color color
Example:Router(config-webvpn-context)# title-color darkseagreen
(Optional) Specifies the color of the title bars on the login and portal pages of an SSL VPN.
•
–
–
–
•
Step 18
svc platform {lin | mac | win} seq sequence-number
Example:Router(config-webvpn-context)# svc platform lin seq 1
(Optional) Configures the platform of an AnyConnect version per context.
•
•
What to Do Next
An SSL VPN policy group configuration must be defined before an SSL VPN gateway can be operationally deployed. Proceed to the "Configuring an SSL VPN Policy Group" section to see information on SSL VPN policy group configuration.
Configuring an SSL VPN Policy Group
The policy group is a container that defines the presentation of the portal and the permissions for resources that are configured for a group of remote users. Entering the policy group command places the router in WebVPN group policy configuration mode. After it is configured, the group policy is attached to the SSL VPN context configuration by configuring the default-group-policy command. The following tasks are accomplished in this configuration:
•
•
•
•
•
Outlook Web Access (OWA) 2003 is supported by the SSL VPN gateway upon completion of this task. The Outlook Exchange Server must be reachable by the SSL VPN gateway via TCP/IP.
A URL list can be configured under the SSL VPN context configuration and then separately for each individual policy group configuration. Individual URL list configurations must have unique names.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
DETAILED STEPS
What to Do Next
At the completion of this task, the SSL VPN gateway and context configurations are operational and enabled (in service), and the policy group has been defined. The SSL VPN gateway is operational for clientless remote access (HTTPS only). Proceed to the "Configuring Local AAA Authentication for SSL VPN User Sessions" section to see information about configuring AAA for remote-user connections.
Configuring Local AAA Authentication for SSL VPN User Sessions
The steps in this task show how to configure a local AAA database for remote-user authentication. AAA is configured in global configuration mode. In this task, the aaa authentication command is not configured under the SSL VPN context configuration. Omitting this command from the SSL VPN context configuration causes the SSL VPN gateway to use global authentication parameters by default.
Prerequisites
SSL VPN gateway and context configurations are enabled and operational.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
What to Do Next
The database that is configured for remote-user authentication on the SSL VPN gateway can be a local database, as shown in this task, or the database can be accessed through any RADIUS or TACACS+ AAA server.
It is recommended that you use a separate AAA server, such as a Cisco ACS. A separate AAA server provides a more robust security solution. It allows you to configure unique passwords for each remote user and accounting and logging for remote-user sessions. Proceed to the "Configuring AAA for SSL VPN Users Using a Secure Access Control Server" section to see more information.
Configuring AAA for SSL VPN Users Using a Secure Access Control Server
The steps in this task show how to configure AAA using a separate RADIUS or TACACS+ server. AAA is configured in global configuration mode. The authentication list or method is referenced in the SSL VPN context configuration with the aaa authentication command. The steps in this task configure AAA using a RADIUS server.
Prerequisites
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
DETAILED STEPS
What to Do Next
Proceed to the section "Configuring RADIUS Attribute Support for SSL VPN" to see RADIUS attribute-value pair information introduced to support this feature.
Configuring RADIUS Accounting for SSL VPN User Sessions
To configure RADIUS accounting for SSL VPN user sessions, perform the following steps.
Prerequisites
Before configuring RADIUS accounting for SSL VPN user sessions, you should first have configured AAA-related commands (in global configuration mode) and have set the accounting list.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Monitoring and Maintaining RADIUS Accounting for an SSL VPN Session
To monitor and maintain your RADIUS accounting configuration, perform the following steps (the debug commands can be used together or individually).
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Configuring RADIUS Attribute Support for SSL VPN
This section lists RADIUS attribute-value (AV) pair information introduced to support SSL VPN. For information on using RADIUS AV pairs with Cisco IOS software, see the "Configuring RADIUS" module in the Cisco IOS Security Configuration Guide: Securing User Services.
Table 5 shows information about SSL VPN RADIUS attribute-value pairs.
Note
webvpn:urllist-name=cisco
webvpn:nbnslist-name=cifs
webvpn:default-domain=cisco.com
Table 5 SSL VPN RADIUS Attribute-Value Pairs
addr (Framed-IP-Address1 )
ipaddr
IP_address
—
addr-pool
string
name
—
auto-applet-download
integer
0 (disable)
1 (enable)20
banner
string
—
citrix-enabled
integer
0 (disable)
1 (enable)30
default-domain
string
—
—
dns-servers
ipaddr
IP_address
—
dpd-client-timeout
integer (seconds)
0 (disabled)-3600
300
dpd-gateway-timeout
integer (seconds)
0 (disabled)-3600
300
file-access
integer
0 (disable)
1 (enable)30
file-browse
integer
0 (disable)
1 (enable)30
file-entry
integer
0 (disable)
1 (enable)30
hide-urlbar
integer
0 (disable)
1 (enable)30
home-page
string
—
—
idletime (Idle-Timeout1)
integer (seconds)
0-3600
2100
ie-proxy-exception
string
DNS_name
—
ipaddr
IP_address
—
ie-proxy-server
ipaddr
IP_address
—
inacl
integer
1-199,
1300-2699—
string
name
—
keep-svc-installed
integer
0 (disable)
1 (enable)31
nbnslist-name
string
name
—
netmask (Framed-IP-Netmask1)
ipaddr
IP_address_mask
—
port-forward-auto
integer
0 (disable)
1 (enable)If this AV pair is not configured, the default is whatever was configured for the group policy.
If this AV pair is configured with an integer of 1, the 1 will override a group policy value of 0.
port-forward-http-proxy
integer
0 (disable)
1 (enable)HTTP proxy is not enabled.
If this AV pair is configured with an integer of 1, the 1 will override a group policy value of 0.
port-forward-http-proxy-url
string
URL address (for example, http://example.com)
—
port-forward-name
string
name
—
primary-dns
ipaddr
IP_address
—
rekey-interval
integer (seconds)
0-43200
21600
secondary-dns
ipaddr
IP_address
—
split-dns
string
—
—
split-exclude4
ipaddr ipaddr
IP_address IP_address_mask
—
word
local-lans
—
split-include4
ipaddr ipaddr
IP_address IP_address_mask
—
sso-server-name
string
name
—
svc-enabled5
integer
0 (disable)
1 (enable)30
svc-ie-proxy-policy
word
none, auto, bypass-local
—
svc-required5
integer
0 (disable)
1 (enable)30
timeout (Session-Timeout1)
integer (seconds)
1-1209600
43200
urllist-name
string
name
—
user-vpn-group
string
name
—
wins-server-primary
ipaddr
IP_address
—
wins-servers
ipaddr
IP_address
—
wins-server-secondary
ipaddr
IP_address
—
1 Standard IETF RADIUS attributes.
2 Any integer other than 0 enables this feature.
3 Any integer other than 0 enables this feature.
4 You can specify either split-include or split-exclude, but you cannot specify both options.
5 You can specify either svc-enable or svc-required, but you cannot specify both options.
What to Do Next
See the "Configuring a URL List for Clientless Remote Access" section for information about customizing the URL list configured in Step 10 of the section "Configuring an SSL VPN Policy Group."
Configuring a URL List for Clientless Remote Access
The steps in this configuration task show how to configure a URL list. The URL list, as the name implies, is a list of HTTP URLs that are displayed on the portal page after a successful login. The URL list is configured in WebVPN context configuration and WebVPN group policy configuration modes.
Prerequisites
SSL VPN gateway and context configurations are enabled and operational.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
DETAILED STEPS
What to Do Next
See the "Configuring Microsoft File Shares for Clientless Remote Access" section for information about configuring clientless remote access to file shares.
Configuring Microsoft File Shares for Clientless Remote Access
In clientless remote access mode, files and directories created on Microsoft Windows servers can be accessed by the remote client through the HTTPS-enabled browser. When clientless remote access is enabled, a list of file server and directory links is displayed on the portal page after login. The administrator can customize permissions on the SSL VPN gateway to provide limited read-only access for a single file or full-write access and network browsing capabilities. The following access capabilities can be configured:
•
•
•
•
•
•
•
•
•
Common Internet File System Support—CIFS is the protocol that provides access to Microsoft file shares and support for common operations that allow shared files to be accessed or modified.
NetBIOS Name Service Resolution—Windows Internet Name Service (WINS) uses NetBIOS name resolution to map and establish connections between Microsoft servers. A single server must be identified by its IP address in this configuration. Up to three servers can be added to the configuration. If multiple servers are added, one server should be configured as the master browser.
Samba Support—Microsoft file shares can be accessed through the browser on a Linux system that is configured to run Samba.
Prerequisites
•
•
Restrictions
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
DETAILED STEPS
What to Do Next
See the "Configuring Citrix Application Support for Clientless Remote Access" section for information about configuring clientless remote access for Citrix- enabled applications.
Configuring Citrix Application Support for Clientless Remote Access
Clientless Citrix support allows the remote user to run Citrix-enabled applications through the SSL VPN as if the application were locally installed (similar to traditional thin-client computing). Citrix applications run on a MetaFrame XP server (or server farm). The SSL VPN gateway provides access to the remote user. The applications run in real time over the SSL VPN. This task shows how to enable Citrix support for policy group remote users.
The Independent Computing Architecture (ICA) client carries keystrokes and mouse clicks from the remote user to the MetaFrame XP server. ICA traffic is carried over TCP port number 1494. This port is opened when a Citrix application is accessed. If multiple application are accessed, the traffic is carried over a single TCP session.
Prerequisites
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
What to Do Next
Support for standard applications that use well-known port numbers, such as e-mail and Telnet, can be configured using the port forwarding feature. See the "Configuring Application Port Forwarding" section for more information.
Configuring Application Port Forwarding
Application port forwarding is configured for thin-client mode SSL VPN. Port forwarding extends the cryptographic functions of the SSL-protected browser to provide remote access to TCP and UDP-based applications that use well-known port numbers, such as POP3, SMTP, IMAP, Telnet, and SSH.
When port forwarding is enabled, the hosts file on the SSL VPN client is modified to map the application to the port number configured in the forwarding list. The application port mapping is restored to default when the user terminates the SSL VPN session.
When you are enabling port forwarding, the SSL VPN gateway will modify the hosts file on the PC of the remote user. Some software configurations and software security applications will detect this modification and prompt the remote user to choose "Yes" to permit. To permit the modification, the remote user must have local administrative privileges.
There is a known compatibility issue with the encryption type and Java. If the Java port-forwarding applet does not download properly and the configuration line ssl encryption 3des-sha1 aes-sha1 is present, you should remove the line from the WebVPN gateway subconfiguration.
Prerequisites
SSL VPN gateway and SSL VPN context configurations are enabled and operational.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Configuring the SSL VPN Gateway to Distribute CSD and Cisco AnyConnect VPN Client Package Files
The SSL VPN gateway is preconfigured to distribute Cisco Secure Desktop (CSD) or Cisco AnyConnect VPN Client software package files to remote users. The files are distributed only when CSD or Cisco AnyConnect VPN Client support is needed. The administrator performs the following tasks to prepare the gateway:
•
•
•
The remote user must have administrative privileges, and the JRE for Windows version 1.4 or later must be installed before the CSD client package can be installed.
For Cisco AnyConnect VPN Client software installation, the remote user must have either the Java Runtime Environment for Windows (version 1.4 or later), or the browser must support or be configured to permit Active X controls.
CSD and Cisco AnyConnect VPN Client software packages should be installed for distribution on the SSL VPN gateway. Download the latest version that supports your device and the image you are using (consult a compatibility matrix for your particular setup).
The CSD software package can be downloaded at the following URL:
•
The Cisco AnyConnect VPN Client software package can be downloaded at the following URL:
•
The Cisco SSL VPN Client software package can be downloaded at the following URL:
•
You will be prompted to enter your login name and password to download these files from cisco.com.
Prerequisites
•
•
Note
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Examples
The following example, starting in global configuration mode, installs the Cisco AnyConnect VPN Client package to an SSL VPN gateway:
Router(config)# webvpn install svc flash:/webvpn/svc.pkgSSL VPN Package SSL-VPN-Client : installed successfullyThe following example, starting in global configuration mode, installs the CSD package to an SSL VPN gateway:
Router(config)# webvpn install csd flash:/securedesktop_10_1_0_9.pkgSSL VPN Package Cisco-Secure-Desktop : installed successfullyThe following example shows that Package B is being installed to an SSL VPN gateway:
Router(config)# webvpn install svc flash:/webvpn/packageB sequence 2What to Do Next
Support for CSD and Cisco AnyConnect VPN Client can be enabled for remote users after the gateway has been prepared to distribute CSD or Cisco AnyConnect VPN Client software.
Configuring Cisco Secure Desktop Support
CSD provides a session-based interface where sensitive data can be shared for the duration of an SSL VPN session. All session information is encrypted. All traces of the session data are removed from the remote client when the session is terminated, even if the connection is terminated abruptly. CSD support for remote clients is enabled in this task.
The remote user (PC or device) must have administrative privileges, and the JRE for Windows version 1.4 or later must be installed before the CSD client packages can be installed.
Prerequisites
•
•
See the "Configuring the SSL VPN Gateway to Distribute CSD and Cisco AnyConnect VPN Client Package Files" section if you have not already prepared the SSL VPN gateway to distribute CSD software.
Restrictions
•
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
What to Do Next
Upon completion of this task, the SSL VPN gateway has been configured to provide clientless and thin-client support for remote users. The SSL VPN feature also has the capability to provide full VPN access (similar to IPsec). Proceed to the "Configuring Cisco AnyConnect VPN Client Full Tunnel Support" section to see more information.
Configuring Cisco AnyConnect VPN Client Full Tunnel Support
The Cisco AnyConnect VPN Client is an application that allows a remote user to establish a full VPN connection similar to the type of connection that is established with an IPsec VPN. Cisco AnyConnect VPN Client software is pushed (downloaded) and installed automatically on the PC of the remote user. The Cisco AnyConnect VPN Client uses SSL to provide the security of an IPsec VPN without the complexity required to install IPsec in your network and on remote devices. The following tasks are completed in this configuration:
•
•
•
•
•
•
•
•
•
Prerequisites
•
•
•
See the "Configuring the SSL VPN Gateway to Distribute CSD and Cisco AnyConnect VPN Client Package Files" section if you have not already prepared the SSL VPN gateway to distribute SSL VPN software.
Restrictions
Only Microsoft Windows 2000, Windows XP, Windows Vista, Apple-Mac, and Linux are supported on the remote client.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
DETAILED STEPS
Examples
Tunnel Filter Configuration
The following example, starting in global configuration mode, configures a deny access filter for any host from the 172.16.2/24 network:
Router(config)# access-list 101 deny ip 172.16.2.0 0.0.0.255 anyRouter(config)# webvpn context context1Router(config-webvpn-context)# policy group ONERouter(config-webvpn-group)# filter tunnel 101Router(config-webvpn-group)# endAddress Pool (Directly Connected Network) Configuration
The following example, starting in global configuration mode, configures the 192.168.1/24 network as an address pool:
Router(config)# ip local pool ADDRESSES 192.168.1.1 192.168.1.254Router(config)# webvpn context context1Router(config-webvpn-context)# policy group ONERouter(config-webvpn-group)# svc address-pool ADDRESSESRouter(config-webvpn-group)# endAddress Pool (Nondirectly Connected Network) Configuration
The following example, starting in global configuration mode, configures the 172.16.1/24 network as an address pool. Because the network is not directly connected, a local loopback interface is configured.
Router(config)# interface loopback 0Router(config-int)# ip address 172.16.1.126 255.255.255.0Router(config-int)# no shutdownRouter(config-int)# exitRouter(config)# ip local pool ADDRESSES 172.16.1.1 172.16.1.254Router(config)# webvpn context context1Router(config-webvpn-context)# policy group ONERouter(config-webvpn-group)# svc address-pool ADDRESSESRouter(config-webvpn-group)# endFull Tunnel Configuration
The following example, starting in global configuration mode, configures full Cisco AnyConnect VPN Client tunnel support on an SSL VPN gateway:
Router(config)# webvpn context context1
Router(config-webvpn-context)# policy group ONE
Router(config-webvpn-group)# functions svc-enabled
Router(config-webvpn-group)# functions svc-requiredRouter(config-webvpn-group)# svc default-domain cisco.comRouter(config-webvpn-group)# svc dns-server primary 192.168.3.1
Router(config-webvpn-group)# svc dns-server secondary 192.168.4.1Router(config-webvpn-group)# svc dpd-interval gateway 30
Router(config-webvpn-group)# svc dpd-interval client 300Router(config-webvpn-group)# svc homepage www.cisco.comRouter(config-webvpn-group)# svc keep-client-installed
Router(config-webvpn-group)# svc rekey method new-tunnel
Router(config-webvpn-group)# svc rekey time 3600Router(config-webvpn-group)# endWhat to Do Next
Proceed to the "Configuring Advanced SSL VPN Tunnel Features" section to see advanced Cisco AnyConnect VPN Client tunnel configuration information.
Configuring Advanced SSL VPN Tunnel Features
This section describes advanced Cisco AnyConnect VPN Client tunnel configurations. The following configuration steps are completed in this task:
•
•
•
Microsoft Internet Explorer Proxy Configuration—The SSL VPN gateway can be configured to pass or bypass Microsoft Internet Explorer (MSIE) proxy settings. Only HTTP proxy settings are supported by the SSL VPN gateway. MSIE proxy settings have no effect on any other supported browser.
Split Tunneling—Split tunnel support allows you to configure a policy that permits specific traffic to be carried outside of the Cisco AnyConnect VPN Client tunnel. Traffic is either included (resolved in tunnel) or excluded (resolved through the Internet service provider [ISP] or WAN connection). Tunnel resolution configuration is mutually exclusive. An IP address cannot be both included and excluded at the same time. Entering the local-lans keyword permits the remote user to access resources on a local LAN, such as network printer.
Prerequisites
•
•
Restrictions
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
DETAILED STEPS
Examples
Split DNS Configuration
The following example, starting in global configuration mode, configures the following DNS names to be resolved in the Cisco AnyConnect VPN Client tunnel:
Router(config)# webvpn context context1Router(config-webvpn-context)# policy group ONERouter(config-webvpn-group)# svc split dns www.example.com
Router(config-webvpn-group)# svc split dns myexample.comIncluding and Excluding IP Prefixes
The following example configures a list of IP addresses to be resolved over the tunnel (included) and a list to be resolved outside of the tunnel (excluded):
Router(config-webvpn-group)# svc split exclude 192.168.1.0 255.255.255.0Router(config-webvpn-group)# svc split include 172.16.1.0 255.255.255.0MSIE Proxy Configuration
The following example configures MSIE proxy settings:
Router(config-webvpn-group)# svc msie-proxy option auto
Router(config-webvpn-group)# svc msie-proxy exception www.example.com
Router(config-webvpn-group)# svc msie-proxy exception 10.20.20.1Router(config-webvpn-group)# svc msie-proxy server 10.10.10.1:80WINS Server Configuration
The following example configures primary and secondary WINS servers for the policy group:
Router(config-webvpn-group)# svc wins-server primary 172.31.1.1Router(config-webvpn-group)# svc wins-server secondary 172.31.2.1Router(config-webvpn-group)# svc wins-server secondary 172.31.3.1Router(config-webvpn-group)# endConfiguring VRF Virtualization
VRF Virtualization allows you to associate a traditional VRF with an SSL VPN context configuration. This feature allows you to apply different configurations and reuse address space for different groups of users in your organization.
Prerequisites
•
•
•
Restrictions
•
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
webvpn context name
Example:Router(config)# webvpn context context1
Enters WebVPN context configuration mode to configure the SSL VPN context.
Step 4
vrf-name name
Example:Router(config-webvpn-context)# vrf-name vrf1
Associates a VRF with an SSL VPN context.
Note
% IP VRF vrf1 configuration applied.% But please use Virtual-Template to configure VRF.See the "Configuring SSLVPN DVTI Support" section for the procedure to configure IP features using virtual template.
Configuring ACL Rules
To configure ACL rules at the application layer level for an individual user, perform the following steps.
The ACL rules can be overridden for an individual user when the user logs in to the gateway (using AAA policy attributes). If a user session has no ACL attribute configured, all application requests from that user session are permitted by default.
Prerequisites
Before configuring the ACL rules, you must have first configured the time range using the time-range command (this prerequisite is in addition to optionally configuring the time range, in the task table, as part of the permit or deny entries).
Restrictions
There is no limitation on the maximum number of filtering rules that can be configured for each ACL entry, but keeping the number below 50 should have no significant impact on router performance.
SUMMARY STEPS
1.
2.
3.
4.
5.
or
deny [url [any | url-string]] [ip | tcp | udp | http | https | cifs] [any | source-ip source-mask] [any | destination-ip destination-mask] [time-range time-range-name] [syslog]
6.
7.
8.
9.
DETAILED STEPS
Associating an ACL Attribute with a Policy Group
To associate an ACL attribute with a policy group, perform the following steps.
Note
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Monitoring and Maintaining ACLs
To monitor and maintain your ACL configuration, perform the following steps.
SUMMARY STEPS
1.
2.
DETAILED STEPS
Configuring SSO Netegrity Cookie Support for a Virtual Context
To configure SSO Netegrity cookie support for a virtual context, perform the following steps.
Prerequisites
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Associating an SSO Server with a Policy Group
To associate an SSO server with a policy group, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring URL Obfuscation (Masking)
To configure URL obfuscation (masking), perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Adding a CIFS Server URL List to an SSL VPN Context and Attaching It to a Policy Group
To add a CIFS server URL list to an SSL VPN context and attach it to a policy group, perform the following steps.
Prerequisites
Before adding a CIFS server URL list to an SSL VPN context, you must have already set up the Web VPN context using the webvpn context command, and you must be in WebVPN context configuration mode.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Configuring User-Level Bookmarks
To configure user-level bookmarks, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring FVRF
To configure FVRF so that the SSL VPN gateway is fully integrated into an MPLS network, perform the following steps.
Prerequisites
As the following configuration task shows, IP VRF must be configured before the FVRF can be associated with the SSL VPN gateway. For more information about configuring IP VRF, see the section "Configuring IP VRF (ip vrf command)" in the "Related Documents" section.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Disabling Full-Tunnel Cisco Express Forwarding
To disable full-tunnel Cisco Express Forwarding support, perform the following steps.
Note
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Configuring Automatic Authentication and Authorization
To configure automatic authentication and authorization so that a user needs to log in only one time, at login, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring SSL VPN Client-Side Certificate-Based Authentication
To configure SSL VPN client-side certificate-based authentication, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
DETAILED STEPS
Configuring a URL Rewrite Splitter
To configure a URL rewrite splitter, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Configuring a Backend HTTP Proxy
To configure a backend HTTP proxy, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring Stateless High Availability with HSRP for SSL VPN
To configure stateless high availability with HSRP for SSL VPN, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Configuring Internationalization
To configure multilanguage support messages initiated by the headend for SSL VPN clients, such as CSD and SVC, the following tasks are required or optional:
•
•
•
•
•
•
•
•
•
Generating the Template Browser Attribute File
To generate the template browser attribute file, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
webvpn create template browser-attribute device:
Example:Router# webvpn create template browser-attribute flash:
Generates the browser attribute template XML file (battr_tpl.xml).
Step 3
Copy the browser attribute file to another device on which you can edit the language being configured.
For an example of how to copy the file to your PC, see the "Example: Copying the Browser Attribute File to Another PC for Editing" section.
Step 4
Copy the edited file back to the storage device.
For an example of how to copy the edited file to a storage device, see the "Example: Copying the Edited File to flash" section.
What to Do Next
Proceed to the "Importing the Browser Attribute File" section.
Importing the Browser Attribute File
To import the browser attribute file from the storage device, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
What to Do Next
Proceed to the "Verifying That the Browser Attribute File Was Imported Correctly" section.
Verifying That the Browser Attribute File Was Imported Correctly
To verify that the browser attribute file was imported correctly, perform the following steps.
SUMMARY STEPS
1.
2.
DETAILED STEPS
What to Do Next
Proceed to the "Creating the Language File" section.
Creating the Language File
To create the language file, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
webvpn create template language device:
Example:Router# webvpn create template language flash:
Creates the language template file lang.js.
Note
Step 3
Copy the language lang.js file to a PC for editing.
For an example of how to copy the language file to another PC, see the "Example: Copying the Language File to Another PC for Editing" section.
Step 4
Copy the edited language lang.js file to the storage device.
For an example of how to copy the edited file to the storage device, see the "Example: Copying the Edited Language File to the Storage Device" section.
Step 5
webvpn create template language {japanese | customize language-name device:file}
Example:Router# webvpn create template language japanese
Creates templates for multilanguage support for messages initiated by the headend in an SSL VPN.
What to Do Next
Proceed to the "Importing the Language File" section.
Importing the Language File
To import the language file, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
What to Do Next
Proceed to the "Verifying That the Language File Was Imported Correctly" section.
Verifying That the Language File Was Imported Correctly
To verify that the language file was imported correctly, perform the following steps.
SUMMARY STEPS
1.
2.
DETAILED STEPS
What to Do Next
Proceed to the "Creating the URL List" section.
Creating the URL List
To create the URL list, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
webvpn create template url-list device:
Example:Router# webvpn create template url-list flash:
Creates the url-list template.
Step 3
Copy the XML file to a PC for editing.
For an example of how to copy an XML file to a PC for editing, see the "Examples: URL List" section.
Step 4
Copy the edited url-list XML file back to the storage device.
For an example of how to copy the edited url-list XML file back to a storage device, see the "Examples: URL List" section.
What to Do Next
Proceed to the "Importing the File into the URL List and Binding It to a Policy Group" section.
Importing the File into the URL List and Binding It to a Policy Group
To import the file into the URL list and bind it to a policy group, perform the following steps.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
What to Do Next
Proceed to the "Verifying That the URL List File Was Bound Correctly to the Policy Group" section.
Verifying That the URL List File Was Bound Correctly to the Policy Group
To verify that the URL list file was bound correctly to the policy group, perform the following steps.
SUMMARY STEPS
1.
2.
DETAILED STEPS
Configuring a Virtual Template
A virtual template enables SSL VPN to interoperate with IP features such as NAT, firewall, and policy-based routing.
Prerequisites
•
•
•
Restrictions
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Configuring SSLVPN DVTI Support
•
•
•
Configuring per-Tunnel Virtual Templates
Perform this task to configure per-tunnel virtual templates. This task describes how to provide DVTI support for an SSL VPN.
A virtual template is configured with the desired IP features. This virtual template is configured in a WebVPN context on a per-tunnel or per-user basis (because a user will have only one tunnel established at a time). Hence the virtual template configuration is applied on a per-tunnel basis for each SSL VPN full tunnel established in the WebVPN context. This configuration also helps you apply a distinct configuration to each user connecting to the WebVPN context using a AAA server.
The distinct per-user policy configuration is downloaded from the AAA server. This configuration includes group policy attributes and ACLs, and is applied to every user connecting to the WebVPN context on a per-user basis.
If a per-user attribute such as ACL is configured both on the AAA server and the virtual template, then the attribute configured on the AAA server takes precedence. The users logged in to the client computer will have the ACL configuration from the AAA server but will have other configurations, such as firewalls and VRF, from the virtual template. That is, the configuration applied to the users will be a combination of the virtual template configuration and the configuration available on the AAA server.
For example, if IP features such as firewalls, ACLs, and VRF are configured in a virtual template and user attributes such as ACLs are configured on the AAA server, the attributes configured on the AAA server take precedence. The users logged in to the client computer will have the ACL configuration from the AAA server but will have firewall and VRF configurations from the virtual template. That is, the configuration applied to the users will be a combination of virtual templates and AAA, where AAA attributes have a higher priority when there is a configuration conflict.
See the "Configuring RADIUS Attribute Support for SSL VPN" section for a list of AAA attributes that support SSL VPN.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Troubleshooting Tips
Use the following commands to debug any errors that you may encounter when you configure the per-Tunnel Virtual Templates:
•
•
Configuring per-Context Virtual Templates
This task describes how to configure virtual tunnel interface support on a per-context basis.
A virtual template is configured with IP features such as NAT, firewalls, and PBR. This virtual template is configured in a WebVPN context, and enables SSL VPN to interoperate with the IP features configured. This configuration is applied to all users connecting to that WebVPN context.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Troubleshooting Tips
Use the following commands to debug any errors that you may encounter when you configure the per-Context Virtual Templates:
•
•
Configuring SSL VPN Phase-4 Features
•
•
•
•
Configuring the Start Before Logon Functionality
Perform this task to configure the Start Before Logon (SBL) functionality.
In order to import the AnyConnect profile to the Cisco IOS headend, the administrator must download the AnyConnect profile from an AnyConnect client (this profile comes by default with AnyConnect), update the UseStartBeforeLogin XML tag available in the profile file to inform AnyConnect to support SBL, and then import the modified profile into the Cisco IOS software.
The secure gateway administrator maintains the AnyConnect profile file and distributes it to the clients.
Following is an extract of the Cisco IOS AnyConnect VPN client profile XML file:
<?xml version="1.0" encoding="UTF-8"?> <AnyConnectProfile xmlns="http://schemas.xmlsoap.org/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.xmlsoap.org/encoding/ AnyConnectProfile.xsd"> <ClientInitialization> <UseStartBeforeLogon UserControllable="false">true</UseStartBeforeLogon> </ClientInitialization>You can select the hosts from the above list.
<ServerList><HostEntry> <HostName>abc</HostName> <HostAddress>abc.cisco.com</HostAddress> </HostEntry> </ServerList> </AnyConnectProfile>Data is required to connect to a specific host.
The SBL functionality connects the client PC to the enterprise network even before the users log into the PC. This functionality allows the administrator to run the logon scripts even if the user is not connected to the enterprise network. This is useful for a number of deployment scenarios where the user is outside the physical corporate network and cannot access the resources until his system is connected to the corporate network.
Only an administrator can enable or disable SBL. The end users accessing the client PC are not allowed to enable or disable this functionality.
Prerequisites
SSL VPN must have the ability to import profiles on the Cisco IOS software and must be able to send the AnyConnect profile to the client.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
DETAILED STEPS
Troubleshooting Tips
Use the debug webvpn cookie command to debug any errors that you may encounter when you configure the SBL functionality.
Configuring Split ACL Support
Perform this task to configure split ACL support.
When the tunnel is active, Cisco IOS SSL VPN supports the split include and split exclude commands to filter and classify the traffic based on IP. Because the Cisco IOS software supports ACLs to classify the traffic, standard ACL support is provided to filter the traffic.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
DETAILED STEPS
Configuring IP NetMask Functionality
Perform this task to configure IP NetMask functionality.
The IP NetMask functionality provides SVC or AnyConnect client provision to configure the network mask when the ip local pool command is configured on the router. This mask must be a classless mask.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Using SSL VPN clear Commands
This section describes clear commands that are used to perform the following tasks:
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Verifying SSL VPN Configurations
This section describes how to use show commands to verify the following:
•
•
•
•
•
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
DETAILED STEPS
Using SSL VPN Debug Commands
To monitor and manage your SSL VPN configurations, perform the following steps.
SUMMARY STEPS
1.
2.
DETAILED STEPS
Configuration Examples for SSL VPN
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Example: Configuring a Generic SSL VPN Gateway
The following output example shows that a generic SSL VPN gateway has been configured in privileged EXEC mode:
Router# show running-configwebvpn gateway SSL_gateway2ip address 10.1.1.1. port 442ssl trustpoint TP_self_signed _4138349635inservice!webvpn context SSL_gateway2ssl authenticate verify all!!policy group defaultdefault-group-policy defaultgateway SSL_gateway2inserviceExample: Configuring an ACL
The following output example shows the ACL is "acl1." It has been associated with policy group "default."
Router# show running-configwebvpn context context1ssl authenticate verify all!acl "acl1"error-msg "warning!!!..."permit url "http://www.example1.com"deny url "http://www.example2.com"permit http any any!nbns-list l1nbns-server 10.1.1.20!cifs-url-list "c1"heading "cifs-url"url-text "SSL VPN-SERVER2" url-value "\\SSL VPN-SERVER2"url-text "SSL-SERVER2" url-value "\\SSL-SERVER2"!policy group defaultacl "acl1"cifs-url-list "c1"nbns-list "l1"functions file-accessfunctions file-browsefunctions file-entrydefault-group-policy defaultgateway publicinservice!Example: Configuring HTTP Proxy
The following output example shows that HTTP proxy has been configured and that the portal (home) page from URL "http://www.example.com" will automatically download the home page of the user:
Router# show running-configwebvpn context myContextssl authenticate verify all!!port-forward "email"local-port 20016 remote-server "ssl-server1.SSL example1.com" remote-port 110 description "POP-ssl-server1"!policy group myPolicyport-forward "email" auto-download http-proxy proxy-url "http://www.example.com"inserviceExample: Configuring Microsoft File Shares for Clientless Remote Access
NBNS Server List Example
The following example, starting in global configuration mode, configures a server list for NBNS resolution:
Router(config)# webvpn context context1Router(config-webvpn-context)# nbns-list SERVER_LISTRouter(config-webvpn-nbnslist)# nbns-server 172.16.1.1 master
Router(config-webvpn-nbnslist)# nbns-server 172.16.2.2 timeout 10 retries 5
Router(config-webvpn-nbnslist)# nbns-server 172.16.3.3 timeout 10 retries 5Router(config-webvpn-nbnslist)# exitFile Share Permissions Example
The following example attaches the server list to and enables full file and network access permissions for policy group ONE:
Router(config-webvpn-context)# policy group ONERouter(config-webvpn-group)# nbns-list SERVER_LISTRouter(config-webvpn-group)# functions file-access
Router(config-webvpn-group)# functions file-browse
Router(config-webvpn-group)# functions file-entryRouter(config-webvpn-group)# endExample: Configuring Citrix Application Support for Clientless Remote Access
The following example, starting in global configuration mode, enables Citrix application support for remote users with a source IP address in the 192.168.1.0/24 network:
Router(config)# access-list 100 permit ip 192.168.1.0 0.255.255.255 anyRouter(config)# webvpn context context1Router(config-webvpn-context)# policy group ONERouter(config-webvpn-group)# citrix enabledRouter(config-webvpn-group)# filter citrix 100Example: Configuring Application Port Forwarding
The following example, starting in global configuration mode, configures port forwarding for well-known e-mail application port numbers:
Router(config)# webvpn context context1Router(config-webvpn-context)# port-forward EMAILRouter(config-webvpn-port-fwd)# local-port 30016 remote-server mail1.company.com remote-port 110 description POP3Router(config-webvpn-port-fwd)# local-port 30017 remote-server mail2.company.com remote-port 25 description SMTPRouter(config-webvpn-port-fwd)# local-port 30018 remote-server mail3.company.com remote-port 143 description IMAPRouter(config-webvpn-port-fwd)# exitRouter(config-webvpn-context)# policy group ONERouter(config-webvpn-group)# port-forward EMAILRouter(config-webvpn-group)# endExample: Configuring VRF Virtualization
The following example, starting in global configuration mode, associates the VRF under the SSL VPN context configuration:
Router(config)# ip vrf vrf1Router(config-vrf)# rd 10.100.100.1:1Router(config-vrf)# exitRouter(config)# webvpn context context1Router(config-webvpn-context)# policy group group1Router(config-webvpn-group)# exitRouter(config-webvpn-context)# default-group-policy policy1Router(config-webvpn-context)# vrf-name vrf2Router(config-webvpn-context)# end
Note
% IP VRF vrf1 configuration applied.% But please use Virtual-Template to configure VRF.See the "Examples: SSL VPN DVTI Support" section for an example on how to use a virtual template to configure a VRF.
Example: RADIUS Accounting for SSL VPN Sessions
The following output example shows that RADIUS accounting has been configured for SSL VPN user sessions:
Router# show running-configversion 12.4service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname host1!aaa new-model!!aaa accounting network SSL VPNaaa start-stop group radiusaaa accounting update periodic 1aaa session-id commonip subnet-zeroip cef!!no ip domain lookupip domain name cisco.comip name-server 172.16.2.133ip name-server 172.16.11.48!line con 0exec-timeout 0 0line aux 0line vty 0 4!!webvpn gateway GW1ip address 172.19.216.141 port 443inservice!webvpn gateway SSL VPNno inservice!webvpn install svc flash:/webvpn/svc.pkgwebvpn aaa accounting-list SSL VPNaaa!webvpn context Default_contextssl encryptionssl authenticate verify all!no inservice!!Example: URL Obfuscation (Masking)
The following output example shows that URL obfuscation (masking) has been configured for policy group "gp_urlobf."
Router: show running-config!!policy group gp_urlobfmask-urlsdefault-group-policy gp_urlobfgateway gw domain dominservice!!Example: Adding a CIFS Server URL List and Attaching It to a Policy List
The following output example shows that the CIFS server URLs "SSLVPN-SERVER2" and "SSL-SERVER2" have been added as portal page URLs to which a user has access. The output also shows that the two servers have been attached to a policy group.
webvpn context context_1ssl authenticate verify all!acl "acl1"error-msg "warning!!!..."permit url "http://www.example1.com"deny url "http://www.example2.com"permit http any any!nbns-list l1nbns-server 10.1.1.20!cifs-url-list "c1"heading "cifs-url"url-text "SSLVPN-SERVER2" url-value "\\SSLVPN-SERVER2"url-text "SSL-SERVER2" url-value "\\SSL-SERVER2"!policy group defaultacl "acl1"cifs-url-list "c1"nbns-list "l1"functions file-accessfunctions file-browsefunctions file-entrydefault-group-policy defaultgateway publicinservice!Example: Typical SSL VPN Configuration
The following output is an example of an SSL VPN configuration that includes most of the features that are available using SSL VPN:
Router# show running-confighostname sslvpn!!aaa new-model!!aaa authentication login default local group radius!!crypto pki trustpoint Gatewayenrollment selfsignedip-address 192.168.22.13revocation-check crlrsakeypair keys 1024 1024!!crypto pki certificate chain Gatewaycertificate self-signed 02!!interface Loopback0ip address 10.10.10.1 255.255.255.0!!interface GigabitEthernet0/1ip address 192.168.22.14 255.255.255.0 secondaryip address 192.168.22.13 255.255.255.0duplex autospeed automedia-type rj45!!ip local pool svc-pool 10.10.10.100 10.10.10.110!!ip radius source-interface FastEthernet1/1!!webvpn gateway ssl-vpnip address 192.168.22.13 port 443http-redirect port 80ssl trustpoint Gatewayinservice!! The following line is required for SSLVPN Client.webvpn install svc flash:/webvpn/svc.pkg!! The following line is required for Cisco Secure Desktop.webvpn install csd flash:/webvpn/sdesktop.pkg!webvpn context ssl-vpnssl authenticate verify all!url-list "sslvpn-dt"url-text "sslvpn-dt" url-value "http://10.1.1.40"url-text "Exchange Server" url-value "http://10.1.1.40/exchange"!sso-server "netegrity"web-agent-url "http://10.1.1.37/vpnauth/"secret-key "sslvpn1"retries 3timeout 15!nbns-list cifsnbns-server 10.1.1.40!port-forward "mail_test"local-port 30016 remote-server "example1.com" remote-port 143 description "IMAP-test"local-port 30017 remote-server "example2.com" remote-port 110 description "POP3-test"local-port 30018 remote-server "example3.com" remote-port 25 description "SMTP-test"!policy group default! The following line applies the URL list.url-list "sslvpn-dt"! The following line applies TCP port forwarding.port-forward "mail_test"! The following line applies CIFS.nbns-list "cifs"! The following line enables CIFS functionality.functions file-access! The following line enables CIFS functionality.functions file-browse! The following line enables CIFS functionality.functions file-entry! The following line enables SSLVPN Client.functions svc-enabled! The following line enables clientless Citrix.citrix enableddefault-group-policy default! The following line maps this context to the virtual gateway and defines the domain to use.gateway ssl-vpn domain sslvpn! The following line enables Cisco Secure Desktop.csd enableinservice!!endExample: Cisco Express Forwarding-Processed Packets
The following output example from the show webvpn stats command shows information about Cisco Express Forwarding-processed packets:
Router# show webvpn statsUser session statistics:Active user sessions : 56 AAA pending reqs : 0Peak user sessions : 117 Peak time : 00:13:19Active user TCP conns : 0 Terminated user sessions : 144Session alloc failures : 0 Authentication failures : 0VPN session timeout : 0 VPN idle timeout : 0User cleared VPN sessions : 0 Exceeded ctx user limit : 0Exceeded total user limit : 0Client process rcvd pkts : 1971 Server process rcvd pkts : 441004Client process sent pkts : 921291 Server process sent pkts : 2013Client CEF received pkts : 1334 Server CEF received pkts : 951610Client CEF rcv punt pkts : 0 Server CEF rcv punt pkts : 779Client CEF sent pkts : 1944439 Server CEF sent pkts : 0Client CEF sent punt pkts : 21070 Server CEF sent punt pkts : 0Example: Multiple AnyConnect VPN Client Package Files
The following example shows that three AnyConnect VPN Client packages have been installed to a gateway and shows the resulting show webvpn install command output:
Router(config)# webvpn install svc vpn1_i386-Release-2.0.0077-k9.pkg sequence 6Router(config)# webvpn install svc vpn2_powerpc-Release-2.0.0077-k9.pkg sequence 8Router(config)# webvpn install svc svc_1.pkg sequence 4Router# show webvpn install status svcSSLVPN Package SSL-VPN-Client version installed:CISCO STC win2k+2,0,0148Fri 12/29/2006 19:13:56.37SSLVPN Package SSL-VPN-Client version installed:CISCO STC Darwin_i3862,0,0Wed Nov 8 04:01:57 MST 2006SSLVPN Package SSL-VPN-Client version installed:CISCO STC Darwin_powerpc2,0,0Wed Nov 8 03:54:50 MST 2006The following example shows that three AnyConnect VPN client packages have been configured and typical output from the show-running config command:
Router# show running-config | begin webvpnwebvpn install svc flash:/webvpn/svc_4.pkg sequence 4!webvpn install svc flash:/webvpn/svc_6.pkg sequence 6!webvpn install svc flash:/webvpn/svc_9.pkg sequence 9Example: Local Authorization
The following example shows that local authorization has been configured:
aaa new-model!aaa authentication login default localaaa authorization network default local!aaa attribute list l2attribute type banner "user2"!aaa attribute list l1attribute type banner "user1"attribute type urllist-name "my-url-list"!username user1 password 0 passwd1username user1 aaa attribute list l1username user2 password 0 passwd2username user2 aaa attribute list l2!webvpn context bestssl authenticate verify all!url-list "my-url-list"heading "external url"url-text "example" url-value "http://www.example.com"!policy group defaultdefault-group-policy defaultaaa authorization list defaultgateway public domain d1inserviceExample: URL Rewrite Splitter
The following example shows that URL mangling has been configured for a specific host and IP address. The unmatched action has been defined as direct access.
webvpn context e1!url rewritehost "www.example.com"ip 10.1.0.0 255.255.0.0unmatched-action direct-access!Example: Backend HTTP Proxy
The following example shows that a backend HTTP proxy has been configured:
webvpn context e1!policy group g1http proxy-server "192.0.2.0" port 2034default-group-policy g1Example: Stateless High Availability with HSRP
Figure 15 shows the topology of a typical stateless high availability with HSRP setup. Router 1 and Router 2 are configured for HSRP on gateway Webvpn. The example following Figure 15 shows the actual configuration.
Figure 15 Stateless High Availability with HSRP Setup
Router 1 Configuration
Router# configure terminalRouter(config)# interface gateway 0/1Router(config-if)# standby 0 ip 10.1.1.1Router(config-if)# standby 0 name SSLVPNRoute(config-if)# exitRouter(config)# webvpn gateway WebvpnRouter(config-webvpn-gateway)# ip address 10.1.1.1 port 443 standby SSLVPNRouter 2 Configuration
Router# configure terminalRouter(config)# interface gateway 0/0Router(config-if)# standby 0 ip 10.1.1.1Router(config-if)# standby 0 name SSLVPN2Router(config-if)# exitRouter(config)# webvpn gateway WebvpnRouter(config-webvpn-gateway)# ip address 10.1.1.1 port 443 standby SSLVPNigh2Examples: Internationalization
The following configuration and output examples display various aspects of the Internationalization feature. This section contains the following examples:
•
•
•
•
•
•
•
Example: Generated Browser Attribute Template
The following is an example of a generated browser attribute template:
<?xml version="1.0" encoding="utf-8"?><!--- Template file for browser attributes import<color> - primary color<scolor> - secondary color<tcolor> - text color<stcolor> - secondary text color<lmsg> - login message<title> - browser title<ticolor> - title colorDefault value will be used if the field is not definedCopyright (c) 2007-2008 by Cisco Systems, Inc. All rights reserved.--><settings><color>#003333</color><scolor>#336666</scolor><tcolor>white</tcolor><stcolor>black</stcolor><lmsg>Welcome to<p>Cisco Systems WebVPN Service</lmsg><title>WebVPN Service</title><ticolor>#003333</ticolor></settings>Example: Copying the Browser Attribute File to Another PC for Editing
The following example shows how to copy a browser attribute file to another PC for editing:
Router# copy flash: tftp:Source filename [battr_tpl.xml]?Address or name of remote host []? 10.1.1.30Destination filename [battr_tpl.xml]?!!677 bytes copied in 0.004 secs (169250 bytes/sec)Example: Copying the Edited File to flash
The following example shows how to copy an edited attribute file to flash:
Router# copy tftp://directory/edited_battr_tpl.xml flash:Example: Output Showing That the Edited File Was Imported
The following show running-config output shows that the browser attribute file was correctly copied to flash:
Router# show running-configwebvpn context gbrowser-attribute import flash:battr_tpl.xmlssl authenticate verify allExample: Copying the Language File to Another PC for Editing
The following example shows how to copy a language file to another PC for editing:
Router# copy flash: tftp:Source filename [lang.js]?Address or name of remote host []? 10.1.1.30Destination filename [lang.js]?!!10649 bytes copied in 0.028 secs (380321 bytes/sec)Example: Copying the Edited Language File to the Storage Device
The following example shows how to copy the edited language file to flash:
Router# copy tftp://directory/edited_lang.js flash:Example: Language Template Created
The following show running-config command output shows that the language file "lang.js" has been imported correctly:
Router# show running-configpolicy group defaultfunctions file-accessfunctions file-browsefunctions file-entryfunctions svc-enabledmask-urlssvc address-pool "mypool"svc keep-client-installedsvc split include 10.1.1.0 255.255.255.0default-group-policy defaultgateway glanguage customize mylang flash:lang.jsinserviceExamples: URL List
The following example shows that the URL list template file has been copied to another PC for editing:
Router# copy flash: tftp:Source filename [url_list_tpl.xml]?Address or name of remote host []? 10.1.1.30Destination filename [url_list_tpl.xml]The following example shows that the URL template file has been copied to flash:
Router# copy tftp://directory/edited_url_list_tpl.xml flash:The following show running-config command output shows that URL list file has been imported into the url-list and that it has been bound to the policy group:
Router# show running-configpolicy group defaulturl-list "test"functions file-accessfunctions file-browsefunctions file-entryfunctions svc-enabledmask-urlssvc address-pool "mypool"svc keep-client-installedsvc split include 10.1.1.0 255.255.255.0default-group-policy defaultgateway glanguage customize mylang flash:lang.jsinserviceExamples: Virtual Template
The following configuration and output examples display various aspects of the Virtual Template feature. The following example, starting in global configuration mode, creates a virtual template and associates it with an SSL VPN context configuration. It also configures the virtual template for VRF and NAT:
Router(config)# interface virtual-template 100Router(config-if)# ip unnumbered GigabitEthernet 0/0Router(config-if)# ip vrf forwarding vrf1Router(config-if)# ip nat insideRouter(config-if)# exitRouter(config)# webvpn context context1Router(config-webvpn-context)# virtual-template 100Router(config-webvpn-context)# exitThe following example creates a virtual template and associates it with a security zone:
Router(config)# interface virtual-template 200Router(config-if)# ip unnumbered GigabitEthernet 0/0Router(config-if)# zone-member security vpnRouter(config-if)# exitRouter(config)# webvpn context context2Router(config-webvpn-context)# virtual-template 200Router(config-webvpn-context)# exitExamples: SSL VPN DVTI Support
•
•
Examples: Configuring per-Tunnel Virtual Templates
Figure 16 shows an example network where remote users User1 and User2 belong to a context called Context1, User3 belongs to a context called Context2, and they connect to the SSL VPN gateway and access the backend server in the corporate network.
Figure 16 Topology Showing a per-Tunnel Virtual Template
•
•
Example: Configuring in the per-Tunnel Context Using Virtual Templates
The following example shows how to apply VRF, a firewall policy, and ACLs to each user based on the virtual template configuration.
If the VRF, firewall policy, and ACL features are configured in the virtual template and user policies are not configured on the AAA server, then only the IP features configured in the virtual template are applied to the users. In this example, User1 and User2 belonging to Context1 have zone1, vrf1, and ACL 1 configured whereas User3 belonging to Context2 has zone3, vrf3, and ACL 3 configured. Hence, different users have different IP features configured.
Virtual Template for User1 and User2
configure terminalinterface virtual-template 1zone-member security zone1ip vrf forwarding vrf1ip access-group 1 inip unnumbered GigabitEthernet 0/1Virtual Template for User3
configure terminalinterface virtual-template 3zone-member security zone3ip vrf forwarding vrf3ip access-group 3 inip unnumbered GigabitEthernet 0/1WebVPN Context for User1 and User2
configure terminalwebvpn context context1virtual-template 1 tunnelinserviceWebVPN Context for User3
configure terminalwebvpn context context2virtual-template 3 tunnelinserviceExample: Configuring in the per-Tunnel Context Using Virtual Templates and a AAA Server
The following example shows how to apply the IP feature configuration to the users based on the user-specific configuration available on the AAA server. The user-specific attributes configured on the AAA server are applied to the users when an SSL VPN session establishes a virtual tunnel. The configuration applied to the users will be a combination of the configurations in the virtual template and the AAA server, where AAA attributes have a higher priority when there is a configuration conflict.
In this example, ACL 1 is configured for User1, ACL 2 is configured for User2, and ACL 3 is configured for User3 on the AAA server using the inacl attribute. Even though ACL 4 is applied to all the users in the virtual template, User1 has ACL 1, User2 has ACL 2, and User3 has ACL 3 configured along with zone and VRF configurations available in the virtual template.
Virtual Template for User1 and User2
configure terminalinterface virtual-template 1zone-member security zone1ip vrf forwarding vrf1ip access-group 4 inip unnumbered GigabitEthernet 0/1Virtual Template for User3
configure terminalinterface virtual-template 3zone-member security zone3ip vrf forwarding vrf3ip access-group 4 inip unnumbered GigabitEthernet 0/1WebVPN Context for User1 and User2
configure terminalwebvpn context context1virtual-template 1 tunnelinserviceWebVPN Context for User3
configure terminalwebvpn context context2virtual-template 3 tunnelinservice
Note
Example: Configuring per-Context Virtual Templates
Figure 17 shows remote users User1 and User2 belonging to context1 and User3 belonging to context2, connecting to the SSL VPN gateway and accessing the backend server in the corporate network. Here, the IP feature configuration is applied to each user based on the configuration applied to the WebVPN context of the user.
Figure 17 Topology Showing a per-Context Virtual Template
The following example shows how to apply VRF and a firewall policy to each user based on the WebVPN context of the user. In this example, User1 and User 2 connected to Context1 have zone1 and vrf1 configured on the virtual template 1, and User3 connected to Context2 has zone2 and vrf2 configured on virtual template 2.
Virtual Template for User1
configure terminalinterface virtual-template 1zone-member security zone1ip vrf forwarding vrf1ip unnumbered GigabitEthernet 0/1Virtual Template for User2
configure terminalinterface virtual-template 2zone-member security zone2ip vrf forwarding vrf2ip unnumbered GigabitEthernet 0/1WebVPN Context for User1
configure terminalwebvpn context context1virtual-template 1inserviceWebVPN Context for User2
configure terminalwebvpn context context2virtual-template 2inservice
Note
Examples: SSL VPN Phase-4 Features
•
•
•
Example: Configuring the Start Before Logon Functionality
The following example shows how to configure SBL functionality:
enableconfigure terminalwebvpn import svc profile profile1 flash:newNamepolicy group group1svc profile profile1endExample: Configuring Split ACL Support
The following example shows how to configure split ACL support:
enableconfigure terminalip access-list standard 1permit 10.0.0.1deny 10.0.0.2exitwebvpn context context1policy group policy1svc split include acl 1endExample: Configuring IP NetMask Functionality
The following example shows how to configure IP netmask functionality:
enableconfigure terminalwebvpn context context1policy group policy1svc address-pool pool1 netmask 255.255.0.0endExamples: Debug Command Output
Example: Configuring SSO
The following output example displays ticket creation, session setup, and response handling information for an SSO configuration:
Router# debug webvpn sso*Jun 12 20:37:01.052: WV-SSO: Redirect to SSO web agent URL - http://example.examplecompany.com/vpnauth/*Jun 12 20:37:01.052: WV_SSO: Set session cookie with SSO redirect*Jun 12 20:37:01.056: WV-SSO: Set SSO auth flag*Jun 12 20:37:01.056: WV-SSO: Attach credentials - building auth ticket*Jun 12 20:37:01.060: WV-SSO: user: [user11], secret: [secret123], version: [1.0], login time: [BCEFC86D], session key: [C077F97A], SHA1 hash : [B07D0A924DB33988D423AE9F937C1C5A66404819]*Jun 12 20:37:01.060: WV-SSO: auth_ticket : user11:1.0@C077F97A@BCEFC86D@B07D0A924DB33988D423AE9F937C1C5A66404819*Jun 12 20:37:01.060: WV-SSO: Base64 credentials for the auth_ticket: dXNlcjExOjEuMEBDMDc3Rjk3QUBCQ0VGQzg2REBCMDdEMEE5MjREQjMzOTg4RDQyM0FFOUY5MzdDMUM1QTY2NDA0OD E5*Jun 12 20:37:01.060: WV-SSO: Decoded credentials = user11:1.0@C077F97A@BCEFC86D@B07D0A924DB33988D423AE9F937C1C5A66404819*Jun 12 20:37:01.060: WV-SSO: Starting SSO request timer for 15-second*Jun 12 20:37:01.572: WV-SSO: SSO auth response rcvd - status[200]*Jun 12 20:37:01.572: WV-SSO: Parsed non-SM cookie: SMCHALLENGE*Jun 12 20:37:01.576: WV-SSO: Parsed SMSESSION cookie*Jun 12 20:37:01.576: WV-SSO: Sending logon page after SSO auth successExamples: Show Command Output
•
•
•
•
•
•
•
•
•
Example: show webvpn context
The following is sample output from the show webvpn context command:
Router# show webvpn contextCodes: AS - Admin Status, OS - Operation StatusVHost - Virtual HostContext Name Gateway Domain/VHost VRF AS OS------------ ------- ------------ ------- ---- --------Default_context n/a n/a n/a down downcon-1 gw-1 one - up upcon-2 - - - down downExample: show webvpn context name
The following is sample output from the show webvpn context command, entered with the name of a specific SSL VPN context:
Router# show webvpn context context1Admin Status: upOperation Status: upCSD Status: DisabledCertificate authentication type: All attributes (like CRL) are verifiedAAA Authentication List not configuredAAA Authentication Domain not configuredDefault Group Policy: PG_1Associated WebVPN Gateway: GW_ONEDomain Name: DOMAIN_ONEMaximum Users Allowed: 10000 (default)NAT Address not configuredVRF Name not configuredExample: show webvpn gateway
The following is sample output from the show webvpn gateway command:
Router# show webvpn gatewayGateway Name Admin Operation------------ ----- ---------GW_1 up upGW_2 down downExample: show webvpn gateway name
The following is sample output from the show webvpn gateway command, entered with a specific SSL VPN gateway name:
Router# show webvpn gateway GW_1Admin Status: upOperation Status: upIP: 10.1.1.1, port: 443SSL Trustpoint: TP-self-signed-26793562Example: show webvpn install file
The following is sample output from the show webvpn install command, entered with the file keyword:
Router# show webvpn install file \webvpn\stc\version.txtSSL VPN File \webvpn\stc\version.txt installed:CISCO STC win2k+ 1.0.01,1,0,116Fri 06/03/2005 03:02:46.43Example: show webvpn install package svc
The following is sample output from the show webvpn install command, entered with the package svc keywords:
Router# show webvpn install package svcSSL VPN Package SSL-VPN-Client installed:File: \webvpn\stc\1\binaries\detectvm.class, size: 555File: \webvpn\stc\1\binaries\java.htm, size: 309File: \webvpn\stc\1\binaries\main.js, size: 8049File: \webvpn\stc\1\binaries\ocx.htm, size: 244File: \webvpn\stc\1\binaries\setup.cab, size: 176132File: \webvpn\stc\1\binaries\stc.exe, size: 94696File: \webvpn\stc\1\binaries\stcjava.cab, size: 7166File: \webvpn\stc\1\binaries\stcjava.jar, size: 4846File: \webvpn\stc\1\binaries\stcweb.cab, size: 13678File: \webvpn\stc\1\binaries\update.txt, size: 11File: \webvpn\stc\1\empty.html, size: 153File: \webvpn\stc\1\images\alert.gif, size: 2042File: \webvpn\stc\1\images\buttons.gif, size: 1842File: \webvpn\stc\1\images\loading.gif, size: 313File: \webvpn\stc\1\images\title.gif, size: 2739File: \webvpn\stc\1\index.html, size: 4725File: \webvpn\stc\2\index.html, size: 325File: \webvpn\stc\version.txt, size: 63Total files: 18Example: show webvpn install status svc
The following is sample output from the show webvpn install command, entered with the status svc keywords:
Router# show webvpn install status svcSSL VPN Package SSL-VPN-Client version installed:CISCO STC win2k+ 1.0.01,0,2,127Fri 07/22/2005 12:14:45.43Example: show webvpn nbns context all
The following sample output from the show webvpn nbns command, entered with the context all keywords:
Router# show webvpn nbns context allNetBIOS name IP Address Timestamp0 total entriesNetBIOS name IP Address Timestamp0 total entriesNetBIOS name IP Address Timestamp0 total entries
Example: show webvpn policy
The following is sample output from the show webvpn policy command:
Router# show webvpn policy group ONE context allWEBVPN: group policy = ONE ; context = SSL VPNidle timeout = 2100 secsession timeout = 43200 seccitrix disableddpd client timeout = 300 secdpd gateway timeout = 300 seckeep SSL VPN client installed = disabledrekey interval = 3600 secrekey method =lease duration = 43200 secWEBVPN: group policy = ONE ; context = SSL VPN_TWOidle timeout = 2100 secsession timeout = 43200 seccitrix disableddpd client timeout = 300 secdpd gateway timeout = 300 seckeep SSL VPN client installed = disabledrekey interval = 3600 secrekey method =lease duration = 43200 secExample: show webvpn policy (with NTLM Disabled)
The following is sample output from the show webvpn policy command. NTLM authentication has been disabled.
Router# show webvpn policy group ntlm context ntlmWEBVPN: group policy = ntlm; context = ntlmurl list name = "ntlm-server"idle timeout = 2100 secsession timeout = 43200 secfunctions =httpauth-disabledfile-accesssvc-enabledcitrix disableddpd client timeout = 300 secdpd gateway timeout = 300 seckeep SSL VPN client installed = disabledrekey interval = 3600 secrekey method =lease duration = 43200 secExample: show webvpn session
The following is sample output from the show webvpn session command. The output is filtered to display user session information for only the specified context.
Router# show webvpn session context SSL VPNWebVPN context name: SSL VPNClient_Login_Name Client_IP_Address No_of_Connections Created Last_Useduser1 10.2.1.220 2 04:47:16 00:01:26user2 10.2.1.221 2 04:48:36 00:01:56Example: show webvpn session user
The following is sample output from the show webvpn session command. The output is filtered to display session information for a specific user.
Router# show webvpn session user user1 context allWebVPN user name = user1 ; IP address = 10.2.1.220; context = SSL VPNNo of connections: 0Created 00:00:19, Last-used 00:00:18CSD enabledCSD Session PolicyCSD Web Browsing AllowedCSD Port Forwarding AllowedCSD Full Tunneling DisabledCSD FILE Access AllowedUser Policy ParametersGroup name = ONEGroup Policy Parametersurl list name = "Cisco"idle timeout = 2100 secsession timeout = 43200 secport forward name = "EMAIL"tunnel mode = disabledcitrix disableddpd client timeout = 300 secdpd gateway timeout = 300 seckeep stc installed = disabledrekey interval = 3600 secrekey method = ssllease duration = 3600 secExample: show webvpn stats
The following is sample output from the show webvpn stats command entered with the detail and context keywords:
Router# show webvpn stats detail context SSL VPNWebVPN context name : SSL VPNUser session statistics:Active user sessions : 0 AAA pending reqs : 0Peak user sessions : 0 Peak time : neverActive user TCP conns : 0 Terminated user sessions : 0Session alloc failures : 0 Authentication failures : 0VPN session timeout : 0 VPN idle timeout : 0User cleared VPN sessions: 0 Exceeded ctx user limit : 0CEF switched packets - client: 0 , server: 0CEF punted packets - client: 0 , server: 0Mangling statistics:Relative urls : 0 Absolute urls : 0Non-http(s) absolute urls: 0 Non-standard path urls : 0Interesting tags : 0 Uninteresting tags : 0Interesting attributes : 0 Uninteresting attributes : 0Embedded script statement: 0 Embedded style statement : 0Inline scripts : 0 Inline styles : 0HTML comments : 0 HTTP/1.0 requests : 0HTTP/1.1 requests : 0 Unknown HTTP version : 0GET requests : 0 POST requests : 0CONNECT requests : 0 Other request methods : 0Through requests : 0 Gateway requests : 0Pipelined requests : 0 Req with header size >1K : 0Processed req hdr bytes : 0 Processed req body bytes : 0HTTP/1.0 responses : 0 HTTP/1.1 responses : 0HTML responses : 0 CSS responses : 0XML responses : 0 JS responses : 0Other content type resp : 0 Chunked encoding resp : 0Resp with encoded content: 0 Resp with content length : 0Close after response : 0 Resp with header size >1K: 0Processed resp hdr size : 0 Processed resp body bytes: 0Backend https response : 0 Chunked encoding requests: 0CIFS statistics:SMB related Per Context:TCP VC's : 0 UDP VC's : 0Active VC's : 0 Active Contexts : 0Aborted Conns : 0NetBIOS related Per Context:Name Queries : 0 Name Replies : 0NB DGM Requests : 0 NB DGM Replies : 0NB TCP Connect Fails : 0 NB Name Resolution Fails : 0HTTP related Per Context:Requests : 0 Request Bytes RX : 0Request Packets RX : 0 Response Bytes TX : 0Response Packets TX : 0 Active Connections : 0Active CIFS context : 0 Requests Dropped : 0Socket statistics:Sockets in use : 0 Sock Usr Blocks in use : 0Sock Data Buffers in use : 0 Sock Buf desc in use : 0Select timers in use : 0 Sock Select Timeouts : 0Sock Tx Blocked : 0 Sock Tx Unblocked : 0Sock Rx Blocked : 0 Sock Rx Unblocked : 0Sock UDP Connects : 0 Sock UDP Disconnects : 0Sock Premature Close : 0 Sock Pipe Errors : 0Sock Select Timeout Errs : 0Port Forward statistics:Connections serviced : 0 Server Aborts (idle) : 0Client Serverin pkts : 0 out pkts : 0in bytes : 0 out bytes : 0out pkts : 0 in pkts : 0out bytes : 0 in bytes : 0WEBVPN Citrix statistics:Connections serviced : 0Server ClientPackets in : 0 0Packets out : 0 0Bytes in : 0 0Bytes out : 0 0Tunnel Statistics:Active connections : 0Peak connections : 0 Peak time : neverConnect succeed : 0 Connect failed : 0Reconnect succeed : 0 Reconnect failed : 0SVCIP install IOS succeed: 0 SVCIP install IOS failed : 0SVCIP clear IOS succeed : 0 SVCIP clear IOS failed : 0SVCIP install TCP succeed: 0 SVCIP install TCP failed : 0DPD timeout : 0Client Serverin CSTP frames : 0 out IP pkts : 0in CSTP data : 0 out stitched pkts : 0in CSTP control : 0 out copied pkts : 0in CSTP Addr Reqs : 0 out bad pkts : 0in CSTP DPD Reqs : 0 out filtered pkts : 0in CSTP DPD Resps : 0 out non fwded pkts : 0in CSTP Msg Reqs : 0 out forwarded pkts : 0in CSTP bytes : 0 out IP bytes : 0out CSTP frames : 0 in IP pkts : 0out CSTP data : 0 in invalid pkts : 0out CSTP control : 0 in congested pkts : 0out CSTP Addr Resps : 0 in bad pkts : 0out CSTP DPD Reqs : 0 in nonfwded pkts : 0out CSTP DPD Resps : 0 in forwarded pkts : 0out CSTP Msg Reqs : 0out CSTP bytes : 0 in IP bytes : 0Example: show webvpn stats sso
The following output example displays statistics for an SSO server:
Router# show webvpn stats ssoSingle Sign On statistics:Auth Requests : 4 Pending Auth Requests :0Successful Requests : 1 Failed Requests :3Retranmissions : 0 DNS Errors :0Connection Errors : 0 Request Timeouts :0Unknown Responses :The following output example displays extra information about SSO servers that are configured for the SSL VPN context:
Router# show webvpn context test_ssoContext SSO server: sso-serverWeb agent URL : "http://example1.examplecompany.com/vpnauth/"Policy Server Secret : "Secret123"Request Re-tries : 5, Request timeout: 15-secondThe following output example displays extra information about an SSO server that is configured for the policy group of the SSL VPN context:
Router# show webvpn policy group sso context test_ssoWV: group policy = sso ; context = test_ssoidle timeout = 2100 secsession timeout = 43200 secsso server name = "server1"citrix disableddpd client timeout = 300 secdpd gateway timeout = 300 seckeep SSL VPN client installed = disabledrekey interval = 3600 secrekey method =lease duration = 43200 secExample: FVRF show Command Output
The following output example shows that FVRF has been configured:
Router# show webvpn gateway mygatewayAdmin Status: downOperation Status: downError and Event Logging: DisabledGW IP address not configuredSSL Trustpoint: TP-self-signed-788737041FVRF Name: vrf_1Additional References
Related Documents
Cisco IOS commands
Cisco AnyConnect VPN Client
•
•
Release 2.4Cisco Secure Desktop
Configuring IP VRF (ip vrf command)
IANA Application Port Numbers
RADIUS accounting
"Configuring RADIUS" module in the Cisco IOS Security Configuration Guide: Securing User Services
Security commands
SSL VPN platforms
Cisco IOS SSL VPN ("Feature Availability" section)
SSL VPN remote users guide
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
No new or modified RFCs are supported by this feature, and support for existing standards has not been modified by this feature.
—
Technical Assistance
Feature Information for SSL VPN
Table 6 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 6
Access Control Enhancements
12.4(20)T
This feature allows administrators to configure automatic authentication and authorization for users. Users provide their usernames and passwords via the gateway page URL and do not have to reenter their usernames and passwords from the login page. Authorization is enhanced to support more generic authorization, including local authorization.
The following sections provide information about this feature:
•
The following commands were introduced by this feature: aaa authentication auto and aaa authorization list.
AnyConnect Client Support
12.4(20)T
Effective with this release, AnyConnect Client adds support for several client-side platforms, such as Microsoft Windows, Apple-Mac, and Linux. The ability to install AnyConnect in a standalone mode is also added. In addition, this feature allows multiple SSL VPN client package files to be configured on a gateway.
The following sections provide information about this feature:
•
•
The following command was modified by this feature: webvpn install.
Application ACL Support
12.4(11)T
This feature provides administrators with the flexibility to fine-tune access control at the application layer level.
The following sections provide information about this feature:
•
The following commands were introduced by this feature: acl, add, error-msg, error-url, and list.
Auto Applet Download
12.4(9)T
This feature provides administrators with the option of automatically downloading the port-forwarding applet under the policy group.
The following section provides information about this feature:
•
The following command was modified by this feature: port-forward (policy group).
Backend HTTP Proxy
12.4(20)T
This feature allows administrators to route user requests through a backend HTTP proxy, providing more flexibility and control than routing through internal web servers.
The following sections provide information about this feature:
•
The following command was added by this feature: http proxy-server.
Cisco AnyConnect VPN Client
12.4(15)T
This feature is the next-generation SSL VPN Client. The feature provides remote users with secure VPN connections to the router platforms supported by SSL VPN and to the Cisco 5500 Series Adaptive Security Appliances.
Users having Cisco IOS releases before Release 12.4(15)T see SSL VPN Client GUI. Users having Release 12.4(15)T and later releases see Cisco AnyConnect VPN Client GUI.
The task configurations in this document for tunnel mode apply to SVC and AnyConnect VPN Client.
For more information about the Cisco AnyConnect VPN Client feature, see the Cisco AnyConnect VPN Client Administrator Guide, Release 2.4 and the Release Notes for Cisco AnyConnect VPN Client, Release 2.4.
Note
Debug Infrastructure
12.4(11)T
Updates to the webvpn debug command provide administrators with the ability to turn debugging on for any one user or group.
The following keywords were introduced by this feature: acl, entry, sso, and verbose.
The following keyword options were added for the http keyword: authentication, trace, and verbose.
The verbose keyword option was added for the citrix, cookie, tunnel, and webservice keywords.
The port-forward keyword was deleted and the detail keyword option for the tunnel keyword was deleted.
Front-Door VRF Support
12.4(15)T
Coupled with the already supported internal VRF, this feature allows the SSL VPN gateway to be fully integrated into an MPLS network.
The following sections provide information about this feature:
Full-Tunnel CEF Support
12.4(20)T
This feature provides better performance for full-tunnel packets.
The following sections provide information about this feature:
•
•
GUI Enhancements
12.4(15)T
These enhancements provide updated examples and explanation of the Web VPN GUIs.
The following section provides information about these updates:
Internationalization
12.4(22)T
The Internationalization feature provides multilanguage support for SSL VPN clients, such as Cisco Secure Desktop (CSD) and SSL VPN Client (SVC).
The following section provides information about these updates:
•
•
The following commands were introduced: browser-attribute import, import, language, webvpn create template.
Licensing support for Cisco IOS SSL VPNs
15.0(1)M
A license count is associated with each counted license and the count indicates the instances of the feature available for use in the system.
In Cisco IOS Release 15.0(1)M, support was added for Cisco 880, Cisco 890, Cisco 1900, Cisco 2900, and Cisco3900 series routers.
The following section provides information about this feature:
The following commands were introduced or modified: debug webvpn license and show webvpn license.
Max-user limit message
12.4(22)T
This error message is received when a user tries to log in to a Web VPN context and his or her maximum user limit has been reached.
Netegrity Cookie-Based Single SignOn (SSO) Support
12.4(11)T
This feature allows administrators to configure an SSO server that sets a SiteMinder cookie in the browser of a user when the user initially logs in. The benefit of this feature is that users are prompted to log in only a single time.
The following sections provide information about this feature:
•
•
•
The following commands were modified for this feature: clear webvpn stats, debug webvpn, show webvpn context, show webvpn policy, and show webvpn stats.
The following commands were added for this feature: max-retry-attempts, request-timeout, secret-key, sso-server, and web-agent-url.
NTLM Authentication
12.4(9)T
This feature provides NT LAN Manager (NTLM) authentication support.
The following section provides information about this feature:
The following command was modified by this feature: functions.
Port-Forward Enhancements
12.4(11)T
This feature provides administrators with more options for configuring HTTP proxy and portal pages.
The following section provides information about this feature:
•
The following commands were added for this feature: acl, add, deny, error-msg, error-url, list, and permit.
RADIUS Accounting
12.4(9)T
This feature provides for RADIUS accounting for SSL VPN sessions.
The following sections provide information about this feature:
•
•
The following command was added by this feature: webvpn aaa accounting-list.
SSL VPN
12.4(6)T
This feature enhances SSL VPN support in Cisco IOS software. This feature provides a comprehensive solution that allows easy access to a broad range of web resources and web-enabled applications using native HTTP over SSL (HTTPS) browser support. SSL VPN introduced three modes of SSL VPN access: clientless, thin-client, and full-tunnel client support.
The following command was introduced in Cisco IOS Release 12.4(15)T: cifs-url-list.
SSL VPN Client-Side Certificate-Based Authentication
15.0(1)M
This feature enables SSL VPN to authenticate clients based on the client's AAA username and password and also supports webvpn gateway authentication of clients using AAA certificates.
The following sections provide information about this feature:
•
•
The following command was modified by this feature: authentication certificate, ca trustpoint, match-certificate, svc profile, username-prefill, webvpn import svc profile.
SSLVPN DVTI Support
15.1(1)T
The SSLVPN DVTI Support feature adds DVTI support to the SSLVPN and hence enables seamless interoperability with IP features such as firewalls, NAT, ACL, and VRF. This feature also provides DVTI support, which allows the configuration of IP features on a per-tunnel basis.
The following sections provide information about this feature:
•
•
•
The following command was introduced or modified: virtual-template.
SSL VPN Phase-4 Features
15.1(1)T
The SSL VPN Phase-4 Features feature provides the following enhancements to the Cisco IOS SSL VPN:
•
•
•
•
•
The following sections provide information about this feature:
•
•
The following commands were introduced or modified: show webvpn session, svc address-pool, svc module, svc split.
Stateless High Availability with Hot Standby Router Protocol (HSRP)
12.4(20)T
This feature allows stateless failover to be applied to VPN routers by using HSRP.
The following sections provide information about this feature:
•
•
•
The following command was modified by this feature: ip address.
URL Obfuscation
12.4(11)T
This feature provides administrators with the ability to obfuscate, or mask, sensitive portions of an enterprise URL, such as IP addresses, hostnames, or port numbers.
The following sections provide information about this feature:
•
•
The following command was added by this feature: mask-urls.
URL Rewrite Splitter
12.4(20)T
This feature allows administrators to selectively mangle requests to the gateway.
The following sections provide information about this feature:
•
•
The following commands were added by this feature: host, ip, unmatched-action, and url rewrite.
User-Level Bookmarking
12.4(15)T
This feature allows a user to bookmark URLs while connected through an SSL VPN tunnel.
The following sections provide information about this feature:
•
The following command was added by this feature: user-profile location.
Virtual Templates
12.4(24)T1
A virtual template enables SSL VPN to interoperate with IP features such as NAT, firewall, and policy-based routing.
The following section provides information about these updates:
•
The following command was introduced: virtual-template.
Feature Information for SSL VPN
Notices
The following notices pertain to this software license.
OpenSSL/OpenSSL 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; that is, 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.
2.
3.
4.
5.
6.
"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 Netscape's 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.
2.
3.
"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.
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; that is, this code cannot simply be copied and put under another distribution license [including the GNU Public License].
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2006-2011 Cisco Systems, Inc. All rights reserved.
