Cisco Cisco Web Security Appliance S170 사용자 가이드
9-10
Cisco IronPort AsyncOS 7.5.7 for Web User Guide
Chapter 9 Identities
Identifying Users Transparently
Step 2
Create an Access, Decryption, Routing, Data Security, or External DLP Policy and select the Identity
created in step
created in step
.
Step 3
In the Access, Decryption, Routing, Data Security, or External DLP Policy group membership, select
“Guests (users failing authentication)” for the Identity in step
“Guests (users failing authentication)” for the Identity in step
Step 4
Submit and commit your changes.
Note
You can configure the Web Proxy to request authentication again if an authenticated user is blocked from
a website due to restrictive URL filtering. To do this, enable the “Enable Re-Authentication Prompt If
End User Blocked by URL Category or User Session Restriction” global authentication setting. For more
information, see
a website due to restrictive URL filtering. To do this, enable the “Enable Re-Authentication Prompt If
End User Blocked by URL Category or User Session Restriction” global authentication setting. For more
information, see
.
Identifying Users Transparently
Traditionally, users identified by an authentication user name are explicitly prompted to enter a user
name and password. The credentials the user enters are then validated against an authentication server,
and then the Web Proxy applies the appropriate policies to the transaction based on the authenticated
user name.
name and password. The credentials the user enters are then validated against an authentication server,
and then the Web Proxy applies the appropriate policies to the transaction based on the authenticated
user name.
This Identity allows guest access.
Guests of this Identity are authorized to access the web.