Version Affected: All
Overview
This article answers frequently asked questions about the HID Mini Token hardware token used with SecureAuth Identity Platform.
Frequently Asked Questions
1. What is the Mean Time Between Failures (MTBF) for tokens?
The MTBF of the HID Mini Token is 8.78 years.
2. If a battery is required to power the token, what is the battery life?
8 years.
3. Is there a requirement to have users recharge the token? Can the battery be replaced?
There is no user requirement to recharge the token. Batteries cannot be replaced.
4. What is the operating temperature range?
0°C to +55°C (32°F to 131°F), 90% relative humidity, non-condensing.
5. Are the tokens water-resistant or waterproof?
HID tokens are rated IPX67 under the International Protection (IP) Marking system.
6. Have the tokens gone through rugged testing?
HID runs periodic tests on products coming off the production line, covering the following:
- Climatic tests
- Keypad durability tests
- Drop tests
- Abrasion and friction resistance tests
- Protection against dust tests
- Vibration tests
- Compression tests
- Humidity environmental tests
- Protection against mechanical impact tests
7. What warranty is available for the tokens? What is the process for replacing tokens that fail under warranty?
Tokens carry a 1-year warranty. Devices need to be returned to the support center, and replacement devices are sent back if the token is within its warranty period.
8. Is there an expiration for an individual token? If so, how long is a token valid, and what is the process to renew or replace it after expiring?
No, HID tokens do not expire.
9. What delivery time would be expected for an order of tokens: 1,000? 10,000? 70,000?
For standard products, quantities of 1,000 or fewer are available from inventory. For quantities of 10,000, the lead time is 6 weeks; for 70,000, the typical lead time is 8 weeks. If the product is customized (logo, branding), lead time is typically 6 to 10 weeks depending on quantity.
10. What standards are supported by the tokens?
OATH HOTP (RFC 4226), OATH TOTP (RFC 6238), and OCRA (RFC 6287).
SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.
Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.
Comments
Please sign in to leave a comment.