# Blacklist Authenticator Fields

**URL:** <https://forum.kee.pm/t/blacklist-authenticator-fields/556>\
**Category:** Uncategorized\
**Created:** [January 8, 2018, 1:26pm UTC](https://forum.kee.pm/t/blacklist-authenticator-fields/556 "2018-01-08T13:26:27Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![luckyrat](https://forum.kee.pm/user_avatar/forum.kee.pm/luckyrat/32/10_2.png) [@luckyrat](https://forum.kee.pm/u/luckyrat)\
**Post date:** [January 8, 2018, 10:48pm UTC](https://forum.kee.pm/t/blacklist-authenticator-fields/556/2 "2018-01-08T22:48:27Z")

</div>

Probably you can just edit your KeePass entry for that website and delete the stored (outdated) 2FA form field.

> **[en | Options](https://github.com/kee-org/KeeFox/wiki/en-%7C-Options#keepass-edit-entry-and-edit-group-dialog)**
>
> Legacy browser and XUL application integration with KeePass Password Safe. See https://github.com/kee-org/browser-addon for the new version for Firefox 57+ - kee-org/KeeFox

If that doesn’t work, you might be interested in related feature we’re considering adding in future:

> [@Potential feature: Ignore some fields](https://forum.kee.pm/t/potential-feature-ignore-some-fields/561):
>
> Needs more detailed use cases and specification. When logging in using forms with some basic captcha functionality or other fields that change with every login operation, Kee will consider the login entry as different to any others already stored in the database and hence, unless disabled by configuration, will ask the user to save the new password. Could come up with a blacklist/whitelist system? With pre-populated magic names? (what? “captcha”? etc.) Also worth thinking about context - e.g.…

---

_[View the full topic](https://forum.kee.pm/t/blacklist-authenticator-fields/556)._
