Defining Location of Central User Data Repository 

Use

In this step, you configure the portal to connect to the directory server where you store the central user data for the portal. You also specify how the hierarchy of groups and users is set up in your corporate LDAP directory.

 

Prerequisites

You have administrator rights in the portal.

You have set up a corporate LDAP directory in your system landscape that contains the user data for portal users.

If you are using Microsoft Active Directory Server as your corporate LDAP directory, portal users must all be in a single domain in the domain tree.

 

Procedure

...

      1.      Start the configuration tool by choosing System Configuration ® User Management Configuration.

If you are calling the configuration tool from the Unification Server, choose Unification Server ® <Unifier Project> ® User Management ® Security & Configuration

      2.      Choose the Directory Server tab.

      3.      Specify how the hierarchy of users and groups is defined in your corporate directory server.

¡      If you define your groups in a tree structure, set the indicator labelled Users are stored under groups in the hierarchy.

¡      If you define your groups in a flat hierarchy, set the indicator labelled Groups point to their members.

For more information about groups in a tree and flat hierarchies, see Organization of Users and Groups in Corporate Directory.

      4.      Enter data in the fields as follows:

Field Name

Field Data

User Information Type

How the user information is stored, for example in an LDAP directory or in an SAP R/3 System. At present only LDAP is possible.

LDAP Server Type

Type of LDAP directory server.

LDAP Server

Host on which the directory server is located.

Server Port

Port of the LDAP directory server.

User

Distinguished name (DN) of user that is used to connect (bind) to the LDAP directory server.

This user should have read and search permissions for the users and groups branch of the corporate LDAP directory.

Password

Password of the user specified above.

Groups Root *

If you have a flat hierarchy (Groups point to their members) enter the distinguished name of the branch of your directory where information about the groups of portal users is stored. If you are using iPlanet Directory Server (Sun ONE Directory Server), see also SAP Note 542632.
If you have a groups in a tree hierarchy (Users are stored under groups in the hierarchy) enter the distinguished name of the branch of your directory where information about portal users and groups is stored
Example: ou=CorporateGroups,c=us,o=mycompany

People Root *

Distinguished name of branch of directory where information about users is stored. (Only visible if you have a flat hierarchy, that is, you chose Groups point to their members)
Example: ou=CorporateUsers,c=us,o=mycompany

* If you are using Microsoft Active Directory Server as your corporate LDAP directory, Groups Root and/or People Root must point to a single domain in the domain tree.

      5.      If you wish to set up a secure connection to the corporate LDAP directory, check SSL Connection. For more information on setting up a secure connection, see Secure Connections to Corporate and Portal LDAP Directories.

      6.      When you have filled all the fields, choose Apply.

You need to restart the portal Web server (Microsoft Internet Information Server) and the Java servlet engine for your changes to take effect. However, do not restart these until you have completed all the tabs of the configuration tool.

 

Result

The portal knows where to look for portal user data.