goauthentik / goauthentik/authentik
Support factory-seeded physical TOTP hardware tokens
- Dominant language
- Python
- Stars
- 25.6k
- Forks
- 2k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 644
Description
## What
import/support factory-seeded physical TOTP hardware tokens (non-programmable cards). Example: https://www.token2.com/shop/category/classic-tokens
## Want
- Import/support factory-seeded physical TOTP hardware tokens (non-programmable cards)
- Yubico OTP (#9012) is a different protocol
## Ideas this came from
- [#2251 Hardware Token support](https://github.com/goauthentik/authentik/issues/2251) — Hardware token support would be great. For example https://www.ftsafe.com/store/product/otp-c200-oath-time-based-totp-token/ Thanks, this is pretty awesome soft
- [#5584 Support for Physical TOTP Devices (Cards/Tokens)](https://github.com/goauthentik/authentik/issues/5584) — Describe your question/ I would like to use a device like i.e this one https://www.amazon.de/Feitian-OTP-Token-Card/dp/B06Y2CF4Q7/ref=sr12?mkdeDE=%C3%85M%C3%85%
- [#23547 Add support for non-programmable TOTP hardware tokens](https://github.com/goauthentik/authentik/issues/23547) — Such as: https://www.token2.com/shop/category/classic-tokens These have factory set seeds that would need to be imported in to authentik. Non-programmable token
## Out of scope
Yubico OTP (#9012) is a different protocol. Leave it open.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by reviewing the related hardware-token issues (#2251, #5584, and #23547) and the existing authentication flows, then define how factory-seeded physical TOTP tokens are imported and supported while keeping Yubico OTP out of scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100