User's Manual

Managing Security Functions
4-8 Active System Manager User Guide, Release 7.1
For example, if the Bind DN attribute is specified as uid=admin,ou=system and the Base DN attribute
is specified as ou=system, then all of the users belonging to the ‘system’ node will be picked up by the
Active System Manager repository, and will be presented to the user to import into the Active System
Manager repository.
If the Bind DN attribute is specified as uid=admin,ou=system and the Base DN attribute is specified
as ou=group1,ou=system, then all of the users belonging to the ‘group1’ node will be picked up by the
Active System Manager software and will be presented to the user to import into the Active System
Manager software. In other words, the users belonging to the ‘system’ node will not be presented to the
user.
In second example above, the users are imported into the Active System Manager repository; however,
using those user IDs, a user is unable to log into the Active System Manager application, because when a
user tries to log in, the Active System Manager software creates a context with the external security
provider by using the Bind DN attribute associated with that security store. In this case, the Bind DN
attribute (uid=admin,ou=system) is used, but before that the UID is replaced by the user ID of the user
who is trying to log in. For example, naresh attempts to log in, then the Bind DN attribute
(uid=Naresh,ou=system) is used. This fails because the user naresh does not belong to ou=system.
In conclusion, while configuring a security store in the Active System Manager repository, the OU
specified with the Bind DN attribute should be of the lowest level in the hierarchy, if the users belonging
to that level must be imported. Further, the Base DN attribute should have a hierarchical OU specification;
i.e., starting from the lower level to highest level. In the second example above, for this to work properly,
the Bind DN attribute should be specified as uid=admin,ou=group1,ou=system and the Base DN
attribute should be ou=group1,ou=system.
Adding NIS Users
Adding NIS users remotely is performed using an import wizard. It consists of importing users from remote
authentication repositories based on standards (NIS).
To add NIS users and create profiles for those users, perform the procedures in the following sub-sections:
• Importing Users from a New NIS Repository
• Importing Users from an Existing Repository
Importing Users from a New NIS Repository
To import users from a new NIS repository, perform the following steps:
1. On the Active System Manager menu bar, click Tools > Users and Groups.
The Security Management window displays with the Users tab open by default; see Figure 4-1 on
page 4-2.
2. Click Add > Remote.
The Remote Repository dialog box displays with the Lightweight Directory Access Protocol (LDAP)
repository (default) and Network Information Service (NIS) repository options.
3. Select the Network Information Service (NIS) option, select the Create a new NIS repository
option, and click Next to open the NIS Repository Definition dialog box.