COOKIES Cookies are a general mechanism that server-side programs (such as CGI scripts) can use to both store and retrieve information on the client side of the connection. This means that applications can leave information on your workstation for later use to "remember" information that may be specific to your use of the application from that workstation. Cookies are stored, retrieved and deleted by your browser responding to commands from an application like WebSite Director (WSD). Each cookie has a "persistence date" attached to it. If you turn on cookie warnings for your browser you will see this immediately following the cookie's label and value as the last item of information (for example: "This cookie will persist until Mon Jan 18 18:58:27 2038"). In addition to specific dates, there are two generic date values that can be defined when a cookie is generated. CyberTeams products use only these two generic date values, as follows: "Forever" - currently set as Jan, 2038 "Expired" - currently set to Dec, 1969. How Cookies are used for the Relogon process When a user attempts to log on to a currently running version of WSD using the Relogon function, the system uses cookies to create a temporary placeholder between the time the user requests the relogon and the successful validation of the user's username/password combination. The Relogon process works as follows: User-1 is currently logged on to WSD User-2 clicks Relogon WSD sends the following cookie to User-2: RelogonInProgress=Yes (persists until Forever) The Browser displays "Authentication Failed. Retry?" User-2 clicks [OK] The Browser displays the Username/Password dialog box User-2 types in the appropriate values and clicks [OK] WSD sends the following cookie to User-2: RelogonInProgress=<space> (persists until Expired) Note: the Expired date is currently set to Dec. 1969 The browser displays the WSD Application Desktop showing that User-2 is now logged on.