Buy options
€21.00Model Number | OTPC-P1-i |
---|---|
Form-factor | credit card |
Functions | TOTP configurable |
Dimensions | 85 × 54 × 1 mm |
Weight | 5 gr |
Programmable |
1 profile unrestricted time sync |
Product ID | T2-56 |
Wordpress | fully compatible | |
---|---|---|
Google Account | fully compatible | |
Azure On-Prem MFA Server | fully compatible | |
Azure Cloud MFA / Office 365 AD Premium P1 or P2 | fully compatible | |
Azure Cloud MFA / Office 365 AD Free/Basic | fully compatible | |
Stripe Dashboard | fully compatible | |
Meraki Dashboard | fully compatible | |
ISDecisions UserLock | fully compatible | |
ESET Secure Authentication | fully compatible | |
Watchguard AuthPoint | fully compatible | |
Duo | fully compatible | |
WebUntis | fully compatible | |
Not listed here |
Write us |
|
If the system you are using is not included in the compatibility list, it does not necessarily indicate incompatibility. We encourage you to refer to our integration guides page or get in touch with us for more information. |
Please check product and platform compatibility before placing an order
All pictures shown are for illustration purpose only. Actual product may slightly vary due to product enhancement or other reasons.
Token2 OTPC-P1-i programmable card with unrestricted time sync , TOTP hardware token
please note that OTPC-P1-i replaces the retired OTPC-P1 model
NFC programmable hardware token in a credit card format than can be programmed using our burner apps available for Android, iPhone or Windows
This model is with unrestricted time sync (i.e. the time can be adjusted without reprovisioning the seed)
Specifications
Form-factor: credit card size
Algorithm: TOTP
Time offset: 30 seconds or 60 seconds [configurable]
Number of digits: 6
Hash algorithm: sha1 (default) or sha256 (set using NFC burner)
Screen type: e-Ink
Screen size: 24 × 7 mm
Dimensions: 85.60 × 53.98 × 0.9 mm
Weight: 4 gr
Expected lifetime: 4-5 years
Programmable: Yes
Time sync: Yes
Maximal seed length : 63 bytes (126 hex / 101 base32)
Hash type: sha-1 or sha-256 [configurable]
Blog
04-09-2024
Update on EUCLEAK Vulnerability and Chip Security
We want to assure you that we do not use Infineon chips, which are affected by the EUCLEAK side-channel attack recently identified by NinjaLabs. This attack exploits a vulnerability related to the extended Euclidean algorithm (EEA) used in modular inversion.
24-05-2024
Reminder: Our management tools for FIDO2.1 Security Keys are Open Source!
Just a quick reminder: our FIDO2.1 Manager tool, your go-to solution for managing FIDO2 credentials securely, is fully open source! Both the Windows version, created with PowerShell, and a Linux (C++ and Python) version are available.
01-05-2024
FIDO2 Security Keys. To PIN or not to PIN?
Whether to require a PIN when using a FIDO2 security key depends on various factors, including the service provider's authentication settings. This results in situations where some services always prompt for a PIN, while others never do - so we have decided to clarify these aspects.