Google Search Appliance Managing Search for Controlled-Access Content - Manual (Page 72)

Google Search Appliance: Managing Search for Controlled-Access Content 72
Scenario 1: Normal Forms Authentication
In Scenario 1, if the sample URL check fails because the user is not yet logged in, the content server
redirects the search appliance to a login system for log in, then the login system’s server redirects the
search appliance back to the content server after login.
Scenario 1 corresponds to Forms Authentication in the search appliance’s legacy authentication. If you
previously used legacy authentication Forms Authentication, and you need the same interactions with
Universal Login, set up your system as described in “Set Up for Scenario 1” on page 72.
Set Up for Scenario 1
For scenario 1, set up a cookie authentication rule by performing the following tasks:
• Specify a Sample URL
• Check When sample URL fails, expect the sample page to redirect to a form, and log in to that
form
The redirect to the login form is provided by the sample URL page response, so do not specify it in the
Redirect URL box.
Process Overview of Scenario 1
The following diagram provides an overview of the cookie authentication process in scenario 1. For
explanations of the numbers in the process, see the steps following the diagram.
1. The user requests a secure search.
2. The browser sends a GET message to the search appliance.
3. The search appliance checks its own session cookie to find out if authentication was previously
completed.
The search appliance sets a session cookie the first time a browser requests a secure search.