Howto use the eToken to log in to a Windows Terminal Server
- date: 23.01.2007
- updated: 16.04.2008
author: CorneliusKoelbel
<cornelius.koelbel AT lsexperts DOT de>
- used eToken hardware: eTokenNG OTP
- used eToken RTE version: 4.55
Coming with the new source code of http://www.rdesktop.org/ rdesktop now supports smartcards. Thus you can also use your eToken to login from a linux client to a Windows Terminal Server.
assumptions
We assume, you or your company set up the Windows Terminal Server this way, that smartcard logon is possible that you enrolled the user certificates (certificate template smartcard logon) to your eToken.
i.e. Smartcard logon to the Terminal Server works fine from the Windows XP box of your collegue 
getting it
So go and get the latest sources of rdesktop via cvs and configure and compile it at least with the flag
configure --enable-smartcard
Roughly -- that is all.
either or
In fact you now can choose, if you want to use opensc or the Aladdin middleware for accessing the eToken.
For eTokens supported by opensc/openct, you can just use openct and pcsc-lite.
If you got some newer eRokens, that are not supported by opensc yet, you will use the eToken middleware as described in the HowTos/eToken_on_Linux.
start it
Now you should be able to connect to your terminal server by starting
rdesktop -r scard my.terminal.server
you will be prompted for the PIN of your eToken.
It is also possible to connect to a second terminal server from within the first one.
Hardware
The eTokenPro 16K does not work very well.
An eTokenNG OTP with CardOS 4.20 works very fine and fast.
missing
when having connected to your terminal server your eTokenPro USB will be identified as eToken Smartcard.
required downloads
The rdesktop sources newer than 1.5.0: