-
Notifications
You must be signed in to change notification settings - Fork 643
API token expiry warning emails #8154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I haven't seen this feature on other products and platforms. Do you have any examples we can refer to? Are you working on this? If not, do you mind me to take it and help implement it? |
can't think of one, but what I have in mind is a "Duplicate" button on each of the existing tokens that would take you to the "Create API token" page with the scopes from the other token filled in and a name of e.g. "XXX (Copy)".
Sure, go ahead! :) |
I'll follow up with the infra team on Zulip in regards to hardening our DMARC and SPF configurations in preparation for sending these emails. 🙂 |
I was too busy last week, but I will begin working on the design and implementation this week. |
Since the API token expiry notification emails have been implemented I will close this issue now. The token copy functionality has its own issue now: #8717 :) |
Some time last year we introduced optional expiration periods for API tokens. One caveat of the existing system is that users don't get notified when their tokens expire and they have to proactively monitor this if they use expiration.
In our team meeting on Friday we discussed how we could improve the situation and one idea was to automatically send out warning emails when an API token expires.
As #6664 (comment) states, such emails are seen as a requirement before we can change the default expiration setting on the API token creation page.
A couple of open questions:
In terms of implementation:
api_tokens
table.api_tokens
table for tokens that have expired (or are going to expire) and where a warning has not been sent yet, and then sends out such a warning email.The text was updated successfully, but these errors were encountered: