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

Google Search Appliance: Managing Search for Controlled-Access Content 57
Currently, when employees search for protected personnel information, they are prompted for their
credentials by each authentication mechanism separately. AlphaLyon’s Information Technology
department has set an objective to centralize serve-time authentication for the various servers hosting
personnel information. This way, users need to provide their credentials only once for content
protected by several authentication mechanisms.
AlphaLyon has these people who interact with this content:
• Ashish, the search appliance administrator
• Tanya, the search appliance administrator
• Joseph, a manager who wants to view personnel information about people in his organization
This use case is based on the assumption that Tanya has added a connector for Documentum and the
content from the CMS has been traversed and fed into the search appliance. For information about
adding connectors, see Introducing Connectors.
Setting Up Crawl and Index
Ashish, the system administrator creates a user account for the search appliance, called ALSearch, and
sets up access policies that ensure that the ALSearch user account is authorized to view all files on
comp.alpha.int, and pers.def.int.
Next, Tanya sets up crawl and index of the controlled-access content by performing the following steps:
1. To provide the search appliance with credentials for crawling and indexing comp.alpha.int, which
is protected by HTTP Basic Authentication, and pers.def.int, which uses NTLM HTTP, Tanya opens
Crawl and Index > Crawler Access.
2. Tanya adds the following rows:
Tanya uses the account name and password for ALSearch that was provided by Ashish, the system
administrator. Note that, for http://comp.alpha.int/, the In Domain text box is cleared. This
cleared checkbox instructs the search appliance to authenticate using HTTP Basic. For http://
pers.def.int/, Tanya supplies the domain, which tells the search appliance to authenticate
against the server using NTLM HTTP.
The Make Public checkbox is also cleared. The search appliance has full access to the server, but
labels any results from them as “secure” and requires authentication and authorization checks
before displaying secure content in the search results.
3. Tanya clicks Save Crawler Access Configuration.
4. Next, Tanya needs to provide the search appliance with credentials for crawling and indexing
content protected by single sign-on systems (http://insidealpha.com and
apacheserver.alphainside.com), so she opens Crawl and Index > Forms Authentication.
5. In the Sample Forms Authentication protected URL box, Tanya enters http://
insidealpha.com/inside.html.
For URLs Matching Pattern, Use: Username: In Domain: Password: Confirm
Password: Make
Public:
http://comp.alpha.int/ ALSearch ******* *******
https://pers.def.int/ ALSearch aphalyon_corp ******* *******