Configuration of User Management and Security 

Purpose

The User Management (UM) component has two application programming interfaces (APIs) based on the same underlying data: a .NET-based API and a Java API. You must provide each of these APIs with certain information, such as the location of the LDAP directory server. This data is required so that the Enterprise Portal knows where to find the central user data.

There is a common configuration tool for both APIs. This tool stores the configuration data in the Windows registry. This data is then exported to a configuration file in the Java iView Runtime when the Java servlet engine is started. The configuration file on the Java iView Runtime also contains attribute mapping information that maps the attributes used by the Java API to the attributes used in the schema on your corporate LDAP directory server.

 

Prerequisites

You have set up a corporate LDAP directory containing all the portal users.

 

Process Flow

You should configure the User Management component once initially, before using the Enterprise Portal. The process is as follows:

...

      1.      You configure the User Management component using the configuration tool. This is described in the following sections:

Setting General User Management and Security Settings

Defining Location of Central User Data Repository

Defining User Repository to Be Used for Authentication

Defining Location of User-to-Role Assignments

Defining Location of User Mapping Data

Defining Parser for Client Certificate

In a clustered environment all machines in the cluster must use the same user management configuration. See Setting General User Management and Security Settings for details on how to use an existing configuration for your portal installation. See also the section on Creating a User Management Configuration in the SAP Enterprise Portal Installation Guide.

      2.      You restart the Java servlet engine.

The Enterprise Portal copies the configuration data from the Microsoft registry to the configuration file in the Java iView Runtime used by the Java UM API.

      3.      You restart the portal Web server (Microsoft Internet Information Server).

      4.      You now map the attributes of the Java UM API to the attributes used in your LDAP schema. This is described in Mapping Attributes.

 

Result

All of the users contained in your central user data repository can log on to the portal. User data is also available to all of the iViews running in the Enterprise Portal.