No email notification for expiring project access token
Summary
One of our customers (internal) reported that they are only receiving notifications for expiring group access tokens, but not for expiring project access tokens.
I was able to reproduce this in GitLab 16.11.1
Steps to reproduce
- Create a project access token that expires the next day.
- Run
PersonalAccessTokens::ExpiringWorker.new.perform
in the Rails console.
After this, expire_notification_delivered
is set to true
but no notification is delivered to the project owner.
Example Project
What is the current bug behavior?
No email notification to project owners for expiring Project Access tokens.
What is the expected correct behavior?
Email notifications should be sent for expiring Project access 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)
Proposal
From groupauthentication Currently only Project maintainers and group owners are intended to recieve notification email. As part of this issue we are correcting an issue where that worked may fail if the resource bot was unavailable (higher priority). Based on the requests, Project owners will also be sent notifications as an enhancement.