AnyConnect 3.1.x deployment to Mac OS X (10.8) clients.
I am using JAMF's Composer (a package building app) to repackage the AnyConnect 3.1 client with profiles to our Mac users. The newly-created package installs and works fine. But our AnyConnect clients are connecting to a Cisco ASA that is configured to use certificates for authentication. AD user certificates are already on each computer. Upon first launch, AnyConnect requests access to the System keychain (requiring admin credentials) and then it requests to sign the key "Configuration Profiles" in the user's keychain. Does anyone know of a way to avoid these hassles? Users do not have admin credentials.
I would like it if we could push out AnyConnect and just have it work upon first launch.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...