Importing users

You can create repository users from information contained in an input file. Before you begin importing users, determine the following:

Authentication type
If the server authenticates users against the operating system, each user must have an account on the server host. If the server uses an LDAP directory server for user authentication, the users do not need to have operating system accounts.
Groups and ACLs
If you specify the attributes user_group (the user’s default group) and acl_name (the user’s default permission set), any groups and permission sets must already exist before you import the users.
Passwords
If you are creating a user who is authenticated using a password stored in the repository, the password cannot be assigned in the input file. You must assign the password manually by modifying the user account after the user has been imported..

To import new users:

On the file system of the host where your browser is running, create a text file in LDIF format.
Save the text file.
Connect to the repository where you want to create new users.
Navigate to Administration > User Management > Users.
Select File > Import Users.
The Import User page displays.
Enter the user information, as described in Table 4.4.
Click Finish.

Table 4.4. Import user properties

Field label	Value
State	Indicates the user’s state in the repository. Select one of the following: Active: The user is a currently active repository user. Active users are able to connect to the repository. Inactive: The user is not currently active in the repository. Inactive users are unable to connect to the repository. If the user is a superuser, only another superuser can reset the state.
Source	The name of an input file. Click Browse to browse to the location of the LDIF file containing information for creating the new users. For more information about the LDIF file format, refer to Import file format.
User Source	Specifies how to authenticate a given repository user’s user name and password. Valid values are: None: Windows only. This means the user is authenticated in a Windows domain. UNIX only: The user is authenticated using the default UNIX mechanism, dm_check_password or other external password checking program. This option only displays on UNIX hosts. Domain only: The user is authenticated against a Windows domain. This option only displays on UNIX hosts. UNIX first: This is used for UNIX repositories where Windows domain authentication is in use. This option only displays on UNIX hosts. The user is authenticated first by the default UNIX mechanism. If the authentication fails, the user is authenticated against a Windows domain. Domain first: This is used for UNIX repositories where Windows domain authentication is in use. This option only displays on UNIX hosts. The user is authenticated first against a Windows domain; if that fails, the user is authenticated by the default UNIX mechanism. LDAP: The user is authenticated through an LDAP directory server.
Description	A description of the user account.
E-Mail Address	The E-mail address of the user. This is the E-Mail address to which notifications are sent for workflow tasks and registered events.
Windows Domain	(Windows only.) The domain name associated with the new user’s Windows account.
Home Repository	The repository where the user receives notifications and tasks.
User is global	If the user is created in the governing repository of a federation, select this option to propagate the user account to all members of the federation.
Default Folder	The default storage place for any object the user creates. Click Select to assign a folder.
Default Group	The group that is associated with the default permission set of the user. Click Select to specify a default group. When the user creates an object in the repository, it automatically belongs to this group.
Default ACL	The permission set that assigns the default permissions to objects the user creates. Click Select to specify a default permission set.
Db Name	The user name of the user in the underlying RDBMS. The DB Name is only required if the user is a repository owner or a user who registers RDBMS tables.
Privileges	The privileges that are assigned to the user. User privileges authorize certain users to perform activities in the repository. Select one of the privileges from the drop-down list, as follows: None Create Type Create Cabinet Create Cabinet and Type Create Group Create Group and Type Create Group and Cabinet Create Group, Cabinet, and Type System Administrator Superuser: If you grant superuser privileges to a user, add that user manually to the group called admingroup. If you revoke a user’s superuser privileges, remove the user from the admingroup.
Client Capability	Indicates what expertise level of the user. This option is for informative purposes only and is not associated with any privileges. Content Server does not recognize or enforce these settings. Choose a user type from the list: Consumer Contributor Coordinator System Administrator
Alias Set	The default alias set for the user. Click Select to specify an alias set.
If user exists, then overwrite user information	Select this option if a user already exists in the repository and you want to replace existing information with the imported information.
If user exists, then ignore information	Select this option if a user already exists in the repository and you want to retain the existing information.