# Fallback MFA instead of MFA reset

**URL:** <https://community.netwrix.com/t/fallback-mfa-instead-of-mfa-reset/10844>\
**Category:** Password Secure Ideas\
**Tags:** planned, mfa\
**Created:** [April 25, 2025, 9:24am UTC](https://community.netwrix.com/t/fallback-mfa-instead-of-mfa-reset/10844 "2025-04-25T09:24:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![zander](https://yyz1.discourse-cdn.com/netwrix/user_avatar/community.netwrix.com/zander/32/1237_2.png) [@zander](https://community.netwrix.com/u/zander)\
**Post date:** [April 25, 2025, 9:24am UTC](https://community.netwrix.com/t/fallback-mfa-instead-of-mfa-reset/10844/1 "2025-04-25T09:24:35Z")

</div>

### What is a one sentence summary of your feature request?

Using a second MFA Method when the first isn’t available, instead of resetting the whole MFA Method for the user

### Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

We’re using a Yubikey as a MFA method. But what happens when you loose your Yubikey or it happens to be not around you. We would like to use OpenOTP as a Fallback Method if this happens. Or any other MFA method available.

### How do you currently solve the challenges you have by not having this feature?

You need to reset the MFA method for the user.

---

<div class="post-metadata">

**Author:** ![Kristina.kaya](https://avatars.discourse-cdn.com/v4/letter/k/a4c791/32.png) [@Kristina.kaya](https://community.netwrix.com/u/Kristina.kaya)\
**Post date:** [April 29, 2025, 1:40pm UTC](https://community.netwrix.com/t/fallback-mfa-instead-of-mfa-reset/10844/2 "2025-04-29T13:40:14Z")

</div>

Hi Sascha,

Thanks for your suggestion! We’ve noted your idea of using a second MFA method as a fallback and will make sure the team takes a look at it. We’ll update you once we have more information on how we can move forward with this.

Thanks again for bringing this to our attention!

Best,

Kristina

---

<div class="post-metadata">

**Author:** ![Florian23](https://avatars.discourse-cdn.com/v4/letter/f/df705f/32.png) [@Florian23](https://community.netwrix.com/u/Florian23)\
**Post date:** [August 14, 2025, 1:37pm UTC](https://community.netwrix.com/t/fallback-mfa-instead-of-mfa-reset/10844/3 "2025-08-14T13:37:49Z")

</div>

We would be interested in that aswell, what is your status to that @Kristina.kaya

---

<div class="post-metadata">

**Author:** ![ssonntag2](https://avatars.discourse-cdn.com/v4/letter/s/6de8d8/32.png) [@ssonntag2](https://community.netwrix.com/u/ssonntag2)\
**Post date:** [June 11, 2026, 10:24am UTC](https://community.netwrix.com/t/fallback-mfa-instead-of-mfa-reset/10844/4 "2026-06-11T10:24:07Z")

</div>

We do use TOTP as second factor and would be interested in a fallback as well.

One idea would be to allow admins to give users a one-time-use shortcut, instead of resetting to whole MFA.

For now we do work with a workaround - setting the IP of the users device on the IP Filter list via Admin Client and database settings. However, this is a bit time consuming to pull off and can only be done by database-admins.

Could a one-time-password with email work?