PDF(4.0 KB) View with Adobe Reader on a variety of devices
ePub(83.6 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(68.5 KB) View on Kindle device or Kindle app on multiple devices
Updated:November 7, 2019
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
On iOS and Android, the platform restricts app access to persistent device identifiers like MAC address, iTunes UDID, and IMEI/MEID. These types of identifiers are typically used by AnyConnect for reporting and authorization of VPN connections. As a workaround, AnyConnect allows EMM/MDM to provision a device identifier that will be reported to the ASA, which forwards it as an RADIUS attribute via the AnyConnect Identifier Extensions protocol. Specifically, the identifier is reported in the device-uid and device-uid-global RADIUS attributes.
The identifier itself is treated as an opaque string by AnyConnect and must be no greater than 256 bytes in length. It is sent as a XML attribute, so it may not contain illegal characters such as: ", ', &, <
On iOS, AnyConnect parses VendorConfig section in the iOS MDM VPN configuration profile. The identifier must be provided as a string to the key DeviceUniqueIdentifier, as follows: