docs: add legacy JWT token usage tracking page#321
Open
mintlify[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
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.
Summary
Documents the new project-admin controls for tracking and disabling legacy user-scoped JWT tokens ahead of their end-of-June 2026 deprecation.
Changes
security-and-compliance/legacy-jwt-token-usage.mdxcovering:porter config set-login-method v2 && porter auth login, or switch CI to a project-scoped API token).Context
The triggering PR adds an admin-only endpoint and dashboard panel that list recent legacy JWT token usage alongside the existing project-wide rejection toggle, so admins can audit who would be affected before flipping the switch.
The dashboard panel is gated by the
user_session_management_enabledfeature flag, so the new page is intentionally not linked frommint.json— it can be linked once the flag is removed.cc @d-g-town for review.