01.01.2013 Views

Web Gateway 7.1.5 Product Guide - McAfee

Web Gateway 7.1.5 Product Guide - McAfee

Web Gateway 7.1.5 Product Guide - McAfee

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

5<br />

Authentication and access management<br />

Filtering users<br />

Options for retrieving user information<br />

This section explains how to retrieve information for authenticating users yourself instead of having<br />

them provided by the default process.<br />

You might want to use the options described here when dealing, for example, with user requests that<br />

provide no header information on the user name and password, or when you use an authentication<br />

method, such as Kerberos, that provides no user group information.<br />

Filling the Authentication.RawCredentials property with values<br />

Configuring authentication basically means to configure a rule that evaluates user credentials, using the<br />

Authentication.Authenticate property, and executes the Authenticate action, which asks a user to<br />

submit credentials if the evaluation shows that this user is not authenticated.<br />

Note: The logon window for submitting authentication credentials is presented to the user by the<br />

Authenticate action. This is not part of processing the Authentication.Authenticate property, which is only the<br />

criteria that must be matched to let the Authenticate action be executed.<br />

The Authentication.Authenticate property gets the credentials it evaluates from the<br />

Authentication.RawCredentials property. This property is internally “filled” with these values by the<br />

proxy module. The proxy module gets the values from the relevant header of the request that a user<br />

sends.<br />

You can fill the Authentication.RawCredentials property with a user name and password yourself. For<br />

this purpose, you need to encode these values in Base64 format.<br />

You might do this to handle requests that do not include a header with user name and password.<br />

However, if you know that a given user sends requests from a client with a particular IP address, you<br />

can configure a rule that sets the Authentication.RawCredentials property to the relevant user name<br />

and password when a request with that address is received.<br />

Another rule, which includes the Authentication.Authenticate property, can then evaluate the<br />

credentials and eventually execute the Authenticate action.<br />

The two rules could look as follows:<br />

Name<br />

Set values for Authentication.RawCredentials<br />

Criteria Action Event<br />

Client.IP equals 10.143.104.45 –> Continue — Set Authentication.RawCredentials =<br />

“Basic Ym9ic21pdGg6dGVzdHBhc3M=”<br />

and:<br />

Name<br />

Authenticate with User Database<br />

Criteria Action<br />

Authentication.Authenticate equals false –> Authenticate<br />

122 <strong>McAfee</strong> <strong>Web</strong> <strong>Gateway</strong> <strong>7.1.5</strong> <strong>Product</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!