User State | Indicates whether the user is Active, Inactive, Locked, or Locked and Inactive. 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. A user may be made inactive because of multiple authentication failures or through resetting the state manually. Repositories of version 5.3 and later may be configured so that a user is automatically activated after being inactivated. Refer to the chapter on users in the Content Server Administration Guide for information on how to configure this. Locked The user is unable to connect to the repository. A sysadmin or superuser must set a user to this state manually and must manually take a user out of this state. Locked and inactive The user is inactive and unable to connect to the repository. A sysadmin or superuser must set a user to this state.
If the user is a superuser, only another superuser can reset the user’s state. |
Input File Path | The name of an input file. |
User Source | Specifies how to authenticate a given repository user’s user name and password. Valid values are: null LDAP The user is authenticated through an LDAP directory server. Inline Password The user must provide a password that is stored only in the repository. There is no external authentication. You must manually enter the password for each user authenticated with a password; the passwords cannot be imported in the LDIF file. UNIX only The user is authenticated using the default UNIX mechanism, dm_check_password or other external password checking program. domain only The user is authenticated against a Windows domain. UNIX first This is used for UNIX repositories where Windows domain authentication is in use. The user is authenticated first by the default UNIX mechanism; if that fails, the user is authenticated against a Windows domain. domain first This is used for UNIX repositories where Windows domain authentication is in use. The user is authenticated first against a Windows domain; if that fails, the user is authenticated by the default UNIX mechanism.
|
Description | A description for the user. |
Windows Domain | (Windows only.) The domain name associated with the new user’s Windows account. |
Home Repository | The repository where the user receives tasks and notifications. |
Default Folder | The default storage location for any object that the user creates. Depending on how you have set up your site, you may need to create a folder for the user. |
Default Group | Choose a group name from the list. When the user creates an object in the repository, it belongs to the group name associated with the user’s default permission set. |
Default permission set | A permission set to use to assign the default permissions to objects created by the new user. |
DB Name | The new user’s username in the underlying RDBMS. |
Privileges | Choose one of the following user privileges from the list: None; Group; Cabinet; Type; Group and Cabinet; Cabinet and Type; Group and Type; Group, Cabinet, and Type; Sysadmin; Superuser. |
Client Capability | Indicates what level of use is expected of the user. Choose the user type from the list: Default Consumer Contributor Coordinator System Administrator
|
Alias Set | Select a default alias set |
Overwrite or ignore information when user exists | If Overwrite is chosen and a user exists in the repository, replace existing information with imported information. If Ignore is chosen and a user exists in the repository, retain existing information. |