# 2FA Update - Two Factor Authentication

**URL:** https://community.baserow.io/t/2fa-update-two-factor-authentication/4255
**Category:** Feature Ideas
**Created:** [January 11, 2024, 9:33am UTC](https://community.baserow.io/t/2fa-update-two-factor-authentication/4255 "2024-01-11T09:33:35Z")
**Posts on this page:** 1
**Showing post:** 17

<div class="post-metadata">

### Author: ![spook](https://community.baserow.io/user_avatar/community.baserow.io/spook/32/2565_2.png) [@spook](https://community.baserow.io/u/spook)
#### Post date: [June 4, 2025, 5:53am UTC](https://community.baserow.io/t/2fa-update-two-factor-authentication/4255/17 "2025-06-04T05:53:25Z")

</div>

This is not an answer to your question, but it might help.

I use this monitoring script: [Fail2Ban or similar for public App access?](https://community.baserow.io/t/fail2ban-or-similar-for-public-app-access/10238) - which alerts me of failed logins (but gives no details of the username or IP)

To compliment that, I place BaseRow behind Nginx Reverse Proxy and using Fail2Ban. BaseRow responds with a 401 when a logon fails, so monitoring the NPM logs with Fail2Ban lets me see at least the IP addresses of failed logons and also ban them.

You could also monitor the NPM logs for successful logins if you want - and possibly also API calls.

However, none of this allows you to monitor which user logs in unfortunately, but hopefully it’s something.

---

_[View the full topic](https://community.baserow.io/t/2fa-update-two-factor-authentication/4255)._