Access token "Last Used" date is incorrect
Summary
As described in this ticket (internal only), there's a seemingly isolated incident where the "Last Used" date for a token was not updated which caused the token to be revoked and several access issues
Steps to reproduce
Under investigation
This was a personal access token being used as a pull secret only with registry_read access, maybe authentications to registry don't trigger an update on the token use date? (I'll confirm this in the upcoming days)\
Example Project
Please see summary
What is the current bug behavior?
"Last Used" date is incorrect for tokens
What is the expected correct behavior?
"Last Used" date should be correct for tokens
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)(we will only investigate if the tests are passing)