While we don’t support security tokens directly, we have a few customers that use two-factor authentication where they use a combination of Laserfiche logins and security tokens (also referred to as a hardware token, authentication token, USB token, or key fob). They have it set up such that the authentication with the security token occurs at either the machine level or the operating system level. The user can then log in to Laserfiche using their preferred login method (Windows Authentication or Laserfiche username and password).

The order of operations would be something like this:

1.      Two-factor authentication with security token at machine level:User turns on their computer and has to insert a key fob into the machine to get authenticated. When Windows boots up, they log into Laserfiche using Windows authentication.

2.      Two-factor authentication with security token at operating system level: User turns on their computer, Windows boots up, and they have to use a key fob to log into Windows. They then log into Laserfiche using Windows Authentication.

In other words, the security token authentication takes place outside of Laserfiche, but the overarching goal (two-factor authentication) is still satisfied.