As part of the v17.1 release, we’re introducing a new feature: the Login History block. This new block, powered by a dedicated HistoryLogin model and database table, offers a clearer and more accurate view of actual login events.
During development, we initially planned to migrate all existing login-related entries (where [Verb] = 'LOGIN') from the longstanding [History] table to the new table. However, after careful analysis, we found that those existing records include a significant amount of noise. In many cases, Rock was logging what looked like login events - but actually weren’t. For instance:
- When an individual starts a new Rock session in their browser and a valid preexisting authentication cookie is found.
- When an individual opens a Rock mobile or TV app and they're already-authenticated from a previous session.
These aren’t true login events, but they’ve historically been logged as such. The result? A lot of clutter in the login history that can lead to confusion rather than clarity.
To ensure the new Login History starts clean and meaningful, we will not be migrating these noisy records. Instead, Rock will delete all [History] records where [Verb] = 'LOGIN' during the upgrade to v17.1. Moving forward, only true login actions - like entering a username and password, using passwordless login, or completing an OIDC flow - will be recorded in the new table.
We know data removal is a big deal. But in this case, it gives us a better foundation to build on - one that's accurate, helpful, and free of historical clutter. It’s all part of our ongoing effort to make Rock more reliable and insightful for you and your team.