Blue Coat Systems Time Clock Proxy SG Manuale Utente
ProxySG Content Policy Language Guide
144
user=
Tests the authenticated username associated with the transaction. This trigger is only available if the
transaction was authenticated (that is, the
transaction was authenticated (that is, the
authenticate( )
property was set to something other
than
no
, and the
proxy_authentication( )
property was not set to
no
).
Syntax
user=user_name
where
user_name
is a username.
•
NTLM realm: Usernames are case-insensitive.
In NTLM this provides the flexibility of matching either a full username (which includes the NT
Domain) or relative username (which does not include the NT Domain).
Domain) or relative username (which does not include the NT Domain).
For example:
user=bluecoat\mary.jones
matches a complete username, and
user=mary.jones
matches a relative name.
•
UNIX (local) realm: Usernames are case-sensitive.
•
RADIUS realm: Username case-sensitivity depends on the RADIUS server’s setting. The
case-sensitive setting should also be set correctly when defining a RADIUS realm in the ProxySG.
case-sensitive setting should also be set correctly when defining a RADIUS realm in the ProxySG.
•
LDAP realm: Username case-sensitivity depends on the LDAP server’s setting. The case-sensitive
setting should also be set correctly when defining an LDAP realm in ProxySG.
setting should also be set correctly when defining an LDAP realm in ProxySG.
In LDAP this provides the flexibility of matching either a fully qualified domain name or relative
username.
username.
For example:
user=”cn=mary.jones,cn=sales,dc=bluecoat,dc=com”
or
user=”uid=mary.jones,ou=sales,o=bluecoat”
matches a complete username, and
user=mary.jones
matches a relative name.
Layer and Transaction Notes
•
Use in
<Admin>
and
<Proxy>
layers.
Examples
; Test for user john.smith.
user=john.smith