Cisco anyconnect android profile

Strict Certificate Trust overrides this setting, see description below.

OCSP Revocation

The AnyConnect client supports OCSP (Online Certificate Status Protocol). This allows the client to query the status of individual certificates in real time by making a request to the OCSP responder and parsing the OCSP response to get the certificate status. OCSP is used to verify the entire certificate chain. There is a five second timeout interval per certificate to access the OCSP responder.

The user can enable or disable OCSP verification in the Anyconnect settings activity, for details see the Android User Guide for Cisco AnyConnect Secure Mobility Client, Release 4.0 . We have also added new API’s in our framework which can be used by MDM administrators to control this feature remotely. Currently we support Samsung and Google MDM.

Strict Certificate Trust

If enabled by the user, when authenticating remote security gateways, AnyConnect disallows any certificate that it cannot verify. Instead of prompting the user to accept these certificates, the client fails to connect to security gateways.

Note	This setting overrides Block Untrusted Server .

If not selected, the client prompts the user to accept the certificate. This is the default behavior.

We strongly recommend that you enable Strict Certificate Trust for the AnyConnect client for the following reasons:

With the increase in targeted exploits, enabling Strict Certificate Trust in the local policy helps prevent “man in the middle” attacks when users are connecting from untrusted networks such as public-access networks.

Even if you use fully verifiable and trusted certificates, the AnyConnect client, by default, allows end users to accept unverifiable certificates. If your end users are subjected to a man-in-the-middle attack, they may be prompted to accept a malicious certificate. To remove this decision from your end users, enable Strict Certificate Trust.

Client Authentication on Mobile Devices

To complete a VPN connection, the user must authenticate by providing credentials in the form of a username and password, a digital certificate, or both. The administrator defines the authentication method on the tunnel group. For the best user experience on mobile devices, Cisco recommends using multiple AnyConnect connection profiles depending on the authentication configuration. You will have to decide how best to balance user experience with security. We recommend the following:

For AAA-based authentication tunnel groups for mobile devices, the group policy should have a very long idle timeout, such as 24 hours, to let the client remain in a reconnecting state without requiring the user to re-authenticate.

To achieve the most transparent end user experience, use certificate-only authentication. When a digital certificate is used, a VPN connection is established without user interaction.

In order to authenticate the mobile device to the secure gateway using a certificate, end users must import a certificate onto their device. This certificate is then available for automatic certificate selection, or it can be associated with a particular connection entry manually. Certificates are imported using the following methods:

Imported manually by the user. See the appropriate user guide for procedures to import certificates to your mobile device.

Added after the user clicks a link provided by the administrator to import a certificate.

See Import Certificates to provide this kind of certificate deployment to your users.

VPN Authentication Using SAML

You can use SAML 2.0 integrated with ASA release 9.7.1 for initial session authentication. To provide a seamless reconnect without disruption, AnyConnect intentionally skips the repeating of the SAML authentication process. Additionally, if the user logs out of the IdP using a browser, the AnyConnect session remains intact.

Follow these guidelines when using SAML:

You must synchronize your ASA’s Network Time Protocol (NTP) server with the IdP NTP server in order to use the SAML feature.

The VPN Wizard on ASDM does not currently support SAML configurations.

You cannot access internal servers with SSO after logging in using an internal IdP.

The SAML IdP NameID attribute determines the user’s username and is used for authorization, accounting, and VPN session database.

You should set Auto Reconnect to ReconnectAfterResume in the AnyConnect Profile Editor, Preferences (Part 1) if you want users to re-authenticate with the Identity Provider (IdP) every time they establish a VPN session via SAML.

For AnyConnect Mobile the following platforms and versions are supported:

Chrome OS 4.0.10151

Refer to the SSO Using SAML 2.0 section in the appropriate release, 9.7 or later, of the Cisco ASA Series VPN Configuration Guide for additional configuration details.

Localization on Mobile Devices

AnyConnect Secure Mobility Client for Android and Apple iOS supports localization, adapting the AnyConnect user interface and messages to the user’s locale.

Prepackaged Localization

The following language translations are included in the AnyConnect Android and Apple iOS apps:

Canadian French (fr-ca)

Chinese (Taiwan) (zh-tw)

Latin American Spanish (es-co)

Portuguese (Brazil) (pt-br)

Simplified Chinese (zh-cn)

Localization data for these languages is installed on the mobile device when AnyConnect is installed. The local specified on your mobile device determines the displayed language. AnyConnect uses the language specification, then the region specification, to determine the best match. For example, after installation, a French-Switzerland (fr-ch) locale setting results in a French-Canadian (fr-ca) display. AnyConnect UIs and messages are translatednyConnect when AnyConnect starts.

Downloaded Localization

For languages not in the AnyConnect package, administrators add localization data to the ASA to be downloaded to the device upon AnyConnect VPN connectivity.

Cisco provides the anyconnect.po file, including all localizable AnyConnect strings, on the product download center of Cisco.com. AnyConnect administrators download the anyconnect.po file, provide translations for the available strings, and then upload the file to the ASA. AnyConnect administrators that already have an anyconnect.po file installed on the ASA will download this updated version.

Initially, the AnyConnect user interface and messages are presented to the user in the installed language. When the device user establishes the first connection to the ASA, AnyConnect compares the device’s preferred language to the available localization languages on the ASA. If AnyConnect finds a matching localization file, it downloads the localized file. Once the download is complete, AnyConnect presents the user interface and user messages using the translated strings added to anyconnect.po file. If a string was not translated, AnyConnect presents the default English strings.

See Import Translation Tables to the Adaptive Security Appliance for instructions on configuring localization on an ASA. If the ASA does not contain localization data for the device’s locale, the preloaded localization data from the AnyConnect application package continues to be used.

More Ways to Provide Localization on Mobile Devices

Localize the AnyConnect UI and Messages by providing a URI link to the user.

Ask your mobile device users to manage localization data on their own device. See the appropriate User Guide for procedures to perform the following localization activities:

Import localization data from a specified server. The user chooses to import localization data and specifies the address of the secure gateway and the locale. The locale is specified per ISO 639-1, with the country code added if applicable (for example, en-US, fr-CA, ar-IQ, and so on). This localization data is used in place of the prepackaged, installed localization data.

Restore default localization data. This restores the use of the preloaded localization data from the AnyConnect package and deletes all imported localization data.

FIPS and Suite B Cryptography on Mobile Devices

AnyConnect for mobile devices incorporates Cisco Common Cryptographic Module (C3M), the Cisco SSL implementation which includes FIPS 140-2 compliant cryptography modules and NSA Suite B cryptography as part of its Next Generation Encryption (NGE) algorithms. Suite B cryptography is available for IPsec VPNs only; FIPS-compliant cryptography is available for both IPsec and SSL VPNs.

Use of cryptography algorithms is negotiated with the headend while connecting. Negotiation is dependent on the capabilities of both ends of the VPN connection. Therefore, the secure gateway must also support FIPS-compliant and Suite B cryptography.

The user configures AnyConnect to accept only NGE algorithms during negotiation by enabling FIPS Mode in the AnyConnect app settings. When FIPS Mode is disabled, AnyConnect also accepts non-FIPS cryptography algorithms for VPN connections.

See About FIPS, NGE, and AnyConnect for general support information.

Additional Mobile Guidelines and Limitations

Apple iOS 5.0 or later is required for Suite B cryptography; this is the minimum Apple iOS version that supports ECDSA certificates used in Suite B.

Android 4.0 (Ice Cream Sandwich) or later is required for Suite B cryptography; this is the minimum Android version that supports ECDSA certificates used in Suite B.

A device that is running in FIPS mode is not compatible with using SCEP to provide mobile users with digital certificates by proxy method or legacy method. Plan your deployment accordingly.

AnyConnect on Android Devices

Guidelines and Limitations for AnyConnect on Android

AnyConnect for Android supports only the VPN features that are strictly related to remote access.

AnyConnect for Android supports only the Network Visibility Module, it does not support any other AnyConnect modules.

The ASA does not provide distributions and updates for AnyConnect for Android. They are available only on Google Play.

AnyConnect for Android supports connection entries that the user adds and connection entries populated by an AnyConnect profile pushed by an ASA. The Android device supports no more than one AnyConnect profile, which is the last one received from a headend. However, a profile can consist of multiple connection entries.

If users attempt to install AnyConnect on devices that are not supported, they receive the pop-up message Installation Error: Unknown reason -8 . This message is generated by the Android OS.

When users have an AnyConnect widget on their home screen, the AnyConnect services are automatically started (but not connected) regardless of the «Launch at startup» preference.

AnyConnect for Android requires UTF-8 character encoding for extended ASCII characters when using pre-fill from client certificates. The client certificate must be in UTF-8 if you want to use prefill, per the instructions in KB-890772 and KB-888180.

AnyConnect blocks voice calls if it is sending or receiving VPN traffic over an EDGE connection per the inherent nature of EDGE and other early radio technology.

Some known file compression utilities do not successfully decompress log bundles packaged with the use of the AnyConnect Send Log button. As a workaround, use the native utilities on Windows and Mac OS X to decompress AnyConnect log files.

Android Specific Considerations

Android Mobile Posture Device ID Generation

Upon a fresh installation, or after the user clears the application data, AnyConnect now generates a unique 256-byte device ID, which is based on the Android ID. This ID replaces the legacy 40-byte device ID based on the IMEI and MAC address generated in earlier releases.

If an earlier version of AnyConnect is installed, a legacy ID has already been generated. After upgrading to this version of AnyConnect, this legacy ID continues to be reported as the Device Unique ID until the user clears the application data or uninstalls AnyConnect.

Generated device IDs can be viewed after the initial application launch from the AnyConnect Diagnostics > Logging and System Information > System > Device Identifiers screen, or inside the AnyConnect log in the device_identifiers.txt file, or on the About Screen.

Note	DAP policies on the secure gateway will need to be updated to use the new device IDs.

The Device-ID is determined as follows:

Where the Android-ID and bytesToHexString are defined as follows:

Android Device Permissions

The following permissions are declared in the Android manifest file for AnyConnect operation:

Allows applications to access information about networks.

Allows applications to access information about Wi-Fi networks.

Allows an application to broadcast sticky intents. These are broadcasts whose data is held by the system after being finished, so that clients can quickly retrieve that data without having to wait for the next broadcast.

Allows applications to open network sockets.

Allows an application to read from external storage.

Allows an application to read the low-level system log files.

Allows read only access to phone state, including the phone number of the device, current cellular network information, the status of any ongoing calls, and a list of any PhoneAccounts registered on the device.

Allows an application to receive the broadcast after the system finishes booting.

AnyConnect on Apple iOS Devices

Guidelines and Limitations for AnyConnect on Apple iOS

AnyConnect for Apple iOS supports only features that are related to remote VPN access such as:

AnyConnect can be configured by the user (manually), by the AnyConnect VPN Client Profile, generated by the iPhone Configuration Utility (http:/​/​www.apple.com/​support/​iphone/​enterprise/​), or using an Enterprise Mobile Device Manager.

The Apple iOS device supports no more than one AnyConnect VPN client profile. The contents of the generated configuration always match the most recent profile. For example, you connect to vpn.example1.com and then to vpn.example2.com, the AnyConnect VPN client profile imported from vpn.example2.com replaces the one imported from vpn.example1.com.

This release supports the tunnel keepalive feature; however, it reduces battery life of the device. Increasing the update interval value mitigates this issue.

Apple iOS Connect On-Demand Considerations:

VPN sessions that are automatically connected as a result of iOS On-Demand logic and have Disconnect on Suspend configured, are disconnected when the device sleeps. After the device wakes up, On-Demand logic will reconnect the VPN session when it is necessary again.

AnyConnect collects device information when the UI is launched and a VPN connection is initiated. Therefore, there are circumstances in which AnyConnect can misreport mobile posture information if the user relies on iOS’s Connect On-Demand feature to make a connection initially, or after device information, such has the OS version, has changed.

This only applies in your environment if you are running a Legacy AnyConnect release earlier than 4.0.05032, or an Apple iOS release earlier than 9.3 while using Apple Connect-on-Demand capabilities. To ensure proper establishment of Connect On-Demand VPN tunnels after updating AnyConnect, users must manually start the AnyConnect app and establish a connection. If this is not done, upon the next iOS system attempt to establish a VPN tunnel, the error message “The VPN Connection requires an application to start up” displays.

Cisco AnyConnect and Legacy AnyConnect are different apps with different app IDs. Hence:

You cannot upgrade the AnyConnect app from a legacy 4.0.05x or earlier version to the new 4.0.07x version. Cisco AnyConnect 4.0.07x is a separate app, installed with a different name and icon.

The different versions of AnyConnect can co-exist on the mobile device, but this is not supported by Cisco. The behavior may not be as expected if you attempt to connect while having both versions of AnyConnect installed. Make sure you have only one AnyConnect app on your device and it is the appropriate version for your device and environment.

Certificates imported using Legacy AnyConnect version 4.0.05069 and any earlier release, cannot be accessed or used by the new AnyConnect app release 4.0.07072 or later. MDM deployed certificates can be accessed and used by both app versions.

App data imported to the Legacy AnyConnect app, such as certificates and profiles, should be deleted if you are updating to the new version. Otherwise they will continue to show in the system VPN settings. Remove app data before uninstalling the Legacy AnyConnect app.

Current MDM profiles will not trigger the new app. EMM vendors must support VPNType (VPN), VPNSubType (com.cisco.anyconnect) and ProviderType (packet-tunnel). For integration with ISE, they must be able to pass the UniqueIdentifier to AnyConnect since AnyConnect no longer has access to this in the new framework. Please consult with your EMM vendor for how to set this up, some may require a custom VPN type and others may not have support available at release time.

Using the New Extension Framework in AnyConnect 4.0.07x and later causes the following changes in behavior from Legacy AnyConnect 4.0.05x:

The Device ID sent to the head end is no longer the UDID in the new version, and it is different after a factory reset unless your device is restored from a backup made by the same device.

You may use MDM deployed certificates, as well as certificates imported using one of the methods available in AnyConnect: SCEP, manually through the UI, or via the URI handler. The new version of AnyConnect can no longer use certificates imported via email or any other mechanism beyond these identified ones.

When creating a connection entry using the UI, the user must accept the iOS security message displayed.

A user-created entry with the same name as a downloaded host entry from the AnyConnect VPN profile will not be renamed until it disconnects, if it is active. Also, the downloaded host connection entry will appear in the UI after this disconnect, not while it remains connected.

Apple iOS Specific Considerations

When supporting AnyConnect on Apple iOS devices, consider:

The SCEP references in this document apply exclusively to AnyConnect SCEP, not Apple iOS SCEP.

Push email notifications do not work over VPN because of Apple iOS constraints. However, AnyConnect works in parallel with externally accessible ActiveSync connections, when the tunnel policy excludes these from the session.

The Apple iPhone Configuration Utility

The iPhone Configuration Utility (IPCU), available from Apple for Windows or Mac OS X, is used to create and deploy configurations to an Apple iOS device. This can be done in place of configuring an AnyConnect client profile on the secure gateway.

The existing IPCU GUI, controlled by Apple, does not know of the AnyConnect IPsec capabilities. Configure IPsec VPN connections within the existing AnyConnect GUI in IPCU. Use the following URI syntax, as defined in RFC 2996 in the Server field. This Server field syntax is backward compatible with the documented usage for configuring SSL VPN connections.

[ ipsec ://][ AUTHENTICATION >[“:” IKE-IDENTITY >“@”]] HOST >[“:” PORT >][“/” GROUP-URL >]

: Indicates that this is an IPsec connection. If omitted, SSL is assumed.

Specifies the authentication method for an IPsec connection. If omitted, EAP-AnyConnect is assumed. Valid values are:

Specifies the IKE identify when AUTHENTICATION is set to EAP-GTC, EAP-MD5, or EAP-MSCHAPv2. This parameter is invalid when used for other authentication settings.

Specifies the server address. The hostname or IP address to be used.

Currently ignored, included for consistency with the HTTP URI scheme.

Tunnel group name appended to the server name.

To connect to a standards-compliant Cisco IOS router only, use the following:

Connect-on-Demand Usage Guidelines

The Apple iOS Connect-on-Demand feature lets other applications, such as Safari, start a VPN connection. Apple iOS evaluates the domain requested by the application against the rules configured for the device’s active connection entry. Apple iOS establishes a VPN connection on behalf of an application only if all of the following are true:

A VPN connection is not already established.

An application compatible with the Apple iOS Connect-on-Demand framework requests a domain.

The connection entry is configured to use a valid certificate.

Connect On Demand is enabled in the connection entry.

Apple iOS fails to match a string in the Never Connect list to the domain request.

Either of the following is true: Apple iOS matches a string in the Always Connect list to the domain request (on Apple iOS 6 only). Or a DNS lookup failed, and Apple iOS matches a string in the Connect if Needed list to the domain request.

Keep in mind the following when using the Connect-on-Demand feature:

After a VPN connection is initiated using iOS’s Connect on Demand, iOS disconnects the tunnel if the tunnel is inactive for a particular time interval. See Apple’s VPN Connect-on-Demand documentation for more information.

We recommend using the Connect if Needed option if you configure rules. A Connect if Needed rule starts a VPN connection if the DNS lookup to an internal host fails. It requires a correct DNS configuration so that hostnames within the enterprise are resolved using internal DNS servers only.

For mobile devices that have Connect on Demand configured, certificate-based authentication tunnel groups have a short (60 second) idle timeout (vpn-idle-timeout). Set a short idle timeout if your VPN session is not critical for an application and does not always need to be connected. The Apple device closes the VPN connection when it is no longer needed, for example, when the device goes into sleep mode. The default idle timeout for a tunnel group is 60 minutes.

Always connect behavior is release dependent:

On Apple iOS 6, iOS always starts a VPN connection when rules in this list are matched.

On iOS 7.x, Always Connect is not supported, when rules in this list are matched they behave as Connect If Needed rules.

On later releases, Always Connect is not used, configured rules are moved to the Connect If Needed list and behave as such.

Apple has introduced a Trusted Network Detection (TND) enhancement to theConnect-on-Demand feature. This enhancement:

Extends the Connect-on-Demand functionality by determining whether the device user is on a trusted network.

Applies to Wi-Fi connectivity only. When operating over other types of network connections, Connect on Demand does not use TND to determine whether to connect a VPN.

Is not a separate feature and cannot be configured or used outside the Connect-on-Demand capabilities.

Contact Apple for more information about Connect on Demand Trusted Network Detection in iOS 6.

The integrated Apple iOS IPsec client and AnyConnect both use the same Apple iOS VPN Connect-on-Demand framework.

Split DNS Resolution Behavior with Split Tunnel

The ASA split tunneling feature lets you specify which traffic goes over the VPN tunnel and which traffic goes in the clear. An associated feature called split DNS lets you specify which DNS traffic is eligible for DNS resolution over the VPN tunnel and which DNS traffic the endpoint DNS resolver handles (in the clear). Split DNS works differently on Apple iOS devices than on other devices if you also configure split tunneling. AnyConnect for Apple iOS responds to this command as follows:

Encrypts only DNS queries for domains in the split-dns list.

AnyConnect tunnels only the DNS queries for the domains specified in the command. It sends all other DNS queries to the local DNS resolver for resolution in-the-clear. For example, AnyConnect tunnels only the DNS queries for example1.com and example2.com in response to the following command:

Encrypts only DNS queries for the domain in the default-domain command.

If the split-dns none command is present and the default-domain command specifies a domain, AnyConnect tunnels only DNS queries for that domain and sends all other DNS queries to the local DNS resolver for resolution in-the-clear. For example, AnyConnect tunnels only the DNS queries for example1.com in response to the following commands:

Sends all DNS queries in-the-clear. If the split-dns none and default-domain none commands are present in the group policy, or if these commands are absent from the group policy but present in the default group policy, AnyConnect sends all DNS queries to the local DNS resolver for resolution in-the-clear.

Note

If split-dns is not specified, the group policy inherits the spit tunneling domain lists that are present in the default group policy. To prevent inheriting a split tunneling domain list, use the split-dns none command. AnyConnect on BlackBerry Devices Guidelines and Limitations for AnyConnect on BlackBerry Enabling Split DNS can break VPN connections. Blackberry supports a maximum of two DNS servers. Our ASA configured DNS server takes precedence because it is prepended in the DNS server list, so our ASA configured DNS server is applied to the tun adapter. If the ASA configures two private DNS servers without DNS forwarding in the ASA side, then DNS resolution of public network will fail. Work around: Until BlackBerry supports more than 2 DNS servers, the Admin should configure only one private DNS server on the ASA end. AnyConnect VPN profiles which are pushed to devices from an ASA headend, block all untrusted servers by default. This may be preventing a successful VPN connection. Disable this setting to provide the user with the option to accept or deny connections to untrusted servers IPsec IKEv2 VPN connections must be enabled and configured manually on the device by the user. Only EAP authentication is supported when connecting to the ASA headend. AnyConnect on Chrome OS Devices Guidelines and Limitations for AnyConnect on Chrome OS When the Chromebook device is managed (enrolled in an Enterprise Chrome Management service), then AnyConnect cannot access client certificates: client certificate authentication does not work. There is limited VPN performance on low-end Chromebooks (chromium issue #514341). Auto reconnect, reconnecting the VPN session when the network interface goes down and up, is supported when using AnyConnect release 4.0.10113 or later with Chrome OS 51 or later. Prior to Chrome 51 and this AC release, if you lost Wi-Fi, or put your device to sleep, AnyConnect would not be able to reconnect on its own. Unless you are using Chrome OS 45 or later, all server certificates, even fully trusted and valid ones, received from the secure gateway are seen as untrusted. After installing or upgrading AnyConnect on Chrome OS, wait until initializing is complete to configure AnyConnect. «Initializing, please wait. » is displayed in the AnyConnect app. This process may take a few minutes. Configure Mobile Device VPN Connectivity on the ASA Secure Gateway Procedure Step 1 Refer to the appropriate release of the Cisco ASA 5500-X Series Next-Generation Firewalls, Configuration Guides for configuration procedures that are common to desktop and mobile endpoints. Consider the following for mobile devices: Configuration > Remote Access VPN > Network (Client) Access > Group Policies > Add / Edit > Advanced > AnyConnect Client > Customization AnyConnect Mobile ignores the home page URL setting, you cannot redirect mobile clients after successful authentication. Name and Aliases of the AnyConnect Connection Profile Configuration > Remote Access VPN > Network (Client) Access > AnyConnect Connection Profiles > Add / Edit Do not use special characters in the Name or Aliases fields of tunnel groups (connection profiles) that are used for AnyConnect mobile client connectivity. Use of special characters may cause the AnyConnect client to display the error message: Connect attempt has failed after logging that it is Unable to process response from Gateway . Configuration > Remote Access VPN > Network (Client) Access > Group Policies > Add / Edit > Advanced > AnyConnect Client Switch off server-side dead peer detection because it prevents the device from sleeping. However, client-side dead peer detection should remain switched on because it enables the client to determine when the tunnel is terminated due to a lack of network connectivity. Configuration > Remote Access VPN > Network (Client) Access > Group Policies > Add / Edit > Advanced > AnyConnect Client We recommend disabling these keepalive messages to conserve the battery life of mobile devices, especially if client-side dead peer detection is enabled. IPsec over NAT-T Keepalive Messages Configuration > Remote Access VPN > Network (Client) Access > Advanced > IPsec > IKE Parameters Enable IPsec over NAT-T must be selected for AnyConnect IPsec to work. When enabled, NAT Keepalive messages are sent every 20 seconds by default, causing excessive battery drainage on mobile devices. To minimally effect battery usage on mobile devices, we recommend you Set the NAT-T Keepalives to the maximum value of 3600 because these messages cannot be disabled. Use the crypto isakmp nat-traversal 3600 command to specify this in the ASA CLI. Step 2 Configure Mobile Posture (also called AnyConnect Identity Extensions, ACIDex) to accept, deny, or restrict mobile connections as desired. See the Configuring Endpoint Attributes Used in DAPs procedure, in the appropriate release of Cisco ASA 5500-X Series Next-Generation Firewalls, Configuration Guides . The following attributes are sent by AnyConnect on Apple iOS to the headend when establishing a connection: Step 3 (Optional) Configure Per App VPN tunneling mode. If Per App VPN tunneling mode is not configured, the AnyConnect app operates in system-tunneling mode. Configure Per App VPN AnyConnect Per App VPN tunneling requires: ASA 9.3.1 or later to configure Per App VPN tunneling. An AnyConnect v4.0 Plus or Apex license. AnyConnect Per App VPN supports the following mobile platforms: Android devices running Android 5.0 (Lollipop) or later. Apple iOS devices running Apple iOS 8.3 or later configured to use Per App VPN in a Mobile Device Management (MDM) solution. Procedure Step 1 Install the Cisco AnyConnect Enterprise Application Selector Tool. Step 2 Use the Application Selector tool to specify an AnyConnect Per App VPN policy for your platform: Define a Per App VPN Policy for Android Devices Define a Per App VPN Policy for Apple iOS Devices Step 3 Create Per App Custom Attributes on the ASA. Step 4 Assign a Custom Attribute to a Policy on the ASA. Install the Cisco AnyConnect Enterprise Application Selector Tool The Application Selector Tool is a standalone application that supports policy generation for both Android and Apple iOS devices. Before You Begin The Cisco AnyConnect Enterprise Application Selector requires Java 7 or later. Procedure Step 1 Download the Cisco AnyConnect Enterprise Application Selector tool from the Cisco.com AnyConnect Secure Mobility Client v4.x Software Center . Step 2 If you are using Android apps in your policy, you must have the Android SDK and the Android SDK Build-tools installed on your system. If you do not, install them as follows. Install the latest version of the Android SDK Tools for the platform you are running the Application Selector Tool on. Install the recommended SDK Tools Only package for your platform using the default paths and settings, including: Install for All Users, so access to package entities is as described. Using the Android SDK Manager, install the latest version of the Android SDK Build-tools . What to Do Next Note If prompted in the application selector tool, configure access to the Android Asset Packaging Tool, aapt , by specifying its installed location, Android SDK installation directory \build-tools\ build-tools version number \ . Define a Per App VPN Policy for Android Devices Your Per App VPN policy consists of a set of rules, where each rule identifies an app whose data flows over the tunnel. Specify the rule options to more stringently identify the allowable app and its use in your mobile device environment. The Application Selector tool uses information from the app’s package file, *.apk , to set rule options. See http:/​/​developer.android.com/​guide/​topics/​manifest/​manifest-element.html for Android package manifest information. Before You Begin The Cisco AnyConnect Enterprise Application Selector requires Java 7 or later. Procedure Step 1 Start the application selector and choose the Android mobile device platform. Step 2 Set the required App ID field. Choose Import from Disk to obtain app-specific package information from an app stored on your local system. The APP ID field (a string in reverse-DNS format) is automatically filled in. For example, if choosing the Chrome app for an Apple iOS policy, the APP ID field is set to com.google.chrome.ios . For Chrome on Android, it would be set to com.android.chrome . Alternatively, you may enter this app-specific information directly. Specify reverse-DNS format using a wildcard, for example, specify com.cisco.* to tunnel all Cisco apps, instead of listing each one in its own rule. The wildcard must be the last character in the APP ID entry. When configuring Per App VPN in a managed environment, verify that the ASA policy allows the same apps to tunnel as the MDM policy. Specifying *.* as the APP ID allows ALL apps to tunnel and ensures that the MDM policy is the only arbiter of tunneled apps. Step 3 (Optional) Select a listed app and configure more parameters if desired. Minimum Version—The minimum version of the chosen app as specified in the package’s manifest attribute android: versionCode . Match Certificate ID—A digest of the application signing certificate. Allow Shared UID—Default value is true. If set to false, applications with an android: sharedUserId attribute specified in the package manifest will not match this rule, and are prevented from accessing the tunnel. Step 4 Click File > Save to save this Per App VPN policy. Step 5 Select Policy > View Policy to view the representation of the defined policy. Copy this string, it is the string that becomes the value of a perapp custom attribute on the ASA. Define a Per App VPN Policy for Apple iOS Devices The policy for Per App VPN on Apple iOS devices is entirely controlled by the MDM facilities. Therefore, AnyConnect must allow ALL apps, and MDM must configure per app policies to specify the particular apps that can be tunneled. Before You Begin The Cisco AnyConnect Enterprise Application Selector requires Java 7 or later. Procedure Step 1 Start the application selector and choose the Apple iOS mobile device platform. Step 2 Set the required App ID field to *.* . This setting allows ALL apps to tunnel through AnyConnect and ensures that the MDM per app policy is the only arbiter of tunneled apps. Step 3 Click File > Save to save this Per App VPN policy. Step 4 Select Policy > View Policy to view the representation of the defined policy. Copy this string, it is the string that becomes the value of a perapp custom attribute on the ASA. Create Per App Custom Attributes Procedure Step 1 In ASDM, navigate to Configuration > Remote Access VPN > Network (Client) Access > Advanced > AnyConnect Custom Attributes to configure a custom attribute type. Step 2 Choose Add or Edit and set the following in the Create / Edit Custom Attribute Type pane: Enter perapp as the type. The type must be perapp , it is the only type of attribute understood by the AnyConnect client for Per App VPN. Enter a description of your choosing. Step 3 Click OK to close this pane. Step 4 Navigate to Configuration > Remote Access VPN > Network (Client) Access > Advanced > AnyConnect Custom Attribute Names to configure a custom attribute. Step 5 Choose Add or Edit and set the following in the Create / Edit Custom Attribute Name pane: Choose the perapp attribute Type . Enter a Name . This name is used to assign this attribute to a policy. Add one or more values by copying the BASE64 format from the policy tool and pasting it here. Each value cannot exceed 420 characters. If your value exceeds this length, add multiple values for the additional value content. The configured values are concatenated before being sent to the AnyConnect client. Assign a Custom Attribute to a Policy on the ASA The perapp custom attribute can be assigned to a Group Policy or a Dynamic Access Policy. Procedure Step 1 Open the policy on the ASA: For a Group Policy navigate to Configuration > Remote Access VPN > Network (Client) Access > Group Policies > Add / Edit > Advanced > AnyConnect Client > Custom Attributes . For a Dynamic Access Policy navigate to Configuration > Remote Access VPN > Network (Client) Access > Dynamic Access Policies Add / Edit . In the Access/Authorization Policy Attributes section select the AnyConnect Custom Attributes tab. Step 2 Click Add or Edit an existing attribute to open the Create / Edit Custom Attribute pane. Step 3 Select the predefined perapp attribute type from the drop-down list. Step 4 Choose Select Value and select a predefined value from the drop-down list Step 5 Click OK to close the open configuration panes. Configure Mobile Device Connections in the AnyConnect VPN Profile The AnyConnect VPN Client Profile is an XML file that specifies client behavior and defines VPN connection entries. Each connection entry specifies a secure gateway that is accessible to the endpoint device and other connection attributes, policies, and constraints. Use the AnyConnect Profile Editor to create a VPN client profile that includes host connection entries for mobile devices. Connection entries defined in the VPN profile delivered to mobile devices from the ASA cannot be modified or deleted by the user. Users can modify and delete only the connection entries that they create manually. AnyConnect retains only one current VPN Client Profile on the mobile device at a time. Upon startup of an automatic or manual VPN connection, the new VPN profile entirely replaces the current profile. If the user manually deletes the current profile, the profile is removed and all connection entries defined in this profile are deleted. Procedure Step 1 Configure basic VPN access. See Configure VPN Access for procedures that are common to desktop and mobile endpoints considering the following exceptions: For all platforms except Apple iOS, regardless of your Auto Reconnect specification, AnyConnect Mobile always attempts to ReconnectAfterResume. For Apple iOS only, Disconnect On Suspend is supported. When Disconnect On Suspend is chosen, AnyConnect disconnects and then releases the resources assigned to the VPN session. It will only reconnect in response to a user’s manual connection or an On Demand connection (if configured). AnyConnect Mobile ignores the Local LAN Access setting, always allowing Local LAN Access regardless of the setting in the Client profile. Step 2 Configure Mobile Specific Attributes: In the VPN Client Profile, select Server List in the navigation pane. Select Add to add a new server entry to the list, or select a server entry from the list and press Edit to open the Server List Entry dialog box. Configure mobile specific parameters as described in AnyConnect Profile Editor, Mobile Settings. Click OK Step 3 Distribute the VPN client profile in one of the following ways: Configure the ASA to upload a client profile onto the mobile device upon VPN connectivity. See The AnyConnect Profile Editor chapter for instructions on how to import the VPN client profile to the ASA and associate it with a group policy. Provide the user with an AnyConnect URI link to import a client profile. (Android and Apple iOS only) See Import a VPN Client Profile to provide this kind of deployment procedure to your users. Have the user import an AnyConnect profile using Profile Management on the mobile device. (Android and Apple iOS only) See the appropriate mobile device User Guide for device-specific procedures. AnyConnect Profile Editor, Mobile Settings Apple iOS / Android Settings Certificate Authentication —The Certificate Authentication policy attribute associated with a connection entry specifies how certificates are handled for this connection. Valid values are: Automatic —AnyConnect automatically chooses the client certificate with which to authenticate when making a connection. In this case, AnyConnect views all the installed certificates, disregards those certificates that are out of date, applies the certificate matching criteria defined in VPN client profile, and then authenticates using the certificate that matches the criteria. This happens every time the device user attempts to establish a VPN connection. Manual —AnyConnect searches for a certificate from the AnyConnect certificate store on the Android device when the profile is downloaded and does one of the following: If AnyConnect finds a certificate based on the certificate matching criteria defined in the VPN client profile, it assigns that certificate to the connection entry and uses that certificate when establishing a connection. If a matching certificate cannot be found, the Certificate Authentication policy is set to Automatic. If the assigned certificate is removed from the AnyConnect certificate store for any reason, AnyConnect resets the Certificate Authentication policy to Automatic. Disabled —A client certificate is not used for authentication. Make this Server List Entry active when profile is imported —Defines a server list entry as the default connection once the VPN profile has been downloaded to the device. Only one server list entry can have this designation. The default value is disabled. Apple iOS Only Setting Reconnect when roaming between 3G/Wifi networks —When enabled (default), AnyConnect does not limit the time that it takes to try to reconnect after losing a connection, after the device wakes up, or after changes occur in the connection type (such as EDGE(2G), 1xRTT(2G), 3G, or Wi-Fi). This feature provides seamless mobility with a secure connection that persists across networks. It is useful for applications that require a connection to the enterprise, but consumes more battery life. If Network Roaming is disabled and AnyConnect loses a connection, it tries to re-establish a connection for up to 20 seconds if necessary. If it cannot, the device user or application must start a new VPN connection if one is necessary. Note Network Roaming does not affect data roaming or the use of multiple mobile service providers. Connect on Demand (requires certificate authorization) —This field allows you to configure the Connect on Demand functionality provided by Apple iOS. You can create lists of rules that are checked whenever other applications start network connections that are resolved using the Domain Name System (DNS). Connect on Demand is an option only if the Certificate Authentication field is set to Manual or Automatic. If the Certificate Authentication field is set to Disabled, this check box is dimmed. The Connect on Demand rules, defined by the Match Domain or Host and the On Demand Action fields, can still be configured and saved when the check box is dimmed. Match Domain or Host —Enter the hostnames (host.example.com), domain names (.example.com), or partial domains (.internal.example.com) for which you want to create a Connect on Demand rule. Do not enter IP addresses (10.125.84.1) in this field. On Demand Action Specify one of the following actions when a device user attempts to connect to the domain or host defined in the previous step: Never connect —iOS will never start a VPN connection when rules in this list are matched. Rules in this list take precedence over all other lists Note When Connect On Demand is enabled, the application automatically adds the server address to this list. This prevents a VPN connection from being automatically established if you try accessing the server’s clientless portal with a web browser. Remove this rule if you do not want this behavior. Connect if Needed —iOS will start a VPN connection when rules in this list are matched only if the system could not resolve the address using DNS. Always Connect —Always connect behaviour is release dependent: On Apple iOS 6, iOS will always start a VPN connection when rules in this list are matched. On iOS 7.x, Always Connect is not supported, when rules in this list are matched they behave as Connect If Needed rules. On later releases, Always Connect is not used, configured rules are moved to the Connect If Needed list and behave as such. Add or Delete —Add the rule specified in the Match Domain or Host and On Demand Action fields to the rules table, or delete a selected rule from the rules table. Automate AnyConnect Actions Using the URI Handler The URI handler in AnyConnect lets other applications pass action requests in the form of Universal Resource Identifiers (URIs) to AnyConnect. To simplify the AnyConnect user setup process, embed URIs as links on web pages or e-mail messages, and give users instructions to access them. Before You Begin URI handling in the AnyConnect application is disabled by default. Mobile device users allow this functionality by setting the External Control app setting to Enable or Prompt. When enabled, external control allows all URI commands without user interaction. When set for prompting, the user is notified of URI activity and allows or disallows it at request time. You should inform your users how to respond to prompts associated with URI handling if you are using them. You must use URL encoding when entering URI handler parameter values. Use a tool such as the one in this link to encode an action request. Also, refer to provided examples below. In the URI, %20 represents a space, %3A represents a colon (:), %2F represents a forward slash (/), and %40 represents an ampersand (@). Slashes in the URI are optional. Provide your users with any of the following actions. Generate a VPN Connection Entry Use this AnyConnect URI handler to simplify the generation of an AnyConnect connection entry for users. anyconnect: [ // ] create [ / ] ?name = Description &host = ServerAddress [ &Parameter1 = Value &Parameter2 = Value . ] Guidelines The host parameter is required, all other parameters are optional. When the action runs on the device, AnyConnect saves all the parameter values that you enter to the connection entry associated with that name and host . Use a separate link for each connection entry that you want to add to the device. Specifying multiple create connection entry actions in a single link is not supported. Parameters name —Unique name for the connection entry to appear in the connection list of the AnyConnect home screen and the Description field of the AnyConnect connection entry. AnyConnect responds only if the name is unique. We recommend using a maximum of 24 characters to ensure that they fit in the connection list. Use letters, numbers, or symbols on the keyboard displayed on the device when you enter text into a field. The letters are case-sensitive. host —Enter the domain name, IP address, or Group URL of the ASA with which to connect. AnyConnect inserts the value of this parameter into the Server Address field of the AnyConnect connection entry. protocol (optional, defaults to SSL if unspecified)—The VPN protocol used for this connection. The valid values are: authentication (optional, applies when protocol specifies IPsec only, defaults to EAP-AnyConnect)—The authentication method used for an IPsec VPN connection. The valid values are: ike-identity (required if authentication is set to EAP-GTC, EAP-MD5, or EAP-MSCAPv2)—The IKE identify when AUTHENTICATION is set to EAP-GTC, EAP-MD5, or EAP-MSCHAPv2. This parameter is invalid when used for other authentication settings. netroam (optional, applies to Apple iOS only)—Determines whether to limit the time that it takes to reconnect after the device wakes up or after a change to the connection type (such as EDGE, 3G, or Wi-Fi).This parameter does not affect data roaming or the use of multiple mobile service providers. The valid values are: true—(Default) This option optimizes VPN access. AnyConnect inserts the value ON into the Network Roaming field of the AnyConnect connection entry. If AnyConnect loses a connection, it tries to establish a new one until it succeeds. This setting lets applications rely on a sustained connection to the VPN. AnyConnect does not impose a limit on the time that it takes to reconnect. false—This option optimizes battery life. AnyConnect associates this value with the OFF value in the Network Roaming field of the AnyConnect connection entry. If AnyConnect loses a connection, it tries to establish a a new one for 20 seconds and then stops trying. The user or application must start a new VPN connection if one is necessary. keychainalias (optional)—Imports a certificate from the System Certificate Store to the AnyConnect Certificate Store. This option is for the Android mobile platform only. If the named certifiate is not already in the system store, the user will be prompted to choose and install it before being prompted to allow or deny it being copied into the AnyConnect store. External Control must be enabled on the mobile device. The following example creates a new connection entry named SimpleExample whose IP address is set to vpn.example.com with the certificate named client assigned to it for authentication. usecert (optional)—Determines whether to use a digital certificate installed on the device when establishing a VPN connection to the host. The valid values are: true (default setting)—Enables automatic certificate selection when establishing a VPN connection with the host. Turning usecert to true without specifying a certcommonname value sets the Certificates field to Automatic, selecting a certificate from the AnyConnect certificate store at connection time. false—Disables automatic certificate selection. certcommonname (optional, but requires the usecert parameter)—Matches the Common Name of a valid certificate pre-installed on the device. AnyConnect inserts the value into the Certificate field of the AnyConnect connection entry. To view this certificate installed on the device, tap Diagnostics > Certificates . You might need to scroll to view the certificate required by the host. Tap the detail disclosure button to view the Common Name parameter read from the certificate, as well as the other values. useondemand (optional, applies to Apple iOS only and requires the usecert, certcommonname parameters, and domain specifications below)—Determines whether applications, such as Safari, can start VPN connections. Valid values are: false (Default)—Prevents applications from starting a VPN connection. Using this option is the only way to prevent an application that makes a DNS request from potentially triggering a VPN connection. AnyConnect associates this option with the OFF value in the Connect on Demand field of the AnyConnect connection entry. true—Lets an application use Apple iOS to start a VPN connection. If you set the useondemand parameter to true, AnyConnect inserts the value ON into the Connect on Demand field of the AnyConnect connection entry. (domainlistalways or domainlistifneeded parameter required if useondemand=true) domainlistnever (optional, requires useondemand=true)—Lists the domains to evaluate for a match to disqualify the use of the Connect on Demand feature. This list is the first one AnyConnect uses to evaluate domain requests for a match. If a domain request matches, AnyConnect ignores the domain request. AnyConnect inserts this list into the Never Connect field of the AnyConnect connection entry. This list lets you exclude certain resources. For example, you might not want an automatic VPN connection over a public-facing web server. An example value is www.example.com . domainlistalways (domainlistalways or domainlistifneeded parameter required if useondemand=true)—Lists the domains to evaluate for a match for the Connect on Demand feature. This list is the second one AnyConnect uses to evaluate domain requests for a match. If an application requests access to one of the domains specified by this parameter and a VPN connection is not already in progress, Apple iOS attempts to establish a VPN connection. AnyConnect inserts this list into the Always Connect field of the AnyConnect connection entry. An example value list is email.example.com,pay.examplecloud.com . domainlistifneeded (domainlistalways or domainlistifneeded parameter required if useondemand=true)—AnyConnect evaluates a domain request for a match against this list if a DNS error occurred. If a string in this list matches the domain, Apple iOS attempts to establish a VPN connection. AnyConnect inserts this list into the Connect if Needed field of the AnyConnect connection entry. The most common use case for this list is to obtain brief access to an internal resource that is not accessible in a LAN within the corporate network. An example value is intranet.example.com . Use a comma-delimited list to specify multiple domains. The Connect-on-Demand rules support only domain names, not IP addresses. However, AnyConnect is flexible about the domain name format of each list entry, as follows: Источник Читайте также:  Флеш плеер для андроида планшет Оцените статью Вам также может понравиться Как деактивировать режим наушников на смартфоне с Android? Когда к мобильному устройству присоединены наушники Обзор игры Джелли-Джу для Android В последние годы популярность мобильных игр резко возросла Лучшие шахматные приложения для iOS и Android Нынешний читерский скандал в шахматном мире сейчас Что хотят увидеть пользователи от Android 5.0 Key Lime Pie ОС Google Android развивается, и по всему видимому Правообладателям Политика конфиденциальности Контакты