Project

General

Profile

Actions
Copy link

Feature #37115

closed

Update last_login_on when sending requests with API Key

Added by Andreas Skorczyk about 4 years ago. Updated 1 day ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Accounts / authentication
Target version:
-
Resolution:
Fixed

Description

Currently, users that access Redmine through the API with a given API key won't surface, as their last_login_on field doesn't get updated. This is a bit problematic in our case, as we can't easily distinguish between an inactive user and one that solely uses the API. The attached patch would change this behavior by calling user.update_last_login_on when finding the user via the API key.
Do you think it makes sense to apply this change or are there reasons against it?

Files

update_last_login_on_on_api_key.patch (409 Bytes) update_last_login_on_on_api_key.patch Andreas Skorczyk, 2022-05-13 11:14

Related issues

Related to Redmine - Defect #20648: Users' "Last connection" is not updated correctly.ClosedActions
Related to Redmine - Feature #43938: Track last usage of API and Atom access keysClosedMarius BĂLTEANUActions
Actions
Copy link

Also available in: Atom PDF