Defect #42812
open
Last-login date recorded incorrectly
0%
Description
In Redmine, each user’s “last login” date is supposed to be recorded automatically.
However, we have found that the stored date sometimes differs from the user’s actual last login.
For example, in the attached screenshot of my own account, I logged in on 2 June, yet the “Last login” field shows 28 May. All of our users authenticate via SAML.
Questions
・Are there known causes or conditions that could lead to this kind of discrepancy?
Any insight would be greatly appreciated. Thank you.
Files
Updated by Holger Just 26 days ago
- Status changed from New to Needs feedback
The last_login_on field is updated when a user logs in with a username / password (i.e. when using the built-in authentication with a stored password or with an external LDAP server), or when automatically logging in with an autologin cookie. It is also not set when authenticating via Basic Auth as this would update the field on each and every request.
Since you state that your users login via SAML (which is not supported by Redmine out of the box), you are likely using a plugin or some custom configuration. Here, the field may not be updated as expected by your plugin. Please contact the plugin authors in that case. If you are using an unchanged Redmine, please provide more details about your configuration.