Repository navigation
Replies: 1 comment
|
There's already a feature request covering hardware tokens: #25256 You're welcome to create a feature request for the second half. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Use Case
In our company, we rely on physical (hardware) programmable OTP tokens for multi-factor authentication. We are currently in the process of migrating from FreeIPA to Authentik.
In FreeIPA, administrators centrally manage and assign hardware tokens to users, while users themselves cannot add, edit, or remove tokens. Currently, the lack of dedicated admin workflows for hardware tokens and the inability to restrict user self-service for OTP tokens in Authentik is blocking our full migration.
Feature Description
We would like Authentik to support the following capabilities:
Admin-Led Hardware OTP Token Enrollment & Assignment:
Allow administrators to import or manually add physical (hardware) TOTP/HOTP tokens (e.g., via secret keys, serial numbers, qr code).
Allow administrators to assign (and unassign) these physical tokens directly to specific user accounts.
Restrictive Self-Service Permissions / Policies:
Provide granular permissions or stage configurations to block standard users from adding new OTP authenticators or editing/deleting existing OTP tokens assigned to them.
Users should only be able to use their assigned hardware token for MFA challenge prompts without being able to alter their OTP settings in the user portal.
Tokens which we are using are:
https://www.token2.com/products/token2-c301-i-programmable-hardware-token-iphone-compatible
All reactions