Configuring rccTSOServer on Windows for user authentication
This topic explains how to set up the Windows® environment for the TSO Client server for proper user authentication.
Before you begin
About this task
If rccTSOServer, the server component of the ClearCase® TSO Client, is to be run in a production environment, use authentication mode 2. To use authentication mode 2, rccTSOServer must be started by a user logged on as an administrator on Windows systems. Start rccTSOServer as a Windows service. Alternatively, an administrator can start the rccTSOServer in the command console, but the user must remain logged on while rccTSOServer is running. For more information about starting rccTSOServer as a Windows service, see Starting the TSO Client server as a Windows service.
To use authentication mode 0, rccTSOServer can be started by any valid ClearCase user. In this mode, rccTSOServer does not impersonate any other user in ClearCase operations. All the operations are accounted to the user who started the rccTSOServer.
The working directory for rccTSOServer should begin with a physical drive letter, such as C: or D:. The working directory cannot support a virtual drive letter such as “Network Mapping Drive" or the “virtual drive set by SUBST."
Every user who logs on to TSO Client must have write permission for the working directory.
Several configurations should be checked to ensure that impersonation of the client is effective in rccTSOServer. The steps for a domain Windows environment and a non-domain Windows environment are different. The “Local Security Policy? should be checked in a non-domain Windows environment, and the “Domain Security Policy? should be checked in the domain controller instead of the specified Windows server.