Cisco Cisco Web Security Appliance S390 Release Notes
9
Release Notes for AsyncOS 9.1.x for Cisco Web Security Appliances
Installation and Upgrade Notes
Availability of Kerberos Authentication for Operating Systems and Browsers
You can use Kerberos authentication with these operating systems and browsers:
•
Windows servers 2003, 2008, 2008R2 and 2012
•
Latest releases of Safari and Firefox browsers on Mac (OSX Version 10.5+)
•
IE (Version 7+) and latest releases of Firefox and Chrome browsers on Windows 7 and XP.
Kerberos authentication is not available with these operating systems and browsers:
•
Windows operating systems not mentioned above
•
Browsers not mentioned above
•
iOS and Android
Deploying a Virtual Appliance
To deploy a virtual appliance, see the Cisco Content Security Virtual Appliance Installation Guide,
available from
available from
Migrating from a Hardware Appliance to a Virtual Appliance
Note
In order to migrate your configuration, both the old and the new appliances must be running the identical
AsyncOS version, including build number. The AsyncOS version you choose must be supported on both
appliances.
AsyncOS version, including build number. The AsyncOS version you choose must be supported on both
appliances.
Step 1
Set up your virtual appliance with a supported AsyncOS release using the documentation described in
Step 2
Upgrade your hardware appliance to this AsyncOS release.
Step 3
Save the configuration file from your upgraded hardware appliance.
Step 4
Load the configuration file from the hardware appliance onto the virtual appliance.
If your hardware and virtual appliances have different IP addresses, deselect Load Network Settings
before loading the configuration file.
before loading the configuration file.
Step 5
Commit your changes.
Step 6
Go to Network > Authentication and join the domain again. Otherwise identities won’t work.
Configuration Files
When you upgrade AsyncOS for Web from the web interface or Command Line Interface (CLI), the
configuration is saved to file in the /configuration/upgrade directory. You can access the upgrade
directory using an FTP client. Each configuration file name is appended with the version number, and
passwords in the configuration file are masked so they are not human readable. (bug 47966)
configuration is saved to file in the /configuration/upgrade directory. You can access the upgrade
directory using an FTP client. Each configuration file name is appended with the version number, and
passwords in the configuration file are masked so they are not human readable. (bug 47966)