Managing user accounts

If you have the appropriate access rights, you can add users to a server configuration from either the Server Administration Tool or a client. Initially, you add a user to a specific group, such as Developers or Testers. The user becomes an explicit member of this group and an implicit member of any of this group’s parent groups, such as the All Users group. This operation can be performed only when the server is running.

Caution: Creating a user account with the name StarTeam has been known to cause problems when using the command line stcmd server-mode command to lock or unlock the server configuration. The command requests a password even when the user has a blank password or when a password has already been provided.

Note: If you are using the Server Administration tool installed with the client, you can only administer remote servers.

Adding a user

Open the Server Administration tool and select the server configuration.
Click the Accounts bar and then click (User Manager). The User Manager tab opens.
Select a group from the Groups tree and click New User. The New User Properties dialog appears.
Type the user’s name in the Full Name field and optionally type the user’s e-mail address in the E-Mail field.
Optionally, type the user's phone number, voice mail number, pager number, fax phone number, and street address in the appropriate fields.
Click the Logon tab.
1. Type the name to be used to log onto the application in the User Name field. If you enter a user name that already exists, the following message displays after you click OK: A user with a given user name already exists.
2. Select the Validate through StarTeam Server button if you want to validate the user against the server. Type a StarTeam password for the user in the Password field and again in the Confirm field. Asterisks appear in the text box instead of the password itself. If the password’s minimum length can be zero, you do not have to enter a password. If you are using strong passwords, be sure to follow the rules for those passwords.
3. (For Microsoft Active Directory or OpenLDAP) To validate the user against your organization’s directory server, select the Validate through directory service button and type the Distinguished Name for the user. An alphanumeric value of up to 254 characters, this value is used to uniquely identify the directory services user. To use directory service validation, the Server must be on a trusted domain in relation to the LDAP server. If a secondary directory service was configured, select Primary or Secondary from the drop down.
Optionally, select the Access Policy tab and specify when this user can access the server configuration. Select one of the following option buttons:
- Access not restricted (the user can access the server configuration at any time)
- Standard five day work week (the user can access the server configuration Monday through Friday from 8 A.M. to 5 P.M.)
- Custom access hours (to set one or two time periods per day when the user can or cannot access the server configuration)
- Select a day of the week from the Day list.
- Select the No Access on That Day check box to deny access, or clear it to allow access on that day.
- Use the From and To boxes to set one or two time periods when access is either allowed or denied.
If the user’s workstation is not in the same time zone as the computer on which the server configuration is running, select the Adjust for Workstation Time Zone check box, and type the number of hours from Greenwich Mean Time (GMT) in the hours from GMT field.
Add the new user explicitly to other groups, as appropriate. Remember that a user is implicitly already a member of the current group’s parent groups, but you must explicitly add a user to groups that are not parents of the current group.

Reviewing a user’s explicit group memberships

Open the Server Administration tool and select the server configuration.
Click the Accounts bar and then click (User Manager).
The User Manager tab opens.
Select the user from the User list.
If the user does not appear in the Users list, you can display a list of all users by:
1. Selecting the All Users group in the Groups tree.
2. Selecting the Show Users in All Descendant Groups check box.
Right-click and select Properties. The User Properties dialog box appears.
Select the Membership tab. The list displays the groups in which this user has explicit membership.

Changing group memberships

Open the Server Administration tool and select the server configuration.
Click the Accounts bar and then click (User Manager).
The User Manager tab opens.
Select the user from the User list.
If the user does not appear in the Users list, you can display a list of all users by:
1. Selecting the All Users group in the Groups tree.
2. Selecting the Show Users in All Descendant Groups check box.
Right-click and select Group Membership. The Group Membership dialog box appears.
Select the groups to which you want to add this user explicitly.
Click OK.

Removing users from groups

Open the Server Administration tool and select the server configuration.
Click the Accounts bar and then click (User Manager).
The User Manager tab opens.
Select the user from the User list. If the user does not appear in the Users list, you can display a list of all users by:
1. Selecting the All Users group in the Groups tree.
2. Selecting the Show Users in All Descendant Groups check box.
Right-click the user’s name, and select Group Membership. The Group Membership dialog box opens.
Deselect the option next to the group from which you want to remove the user.
Click OK.

Removing user accounts

Open the Server Administration tool and select the server configuration.
Click the Accounts bar and then click (User Manager). The User Manager tab opens.
Select the user from the User list. If the user does not appear in the Users list, you can display a list of all users by:
1. Selecting the All Users group in the Groups tree.
2. Selecting the Show Users in All Descendant Groups check box.
Right-click the user’s name and select Delete Account. The system displays the following message:
```
Do you want to delete username’s user account?
```
Click Yes. This action permanently removes the user from the server configuration.

Checking user account status

Open the Server Administration tool and select the server configuration.
Click the Accounts bar and then click (User Manager). The User Manager tab opens.
Select the All Users group in the Groups tree.
Select the Show Users in All Descendant Groups check box.
Review the information about the specific user that displays in the Users list.
Tip: To ensure that the information in the Users list box is current, click Refresh.

Suspending user accounts

To suspend a user's account:

Open the Server Administration tool and select the server configuration.
Click the Accounts bar and then click (User Manager). The User Manager tab opens.
Select the user from the User list.
If the user does not appear in the Users list, you can display a list of all users by:
1. Selecting the All Users group in the Groups tree.
2. Selecting the Show Users in All Descendant Groups check box.
Right-click the user’s name and select Suspend Account. The account status in the Users list changes to Suspended, and access to the server is denied after the user logs out.

Reactivating user accounts

Open the Server Administration tool and select the server configuration.
Click the Accounts bar and then click (User Manager). The User Manager tab opens.
Select the user from the User list.
Right-click the user’s name and select Reactivate Account. The user account is reactivated.

Reactivating administrative accounts

It is possible for any user, even users with an administrative account, to be locked out of a server configuration when the number of retries with the wrong password has been exceeded. The lockout period for the main administrative account (Administrator) is 24 hours. However, you can unlock the administrative account before the 24 hours have elapsed by using the following procedure:

Shut down the server configuration and disconnect its network connection to keep remote users off.
Start the server configuration using the command line in foreground mode from the StarTeam Server installation folder.
```
starteamserver -start StarClient -fg
```
The configuration name specification is case-sensitive with the command line. The command prompt must be left open until the server configuration is shut down.
Note: In the above example, StarClient is the name of the server configuration.
Set the system clock one day ahead.
Log in as Administrator and log off. This action will reactivate the Administrator account.
Set the clock back one day to its original time.
Shut down the server configuration by entering “X” and clicking Type, which is how the server is shutdown in foreground mode.

Forcing users to log off

You may have to force a user to log off for any number of reasons, including code violations or disaster recovery. When you force a user to log off, the user’s next operation displays the following error message: You are no longer logged on.

Depending on the reason for your action, you may need an additional method, such as e-mail or the telephone, to notify users to stop accessing the application.

To log on again, the user must exit the application and restart the client. Most integrations between StarTeam and another application require the user to restart the application being used. However, these users are not usually notified that their connections to the server have been terminated. This operation can be performed only when the server is running.

Open the Server Administration tool and select the server configuration.
Click the Accounts bar and then click (User Manager).
The User Manager tab opens.
Select the user. If the user you want to work with does not appear in the Users list, you can display a list of all users by doing the following:
1. From the Groups tree, select the All Users group.
2. Select the Show Users in All Descendant Groups check box.
Right-click the user’s name and select Force Logoff from the context menu. The user is immediately denied access to the server configuration and to all projects residing in this server configuration.
Note: You cannot force your own logoff.