About Content Crawler Security Options
A crawler can use a range of credential types to access
a secure file.
If you need to apply credentials to access a file, you can use
any of the following options:
| SSO |
SSO must be configured in the portal and on the remote server,
using the instructions of your SSO vendor. |
| Basic Authentication |
Set the remote server to pass the user's basic
authentication headers to the remote resource. Both sources must be
using the same directory. For example, if a user logs in using an
IPlanet directory, it is unlikely they will be able to access an Exchange
resource. |
| Content Source credentials |
Content Source credentials are generally valid only for crawling
a database. Most other use cases require user-specific credentials. |
| User preferences via form-based authentication |
Preferences stored in the ALI database can be used to create
a cookie if the resource accepts session-based authentication. User
preferences generally cannot be used if the resource expects basic
authentication. For example, the Content Service for Notes uses this
approach when Notes is using session-based (cookie) authentication.
You must enter all User settings and User Information required by
a content crawler on the Preferences page of the Content Crawler editor. |
| Force users to log in |
If the required credentials are not available, redirect the
user to the appropriate page and/or provide an intelligible error
message. For example, the Content Service for Notes uses this approach
when Notes is using basic authentication. |
