|Model Number||OTPC-P2-i Nonbranded|
restricted tyme sync
|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|
Not listed here
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-P2-i programmable card with restricted time sync - nonbranded
The seeds can be set and reset an unlimited number of times using Token2 NFC burner Android, iPhone and Windows applications.
Form-factor: standard credit card - nonbranded
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: 5 gr
Expected lifetime: 4-5 years
Time sync: Yes [restricted: setting time will clear the seed]
Maximal seed length : 63 bytes (126 hex / 101 base32)
Hash type: sha-1 or sha-256 [configurable]
iOS Mail or Outlook App for Office 365 Users with Passwordless Authentication
As more and more organizations adopt a passwordless method of authentication, users are faced with the challenge of configuring their email accounts on their mobile devices.
Unlocking the Benefits of Azure Passwordless with FIDO2 Keys
We understand that some of our customers have questions and concerns about migrating to Azure Passwordless with FIDO2 keys. With this blog post, we aim to address and clarify some of the common queries that may arise regarding the technology.
Top myths about FIDO2 security keys and Passwordless access
We have been getting quite a lot of questions about the security level of FIDO keys, in the light of some recent news and research papers covering potential vulnerabilities of both the protocol stack itself and the hardware of certain implementations.