User properties

The following table describes each field that must be completed to create a new user. For more information on users, see the Content Server Administrator’s Guide.

Table 23.1. Properties of a user

Field label	Value
User State	Indicates the user’s state in the repository: 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. Locked The user is unable to connect to the repository. A sysadmin or superuser must set a user to 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.
Name	The user name for the new user. If you are modifying the properties of a user, you cannot change the user name. Instead, you must reassign the user’s objects to another user. User the instructions in Reassigning objects to another user.
User Login Name	The login name used for authenticating a user in 5.3 and later repositories. If the user is an operating system user, the user login name must match the user’s operating system name. If the user is an LDAP user, the user login name must match the LDAP authentication name. If a repository was upgraded to 5.3 from an earlier version, this field is populated during the upgrade with the value of the user OS name property.
User Login Domain	Identifies the domain in which the user is authenticated. This is typically a Windows domain or the name of the LDAP server used for authentication.
User Authentication Source	Specifies how to authenticate a given repository user’s user name and password. Valid values depend on whether the repository runs on UNIX or Windows. On UNIX, the valid values are: null LDAP The user is authenticated through an LDAP directory server. Password The user is authenticated based on a password stored in the repository. Choose Password for repository users who are not authenticated on an LDAP server or Windows domain. 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. On Windows, the valid values are: null LDAP The user is authenticated through an LDAP directory server. Password The user is authenticated based on a password stored in the repository. Choose Password for repository users who are not authenticated on an LDAP server or Windows domain.
Password	If Password is selected as the User Authentication Source, this field is displayed. Type the user’s password, which is then encrypted and stored in the repository.
Description	A description of the user.
Email Address	The user’s email address for receiving notifications from the repository.
User OS Name	The new user’s operating system user name. Required in 5.2.5 repositories. Not required in 5.3 and later repositories.
Windows Domain	On Windows, the domain name associated with the new user’s Windows account. On UNIX, the domain on which the user is authenticated if Windows domain authentication is in use.
Home Repository	The repository where the user receives notifications and tasks.
Default Folder	The default storage place for any object the user creates. Normally, this is a cabinet where the user’s name is the object name. Select Choose existing folder to assign a folder you already created as the user’s default folder. Select Choose/Create folder with the user name to automatically create a folder with the user’s name as the object name.
Accessible Folders	Use this field optionally to restrict the user’s repository access: If any folders are selected, the user has access only to those folders and objects in the selected folders. The user automatically has access to his or her default folder. If no folders are selected, the user has access to the entire repository, subject to the permissions set on folders and objects in the repository.
Default Group	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 used to assign the default permissions to objects created by the user.
DB Name	The new user’s username in the underlying RDBMS. The DB Name is required only if the user will be a repository owner or a user who registers RDBMS tables.
Privileges	Choose a user privilege from the list. User privileges authorize certain users to perform activities that are required to administer and maintain the system. The privilege levels are: 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.
Extended Privileges	Sets the level of extended privileges for auditing. Superusers and sysadmins cannot modify their own extended privileges. None The user cannot configure auditing, view audit trails, or purge audit trails. Config audit The user can configure auditing. Purge audit The user can purge existing audit trails. Config and Purge Audit The user can configure auditing and purge existing audit trails. View Audit The user can view audit trails. Config and View Audit The user can configure auditing and view existing audit trails. View and Purge Audit The user can view existing audit trails and purge them. Config, View, and Purge Audit The user can configure auditing and view and purge existing audit trails.
Client Capability	Indicates what level of use is expected of the user. Choose the user type from the list. There are four types of users: Consumer Contributor Coordinator System Administrator Content Server does not recognize or enforce these settings.
Alias Set	The default alias set for the user.
Workflow Disabled	Indicates whether a user can receive workflow tasks.
Propagate changes to members	Displays only when editing a global user. When checked, changes to the member are propagated to members of a repository federation.
Turn off authentication failure checking	If checked, user may exceed the number of failed logins specified in the Maximum Authentication Attempts field of the repository config object.