Is there a simple way to blacklist the third field (Authenticator) so Kee doesn’t try to fill this one? I’m talking about this page https://bitcoinvest.de/en/
Probably you can just edit your KeePass entry for that website and delete the stored (outdated) 2FA form field.
If that doesn’t work, you might be interested in related feature we’re considering adding in future:
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.…