Probably the most common problem you may face working with USB security tokens is the inability to forward them to a virtual environment. By default, most virtual machines do not provide access to the functionality and contents of devices attached to the host machine. So, you’ll need to find a way to duplicate your device to share it between your guests and host OSes.
Certain difficulties may also appear if you try to provide access USB token remotely for multiple users over the network. If there’s token based authentication in your company and you need to share, let’s say, a bank token among several team members, you’re most likely to need a dedicated third-party tool to help you copy the device to remote computers.
Here are several methods to share USB security tokens using a software solution:
FlexiHub is another software with features similar to those of Donglify. You can use it as remote access token software, but the tool does not offer the ability to establish multiple connections with the same device.
Follow these easy steps to use FlexiHub:
USB Network Gate enables you to access a security token with one remote machine at a time. A nice feature of the software is the ability to see which machine is currently connected to a USB device. This can be very useful if you have forgotten to disconnect the dongle from another computer.
Here’s how to easily access a remote USB token using USB Network Gate:
The main functionality of all security tokens is basically the same. Every token provides some kind of authentication code that allows users to access a particular service like an online bank account, etc. However, security keys may differ in the means they use for generating those authentication codes.
Static password tokens
The simplest type of security tokens is static password tokens which store the secret code inside the device and release it any time the user asks for it. It seems clear that you won’t get a high level of security with the keys of this sort.
As their name indicates, time-synchronized tokens generate a password based on the time. The timer they contain is synchronized with another timer, working on the authentication server-side. This allows changing passwords generated by the tokens at a set time interval, for example, every 3 minutes.
The mission of asynchronous tokens is to generate passwords that are unpredictable to guess, even if all the previously generated passwords are known. Those passwords change every time they are generated.