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

Google Search Appliance: Managing Search for Controlled-Access Content 6
Which Sections of this Guide Should I Read ?
This guide helps you to answer the following questions:
• How do I set up my search appliance to crawl and index controlled-access content?
• Once I have indexed controlled-access content, how do I specify the content that is visible to a user
during serve? Public content (access=p) is available in all search results, while secure content
(access=s) is only visible to authorized users.
Because some methods of accessing controlled-access content do not support secure serve, the
answers to these questions depend on your existing access control infrastructure, and whether your
content sources require secure serve.
The following table explains which sections in this guide are most relevant for each access method, and
provides links to those sections.
Access Method Access Type Suggested Crawl Method Suggested Serve Method
HTTP Basic or NTLM
HTTP Public or
secure Crawler Access (see
“Configuring Crawl for HTTP
Basic or NTLM HTTP” on
page 10) HTTP Basic or NTLM
authentication (see “HTTP-
Based Authentication” on
page 23)
Access content on a
Windows or SMB/
CIFS file share Public or
secure Crawler Access (see
“Configuring Crawl for HTTP
Basic or NTLM HTTP” on
page 10) Pass user credentials and
optionally authenticate with
LDAP (see “Integrating the
Search Appliance with an
LDAP Server” on page 34)
Single login domain:
Windows (Kerberos)
Authentication for
Windows Server or
Sharepoint Server Public or
secure Crawler Access (see
“Configuring Crawl for HTTP
Basic or NTLM HTTP” on
page 10) IWA (Integrated Windows
Authentication) / Kerberos
authentication (see
“Kerberos-Based
Authentication” on page 25)
Single login domain:
one set of domain
credentials provides
access to all content,
and the login form
does not use frames
or JavaScript. Public or
secure Forms Authentication (see
“Configuring Crawl for Cookie-
Based Access” on page 10) Cookie-based authentication
(see “Cookie-Based
Authentication” on page 20)
Single login domain:
one set of domain
credentials provides
access to all content.
The login form is
plain HTML. Single or
multiple cookie
domains. Public or
secure Forms Authentication (see
“Configuring Crawl for Cookie-
Based Access” on page 10) Cookie-based authentication
(see “Cookie-Based
Authentication” on page 20)