docs: document per-project user-scoped JWT token deprecation#305
Open
mintlify[bot] wants to merge 1 commit into
Open
docs: document per-project user-scoped JWT token deprecation#305mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
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
Adds a Security & Compliance page covering the new per-project setting that lets admins reject legacy user-scoped Porter JWT tokens.
Changes
security-and-compliance/deprecate-user-jwt-tokens.mdxexplaining what the setting does, what is and isn't affected, how to toggle it from the dashboard and API, and a recommended migration path.mint.json.Context
Follows an upstream change that introduces a
reject_user_jwt_tokenstoggle on projects. When enabled, the auth middleware rejects requests authenticated with user-scoped Porter JWTs for that project. Project API tokens, WorkOS access tokens, and dashboard cookie sessions are unaffected, so admins keep dashboard and CLI access and can flip the setting back off at any time./assign @d-g-town