Google Search Appliance Getting the Most from Your Google Search Appliance - Manual (Page 68)

Google Search Appliance: Getting the Most from Your Google Search Appliance Essentials 68
• x.509 Certificates for user authentication
When using the SAML Authorization SPI to serve secure content results from SMB shares, you must use
Kerberos for user authentication.
Useful Knowledge for Writing Web Services
To write an Identity Provider or Policy Decision Point web service, you need a basic understanding of the
following technologies.
• XML—Extensible Markup Language
• SAML 2.0—An XML-based standard whose primary use case is inter-domain single sign-on
• SOAP 1.1—The Simple Object Access Protocol, an XML-based protocol for exchanging information
over the Internet
Configuring the Search Appliance for Using the SPIs
Configure the search appliance to use the Authentication SPI by using the SAML tab of the Serving >
Universal Login Auth Mechanisms page. Configure the search appliance to use the Authorization SPI
by using the Serving > Access Control page.
Learn More about the SAML Authentication and Authorization SPIs
For more information about how the SAML Authentication and Authorization SPIs work and how to set
up the Identity Provider and Policy Decision Point web services that are required by the Authentication
and Authorization SPIs, refer to the Authentication/Authorization for Enterprise SPI Guide.
For more information on search appliance configuration for use with these SPIs, refer to the section
“The SAML Authentication Service Provider Interface (SPI)” in Managing Search for Controlled-Access
Content.
Developing Custom Connectors
Google provides the Enterprise connector framework for developing custom connectors to non-web
repositories. The Google Enterprise Connector Framework project on code.google.com provides open
source software for the connector manager and connectors. Developers using the resources provided
in this project can create connectors for virtually any type of document-based repository. Google does
not support the open-source software or changes you make to the open-source software.
Useful Knowledge for Developing Connectors
To develop a custom content connector by using the Connector Framework, you need a basic
understanding of the following technologies:
• A content management system and its API
• Java programming with JDK 1.4.2 or later
• The Spring Framework and Inversion of Control (IOC)