You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users can have multiple TOTP Authenticators registered with FusionAuth. If they lose one or change devices, they will want to remove that authenticator from their account. Currently it's impossible to tell which of your authenticators is which device.
Solution
Users will be able to add a custom name/identifier to their Authenticator, to differentiate between apps/hardware keys etc.
Using a self-hosted flow, users could add this field and we would store it in a database alongside the id and join in the front end (although this is not currently returned when a 2FA method is added), so adds additional complexity. This would also require complete ownership of the login flow, to capture changes when 2FA is enforced and set on login, which is a significant undertaking.
Additional context
Add any other context or screenshots about the feature request here.
Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.
The text was updated successfully, but these errors were encountered:
Custom names for TOTP Authenticators
Problem
Users can have multiple TOTP Authenticators registered with FusionAuth. If they lose one or change devices, they will want to remove that authenticator from their account. Currently it's impossible to tell which of your authenticators is which device.
Solution
Users will be able to add a custom name/identifier to their Authenticator, to differentiate between apps/hardware keys etc.
Related Issues
Alternatives/workarounds
Using a self-hosted flow, users could add this field and we would store it in a database alongside the id and join in the front end (although this is not currently returned when a 2FA method is added), so adds additional complexity. This would also require complete ownership of the login flow, to capture changes when 2FA is enforced and set on login, which is a significant undertaking.
Additional context
Add any other context or screenshots about the feature request here.
Community guidelines
All issues filed in this repository must abide by the FusionAuth community guidelines.
How to vote
Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.
The text was updated successfully, but these errors were encountered: