Integrating Microsoft Terminal Server and Citrix

SecureLogin can simplify authentication to numerous configurations of MicrosoftTerminal Server and Citrix MetaFrame*. Integration of SecureLogin Terminal Server and Citrix consists of the following components. Not all may be required, depending on your implementation.

• Client login extension (slina.dll) applied to a workstation with the Novell^® Client^TM (without the Novell NMAS^TM client), which provides a link between the following:
  • The Novell GINA (graphical identification and authentication) or the Windows 9x login panel
  • The GINA running on the terminal server

• NMAS client integration library (slnmas.dll) applied to a workstation with the Novell Client and Novell NMAS client, provides a link between the client login and the GINA running on the terminal server

  NOTE:  Client slina.dll and slnmas.dll also provide support for offline authentication to SecureLogin by using your NDS or eDirectory username and password.

• GINA stub (sl_tscgina.dll) applied to a workstation without the Novell Client, which provides a link between the Microsoft GINA and the GINA running on the terminal server
• Server login extension (slina.dll) applied to a terminal server with the Novell Client, which provides the server-side link to the client GINA
• Server GINA replacement (sl_tsgina.dll) applied to a terminal server without the Novell client, which provides the server-side link to the client GINA stub
• SecureLogin Virtual Channel Driver (vdslsson.dll or tsslsso.dll), which provides the conduit for secure communications between the client and server extensions
• Published Application integration (ProLauncher.exe) applied to a Citrix server, which provides proper initialization and termination of the SecureLogin components (combroker.exe and proto.exe) running on the server

The following diagram illustrates the SecureLogin architecture: