You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: text/0032-improved-api-tokens.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -117,7 +117,7 @@ This also allows for a smooth transition of self-hosted instances keeping pace w
117
117
First, we will need to support naming and showing a mostly obfuscated token in the UI to help users identify them.
118
118
119
119
1. The frontend is updated to no longer display the token value for existing tokens. [#61941](https://github.com/getsentry/sentry/pull/61941)
120
-
2. Nullable `name` and `token_last_characters` fields are added to the `ApiToken` model.
120
+
2. Nullable `name` and `token_last_characters` fields are added to the `ApiToken` model.[#58945](https://github.com/getsentry/sentry/pull/58945)
121
121
- New `ApiToken`s created should automatically have the `token_last_characters` populated based on an option.
122
122
The option is required in order to properly test the upcoming backfill migration. [#62972](https://github.com/getsentry/sentry/pull/62972)
123
123
3. A backfill migration is created and ran to fill in the `token_last_characters` for all `ApiToken` entries. [#63342](https://github.com/getsentry/sentry/pull/63342)
0 commit comments