Manage hardware tokens

OATH hardware tokens are physical devices that generate passcodes for users to authenticate with Akamai MFA. After you acquire new tokens, add them to Akamai MFA by uploading a CSV file. You can then assign each token to a user.

Akamai MFA supports the following types of OATH hardware tokens:

  • Time-based One-Time Password (TOTP) tokens generate a new passcode at a fixed interval, such as every 30 or 60 seconds. Supported TOTP tokens comply with RFC 6238.
  • HMAC-based One-Time Password (HOTP) tokens generate a new passcode on demand, such as when the user presses the token's button. Supported HOTP tokens comply with RFC 4226.

Both types use Hash-based Message Authentication Code (HMAC) algorithms to compute each passcode from a secret key, using SHA-1, SHA-256, or SHA-512 cryptographic hash functions.

📘

For secure authentication, use hardware tokens with secret keys that are at least 128 bits (equivalent to 32 hexadecimal, 26 Base32, or 24 Base64 characters). While Akamai MFA supports shorter secret keys for backward compatibility with older tokens, they're less secure.

Add hardware tokens

Complete these steps to add hardware tokens.

Before you begin

Check the token's spec sheet for its OATH type, HMAC algorithm (for example, SHA-1), code length, and time step or initial counter. The settings that you choose apply to every token in the file, so add different types of tokens in separate files.

How to

  1. In the Enterprise Center navigation menu, select Multi-factor Authentication > Devices.

  2. Click Add hardware tokens in the page header.

  3. On the add hardware tokens page, in the Configuration & Upload section, select a value for each setting. No setting has a default. Upload is available only after you complete all fields.

    SettingOptions
    OATH typeTOTP (time-based) or HOTP (counter-based).
    HMAC algorithmSHA-1, SHA-256, or SHA-512.
    Code length6, 8, or Other (6 to 9 digits).
    Time step (TOTP only)30, 60, or Other (1 to 300 seconds).
    Initial counter (HOTP only)0 or Other (0 to 1,000,000). New tokens usually start at 0.
  4. Create a CSV file of 1 MB or less. The first row must be the header, followed by one row for each token:

    • TOTP: SerialNumber,SecretKey
    • HOTP: SerialNumber,SecretKey,Counter. Counter is optional and accepts 0 to 1,000,000. It overrides Initial counter for that token. If the cell is empty, the token uses Initial counter.

    SerialNumber uniquely identifies each token. SecretKey is the token's secret in hex, Base32, or Base64 format. Token vendors usually provide secrets in hex.

    TOTP example:

    SerialNumber,SecretKey
    1234567890,3132333435363738393031323334353637383930
    1234567891,4142434445464748494a4b4c4d4e4f5051525354

    HOTP example:

    SerialNumber,SecretKey,Counter
    1234567890,3132333435363738393031323334353637383930,
    1234567891,4142434445464748494a4b4c4d4e4f5051525354,25
  5. In CSV file, select your CSV file or drag it onto the upload bar. To clear the selected file, click X.

  6. Click Upload.

🚧

Review your token settings carefully. If any setting doesn't match the tokens in your file, passcodes from those tokens will fail. The upload process can't detect misconfiguration and the settings can't be edited later. To recover misconfigured tokens, unassign and delete them, then upload them again with the correct configuration.

Upload results

Depending on the upload results, note the following behavior:

  • All tokens were added. A message confirms that N hardware tokens were added, and the Devices page opens.

  • Some or no tokens were added. A message shows how many tokens were added, and a dialog lists the serial numbers that weren't added:

    • Already added to this account. Indicates that tokens already exist in your Akamai MFA service.
    • Listed more than once in the file. Indicates duplicate rows in your file.

    Click Download CSV to save a list of every serial number with its status: successful, existing, or duplicate. Click Add More to return to the page with your settings and file kept, or Done to go to the Devices page.

  • The file was rejected. If the file isn't a .csv file, is larger than 1 MB, has an incorrect header, or has an invalid Counter value, an error message explains the issue. The page remains open and preserves your settings, so you can fix the file and upload it again.


Did this page help you?