For normal login, and changing passwords after your account is already AuthLite Integrated, the hardware keys (yubikeys) work normally over RDP.
But two situations require special attention over RDP:
If you attempt to do one of the above procedures in an RDP session, you will receive an error that there is no key plugged in. These programs can only write to the yubikey when it is plugged in to a USB port they can see. Over an RDP session, the yubikey is not actually connected to the remote system, only its keystrokes are sent. This is good enough to use the key, but not enough to program it.
A yubikey can be programmed over RDP, but it is necessary to add software to proxy the actual USB device over the RDP session, so that the remote machine believes it is plugged in directly. Microsoft RDP/Terminal services unfortunately does not include this functionality.
We have tested and recommend the software USB Redirector RDP edition. Note that this is a different, separate product from "USB Redirector"; the "RDP" part is an important distinction, the other product won't work for this case.
Procedure to program a key over RDP:
Note that as long as the key remains "shared", tapping the OTP button will not work. This is because the remote computer sees the shared key as a keyboard that is plugged in at the console. So, its keystrokes are not directed into your RDP session, but instead to the console session! To use the freshly programmed key, you must first unshare it from the local USB Redirector client.
Questions or comments about this article? Let us know: