Permissions for Accessing Web Repositories 

Use

Users can access documents stored in Web repositories by means of a search with or without a permissions check.

Case A - No Permissions Check

The Web server for the Web repository does not support a permissions concept or no permissions are assigned. The search results are not checked for permissions.

 Case B - Permissions Check

The Web server for the Web repository supports a permissions concept and permissions are assigned. 

You want permissions to be checked when users attempt to access documents. The search function only displays documents in the search results if the user in question has the requisite permissions.

Using the security manager for Web repositories can considerable hamper performance, since additional requests are sent to the Web server.

Activities

Depending on which case is relevant for you, you have to carry out different configuration steps.

Case A - No Permissions Check

...

       1.      Register the remote Web server in an HTTP system.

Leave the User and Password parameters empty.

       2.      Create a Web site. Assign the Web site to the HTTP system you just created.

       3.      Configure a cache for the Web repository manager.

       4.      Configure a Web repository manager. In the configuration, select the cache and Web site you just created.

Leave the Security Manager parameter empty.

       5.      Create a new index (see Creating an Index) or edit an existing index and assign the Web repository to it. Select the crawler parameters that you want to use.

For more information, see Assigning Data Sources. You can also define a schedule (optional).

Case B - Permissions Check

...

       1.      Register the remote Web server in an HTTP system.

Leave the User and Password parameters empty.

       2.      Create a Web site. Assign the Web site to the HTTP system you just created.

       3.      Configure a cache for the repository manager (see Caches).

       4.      Configure a Web repository manager. In the configuration, select the cache and Web site you just created.

Choose Web Security Manager for the Security Manager parameter.

       5.      Create a new index (see Creating an Index) or edit an existing index and assign the Web repository to it. Select the crawler parameters that you want to use.

For more information, see Assigning Data Sources. You can also define a schedule (optional).

       6.      In the portal system landscape (System Administration → System Configuration → System Landscape), create an HTTP system (New System (from template)).

In the System Name and System ID field, enter the value of the System ID parameter for the HTTP system you created in step 1.

Enter an alias for the system. Note that the alias must be the same as the value of the System ID parameter for the HTTP system you created in step 1.

       7.      Each user enters his or her mapping data in the portal. As the administrator, you carry out the user mapping for the index_service service user. For more information, see Specifying User Mapping.