Cisco Cisco Web Security Appliance S170 사용자 가이드
9-5
Cisco IronPort AsyncOS 7.5.7 for Web User Guide
Chapter 9 Identities
Evaluating Identity Group Membership
the non-Identity policy groups, it matches only non-Identity groups that specify “All Identities” and
apply to “All Users.” Typically, this is the global policy, such as the global Access Policy. For a
diagram of how this occurs, see
apply to “All Users.” Typically, this is the global policy, such as the global Access Policy. For a
diagram of how this occurs, see
•
Cookie-based authentication surrogates and explicit requests. The behavior is different,
depending on whether or not credential encryption is enabled:
depending on whether or not credential encryption is enabled:
–
Credential encryption enabled. The behavior is the same as cookie-based authentication with
transparent requests, as described previously. See also
transparent requests, as described previously. See also
.
–
Credential encryption disabled. The Web Proxy uses no surrogates. HTTPS and FTP over
HTTP requests are authenticated and matched to Identity groups like HTTP requests. For a
diagram of how this occurs, see
HTTP requests are authenticated and matched to Identity groups like HTTP requests. For a
diagram of how this occurs, see
Understanding How Authentication Scheme Affects Identity Groups
You define the authentication scheme for each Identity group, not at each realm or sequence. That means
you can use the same NTLM realm or a sequence that contains an NTLM realm and use it in Identity
groups that use either the NTLMSSP, Basic, or “Basic or NTLMSSP” authentication schemes.
you can use the same NTLM realm or a sequence that contains an NTLM realm and use it in Identity
groups that use either the NTLMSSP, Basic, or “Basic or NTLMSSP” authentication schemes.
Table 9-1
Matching HTTPS and FTP over HTTP Requests to Identities
Surrogate
Types
Types
Explicit Requests
Transparent Requests
No Surrogate
HTTPS and FTP over HTTP requests
are matched like HTTP requests.
are matched like HTTP requests.
N/A
IP-based
HTTPS and FTP over HTTP requests
are matched like HTTP requests.
are matched like HTTP requests.
FTP over HTTP requests are matched like
HTTP requests.
HTTP requests.
HTTPS requests are matched like HTTP
requests under any of the following
conditions:
requests under any of the following
conditions:
•
A previous HTTP request was
authenticated using an identity with an
IP-based surrogate.
authenticated using an identity with an
IP-based surrogate.
•
A previous HTTP request was not
authenticated, but the HTTPS Proxy is
configured to decrypt the first HTTPS
request.
authenticated, but the HTTPS Proxy is
configured to decrypt the first HTTPS
request.
Otherwise, if a previous HTTP request was
not authenticated and the HTTPS Proxy is
configured to deny the request, the HTTPS
request fails.
not authenticated and the HTTPS Proxy is
configured to deny the request, the HTTPS
request fails.
Cookie-based
The client is not prompted for
authentication.
authentication.
Note: When credential encryption is
disabled, no surrogates are used, and
HTTPS requests are matched like HTTP
requests.
disabled, no surrogates are used, and
HTTPS requests are matched like HTTP
requests.
The client is not prompted for
authentication.
authentication.