Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom names for TOTP Authenticators #2739

Open
jamescottrill opened this issue May 8, 2024 · 2 comments
Open

Custom names for TOTP Authenticators #2739

jamescottrill opened this issue May 8, 2024 · 2 comments

Comments

@jamescottrill
Copy link

jamescottrill commented May 8, 2024

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.

@mooreds
Copy link
Collaborator

mooreds commented May 8, 2024

@jamescottrill is this a duplicate of #1463 ? Seems so on first read. If so, please upvote 1463 and close out this issue. If not, no worries!

@mooreds
Copy link
Collaborator

mooreds commented May 8, 2024

Actually, I take that back. It's slightly different, so I think we should leave it open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants