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

Google Search Appliance: Managing Search for Controlled-Access Content 53
Chapter 3
Use Cases with Public and Secure
Serve for Multiple Authentication
Mechanisms
Chapter 3
This section provides more detailed explanation of how to set up crawl for controlled-access content
and how to set up the Google Search Appliance to centralize serve-time authentication.
Use Case 1: HTTP Basic or NTLM HTTP Controlled-
Access Content with Public Serve
The ABC Company wants to make its controlled-access content discoverable using intranet search. The
content is stored on these internal servers:
• events.abc.int is a simple web server that uses HTTP Basic authentication. This server contains
information about internal company events.
• announce.abc.int is a Microsoft IIS web server that uses Integrated Windows Authentication over
NTLM HTTP. This server contains announcements for employees.
• directory.abc.int is another Microsoft IIS server. This server provides phone and office location
information about employees. For the purpose of this example, let’s suppose that content from this
server is best provided by a web feed.
All these servers are located on the same domain, abc_corp. Although authentication is required by
each of these servers, this information isn’t sensitive. ABC Company wants to serve the snippet results
as public content, viewable by any employee. There is no reason to require the search appliance to
perform document-level authentication when serving results.
ABC Company has these people who interact with this content:
• Adam, the system administrator
• Sandra, the search appliance administrator
• Eric, an employee who needs to find content