Home > Solutions > SafeSign IC Partner Solutions > for Terminal Services

SafeSign Identity Client for Microsoft Windows Terminal Services

Strong authentication with cryptographic smart cards and USB tokens

Terminal Services is a multi-session environment that gives remote computers access to a server desktop through "thin client" software. In Terminal Server mode, you can access Windows-based applications or the Windows desktop itself on virtually any computing device - including those that cannot run Windows.

When a user runs an application on Terminal Server, all of the application execution takes place on the server, and only keyboard, mouse, and display information traverses the network. Users see only their own individual sessions, which are managed transparently by the server operating system, and remain independent of any other client session. Through terminal emulation, Terminal Services allows the same set of applications to run on diverse types of desktop hardware.

An improved feature of Terminal Services in Windows 2003 Server is that it is possible to log on to the Windows environment using smart card logon, as was not possible with previous versions of the Microsoft Terminal Server (Windows 2000 Server). A smart card that contains Windows logon credentials can provide those credentials to a Windows Server 2003 remote session for log-on. Note that this feature requires a client OS that can recognize the smart card first: Windows 2000, Windows XP, Windows 2003, Windows Vista, Windows 7 and Windows CE .NET.

SafeSign Identity Client for Windows 2003 Terminal Services

For smart card logon with Terminal Services in Windows 2003 Server to work, the following prerequisites are to be fulfilled:
  • Active Directory installed and configured;
  • Microsoft Certification Authority installed and configured;
  • SafeSign Identity Client software installed on the Windows  (Terminal) Server;
  • Drivers for the smart card reader(s) installed on the Windows  (Terminal) Server and on the client;
  • A smart card reader installed on the client (if a smart card is used);
  • A token (smart card or USB token) that is supported by SafeSign Identity Client, personalized which a Digital ID which supports smart card logon for use on the client;
  • Windows 2000, Windows XP, Windows Server 2003, Windows Vista or Windows 7 used as a client to connect to the Windows (Terminal) Server.
Once these requirements are met, users can start up a Terminal Server Connection and authenticate themselves by means of a token. Example: a user with a PC with Windows XP installed can set up a remote connection by inserting his token and entering the PIN. But it may even go further than that: the user can first use his token to logon to the domain (his Windows XP client is part of) and then set up a terminal connection for those applications and services that run on the server with the same token. And even when connected to the Terminal Server, SafeSign Identity Client can be used on the terminal itself: for example, the user can go to a secure web page and authenticate himself with his token and PIN.