Skip to content
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

Closed
Tracked by #6
nijel opened this issue Sep 4, 2018 · 9 comments · Fixed by #64509
Closed
Tracked by #6

Add comment/name to Auth Tokens #9600

nijel opened this issue Sep 4, 2018 · 9 comments · Fixed by #64509

Comments

@nijel
Copy link

nijel commented Sep 4, 2018

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.

@Nowaker
Copy link

Nowaker commented Feb 21, 2020

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.

@BYK BYK added the Security label Oct 24, 2020
@BYK BYK self-assigned this Oct 24, 2020
@github-actions

This comment has been minimized.

@Nowaker

This comment has been minimized.

@getsentry-release
Copy link

Routing to @getsentry/ecosystem for triage. ⏲️

@github-actions
Copy link
Contributor

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 Status: Backlog or Status: In Progress, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

@Nowaker
Copy link

Nowaker commented Nov 12, 2021

Closing feature requests ain't good.

@Willt123
Copy link

Don't want to be a +1'er but this feature is integral to any business use of Sentry.
Currently, we're keeping a seperate spreadsheet of token last 4 digits to project mapping which is not great for security.

I've looked into the branch this request is tracking (75) and I can't see names for tokens mentioned.
Personally, I feel if a system allows you to request multiple tokens we should be able to name them, otherwise we're going to have to go down the route of creating an internal integration for each project just to to be able to name the token.

@mdtro
Copy link
Member

mdtro commented Jan 17, 2024

For those following this issue, I'm working on this. 🙂 Names on your API tokens should be available soon.
I'll update here once it is.

mdtro added a commit that referenced this issue Feb 2, 2024
Adds backend support for naming API tokens.

- see issue #9600 and
getsentry/customer-feedback#22
- #58918
- [RFC #32](getsentry/rfcs#32)
@mdtro mdtro linked a pull request Feb 5, 2024 that will close this issue
cmanallen pushed a commit that referenced this issue Feb 7, 2024
@mdtro
Copy link
Member

mdtro commented Feb 16, 2024

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.

@github-actions github-actions bot locked and limited conversation to collaborators Mar 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

10 participants