Cisco Cisco Web Security Appliance S670 Release Notes
68
I R O N P O R T A S Y N C O S 6 . 3 . 7 F O R W E B R E L E A S E N O T E S
NTLM authentication settings might not save correctly
When NTLM Basic authentication is configured and then disabled in a web access policy
group, settings are saved and you do not have to repeat the setup if you re-enable. Currently,
the appliance fails to save the authentication scheme and the setting defaults to “Use
NTLMSSP.” [Defect ID: 30255]
group, settings are saved and you do not have to repeat the setup if you re-enable. Currently,
the appliance fails to save the authentication scheme and the setting defaults to “Use
NTLMSSP.” [Defect ID: 30255]
Issue with manual updates and WCCP
Manual updates fail to download when the appliance is configured as a WCCP transparent
proxy with IP spoofing enabled. The manual update succeeds when IP spoofing is disabled.
[Defect ID: 32114]
proxy with IP spoofing enabled. The manual update succeeds when IP spoofing is disabled.
[Defect ID: 32114]
Changing NTLM non-admin user credentials requires AD server configuration
When changing the non-admin user credentials for the Active Directory server on the
appliance, the credentials used to join the Active Directory domain must also be configured
on the Active Directory server. The new credentials must have at least the following
permissions on the “Computers” container in the “Active Directory Users and Computers”
MMC applet: Create Computer Objects, and Delete Computer Objects. [Defect ID: 29868]
appliance, the credentials used to join the Active Directory domain must also be configured
on the Active Directory server. The new credentials must have at least the following
permissions on the “Computers” container in the “Active Directory Users and Computers”
MMC applet: Create Computer Objects, and Delete Computer Objects. [Defect ID: 29868]
Response message for manual updates might be inconsistent
The result code for manually updated components is always “
Success — Component was
successfully updated.
” In some instances, update status and descriptive messaging
might not reflect actual activity. [Defect IDs: 25069, 28629, 31966]
Partial messaging for denied HTTP CONNECT requests
Some browsers truncate HTTP data that is sent in response to a CONNECT request. This
means that if the Web Security appliance denies a CONNECT request, the “
means that if the Web Security appliance denies a CONNECT request, the “
page cannot be
displayed: Access Denied
” error message might be incomplete. [Defect ID: 37384,
26979, 23483, 23480]
No alerts for failed authentication servers
The Web Security appliance does not currently support alert messaging for failed
authentication servers. To manage the appliance during such an event, use the advanced
authentication settings to specify an action if the authentication server becomes unavailable.
This option is located on the Network > Authentication page. [Defect ID: 27887]
authentication servers. To manage the appliance during such an event, use the advanced
authentication settings to specify an action if the authentication server becomes unavailable.
This option is located on the Network > Authentication page. [Defect ID: 27887]
System reports false hard disk failure
Transient reports of hard disk failures might be erroneous. Performing a same drive hot swap
resets the RAID firmware and likely resolves this issue. [Defect ID: 28821]
resets the RAID firmware and likely resolves this issue. [Defect ID: 28821]
Issue with temperature alerts
The system health daemon fails to send alerts when the environmental temperature reaches
critical levels. To prevent disk failure due to high temperatures, power down the appliance
before the ambient air temperature reaches 95 degrees Fahrenheit. [Defect ID: 28958]
critical levels. To prevent disk failure due to high temperatures, power down the appliance
before the ambient air temperature reaches 95 degrees Fahrenheit. [Defect ID: 28958]