The Microsoft Windows Remte Desktop client supports the use of smartcards (eToken). A typical use case is when a user connects from home (local Windows desktop) to their office computer (remote Windows desktop). The Windows RDP client ‘forwards’ the local eToken connection to the remote machine so that applications on the remote machine that require eToken authentication can be used.
- Possession of eToken with UTORauth-issued certificate and a current version of the SafeNet client installed on local and remote Windows hosts.
- These instructions apply to the Windows RDC client only. Note that other vendor versions of the Remote Desktop client, which may be used on a MacOSX or Linux desktop, may or may not handle the smartcard redirection. We currently have not tested such a client but there are a few available.
- By default, smart card redirection is enabled, so there’s no action required.
- Plug in the eToken on the local desktop
- Start the Remote Desktop Client
- Use remote applications as usual
- To test the availability of the X.509 certificate on the eToken to the remote end, open Internet Explorer and navigate as follows: Internet Options -> Content tab -> Certificates button -> Personal tab. You should see your UTORauth certificate there. If not, close the RDC connection, re-plug the eToken, making sure the eToken LED is active, and restart the RDC.