Configuring credential groups, Cookie-based authentication – Google Search Appliance Managing Search for Controlled-Access Content User Manual
Page 20
Google Search Appliance: Managing Search for Controlled-Access Content
20
If this option is checked, the user is not required to type a username and password in the Universal
Login Form for this credential group. The user can submit the Universal Login Form and view search
results. However, if the user does not login, then search results do not include secure results protected
by that credential group.
If this option is not checked, the user is required to type a username and password in the Universal
Login Form. The user cannot view any search results until he has supplied his username and password.
He will keep being sent back to the Universal Login Form until he provides the correct credentials.
Adding a Credential Group
To create a new credential group:
1.
Click Serving > Universal Login.
2.
In the Credential Group Name box, type a name for the new credential group.
Credential group names can be up to 200 characters long and can contain only alphanumeric
characters, underscores, and hyphens. A name cannot begin with a hyphen.
3.
(Optional) Type the name that you want to appear on the Universal Login form in the Credential
Group Display Name box. There are no character or format restrictions on the Credential Group
Display Name.
4.
Select Require a user-name for this credential group? and Group is optional?, as described in
the preceding sections.
5.
Click Create New Credential Group.
The new credential group’s name appears in the list of credential groups.
Configuring Credential Groups
After you create a new credential group, you can configure it by adding credential group rules on the
Serving > Universal Login Auth Mechanisms page. This page provides tabs for a adding rules for the
following types of authentication mechanisms:
•
“Cookie-Based Authentication” on page 20
•
HTTP-based or NTLM authentication (see “HTTP-Based Authentication” on page 23)
•
“Client Certificate-Based Authentication” on page 24
•
“Kerberos-Based Authentication” on page 25
•
SAML (see “Configuring a Credential Group for SAML Authentication” on page 32)
•
•
Cookie-Based Authentication
During serve, secure content from sites that were crawled through a Forms Authentication rule are
handled by cookie-based authentication.