-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Add comment/name to Auth Tokens #9600
Comments
GitLab tokens have names. GitHub tokens have names. DataDog tokens have names. The list never ends. Please let us define a name for Sentry tokens too. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Routing to @getsentry/ecosystem for triage. ⏲️ |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Closing feature requests ain't good. |
Don't want to be a +1'er but this feature is integral to any business use of Sentry. I've looked into the branch this request is tracking (75) and I can't see names for tokens mentioned. |
For those following this issue, I'm working on this. 🙂 Names on your API tokens should be available soon. |
Adds backend support for naming API tokens. - see issue #9600 and getsentry/customer-feedback#22 - #58918 - [RFC #32](getsentry/rfcs#32)
Adds backend support for naming API tokens. - see issue #9600 and getsentry/customer-feedback#22 - #58918 - [RFC #32](getsentry/rfcs#32)
We now support adding names to newly created tokens! 🙂 We don't yet have support for editing an existing token to add a name to it, but that'll be coming soon. |
With many Auth Tokens it's quite easy to loose track of them. Having comment or name field for each Auth Token it would be easier to found the ones which are no longer used and can be safely removed.
I'm currently using sentry.io service if that matters.
The text was updated successfully, but these errors were encountered: