Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Duo supports authentication using one-time password (OTP) hardware tokens such as Deepnet SafeID. There are 2 types of OTP tokens, event-based (HOTP) and time-based (TOTP), and Duo can support both event-based and timed based tokens. However, Duo does not support TOTP token drift or TOTP resync. As a result, TOTP tokens may eventually fall out of sync and generate invalid passcodes. Therefore, in long run, event-based token works better with Duo.

Deepnet SafeID provides both event-based and time-based tokens. Below is the list of SafeID tokens:

Import Hardware Tokens

Frist obtain you seed data using the instructions in the following guide (in step 4 select "Duo CSV");

...

7 - Click Import Hardware Tokens button 

Assigning Hardware Tokens

Once tokens have been uploaded the will need to be assigned to users using the following instructions;

Expand
titleHow to assign hardware tokens to end users in Duo

Include Page
Assign a hardware token to an end user in Duo
Assign a hardware token to an end user in Duo

Synchronising HOTP Hardware Tokens

If you are using SafeID/Eco event based tokens (HOTP), then if you find that the OTP codes generated by the token are rejected by Duo during authentication, you may find that you need to synchronise the tokens using the following procedure;

...

Please note that only event based HOTP tokens (SafeID/Eco)  can be synchronised with Duo as Duo currently doesn't support synchronising TOTP tokens.

Deleting Hardware Tokens

Tokens that have been previously imported into Duo can be removed using the following procedure;

Expand
titleHow to delete hardware tokens in Duo

Include Page
Delete Tokens in Duo
Delete Tokens in Duo

...