Swivel OATH HOTP Hardware Token

From Swivel Knowledgebase
Revision as of 11:25, 5 December 2014 by Gfield (talk)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Overview

Swivel provide tokens for authentication, below are the details of the Swivel OATH compliant HOTP token, see also Swivel OATH TOTP Hardware Token. Each time the button is pressed a number is displayed for use as a One Time Code in authenticating a user. For provisioning tokens see Token. A Swivel hardware token consists of the following:

  • Serial Number to identify the hardware token
  • Seed associated with the serial number, the seed is used to generate the OTC. The seed is sent separately from the token
  • One Time Code, generated on the hardware token when the button is pressed.


Swivel OATH HOTP hardware token.jpg


Technical Specification

Swivel Hardware Token Specification
Platform Specification
User Interface Up to 8-characters high contrast LCD display, Built-in button, OTP displayed for 10 seconds S 3 and later. Approx. size: 0.5Mb
Security Algorithms OATH compliant event-based HOTP
Memory Type Random Access Memory (RAM)
Endurance More than 14,000 clicks
Battery Lifecycle 4 years
Power Consumption Less than 0.005mW
Operating Temperature (-4°F ~ 158°F) (-15.6 degC ~ 70 degC)
Humidity 0% ~ 100% without condensation
Security Tamper evident, IP54 ingress
Warranty 4 Years


Customization

Please contact Swivel for a quote if customization or other features/functionality is required.


Determining between a Swivel HOTP and a TOTP token

The Swivel OATH HOTP Hardware Token is similar to the Swivel OATH TOTP Hardware Token but there are some differences to tell them apart:

  • When the button is pressed the HOTP token displays an OTC for about 12 seconds, the TOTP token 60 seconds.
  • The HOTP token OTC can be used consecutively regardless of time, the TOTP token OTC has to be used within a very short time period.
  • The Administrator can check the Serial Number against the list of purchased tokens.


Testing

Known Issues

Troubleshooting

If the Token seed will not import see Token

If the token will not sync ensure that HOTP has been selected at time of import. If it has been imported incorrectly, remove the token and reimport.

For further issues and token returns contact support@swivelsecure.com