feat(auth-api): Revoke tokens from a deleted workspace #7882
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Due to a recent change to allow a workspace token to create and manage the workspace lifecycle, we need to revoke the tokens for a workspace when the workspace has been deleted This means the usage of that token cannot be made at all! We don’t want tokens to be in circulation that allow a user to create or update workspaces if they are not actually able to be revoked or expired This work also includes a migration to allow us to revoke existing tokens that would have fallen through the cracks here
Dependency Review✅ No vulnerabilities or OpenSSF Scorecard issues found.Scanned FilesNone |
aaron-dernley
approved these changes
Nov 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to a recent change to allow a workspace token to create and manage the workspace lifecycle, we need to revoke the tokens for a workspace when the workspace has been deleted
This means the usage of that token cannot be made at all! We don’t want tokens to be in circulation that allow a user to create or update workspaces if they are not actually able to be revoked or expired
This work also includes a migration to allow us to revoke existing tokens that would have fallen through the cracks here
Also introduces a reason into the revokeToken posthog event so that we can tell a user the token has been revoked based on
Xaction