This repository was archived by the owner on Sep 21, 2026. It is now read-only.
Repository navigation
docs: stop documenting key and JWT minting from existing credentials - #3178
Merged
Merged
Conversation
Cloud no longer allows project.createKey or account.createJWT, so leaked credentials cannot mint replacements.
Appwrite WebsiteProject ID: Website (appwrite/website)Project ID: Tip HTTPS and SSL certificates are handled automatically for all your Sites |
Contributor
Greptile SummaryThe PR updates credential-creation guidance to match Cloud restrictions and retires documentation for minting replacement credentials.
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains. Important Files Changed
Reviews (4): Last reviewed commit: "docs: rephrase changelog so leaked crede..." | Re-trigger Greptile |
The guide depended on minting long-lived keys from the API, which Cloud no longer allows.
adityaoberai
approved these changes
Aug 17, 2026
adityaoberai
left a comment
Contributor
There was a problem hiding this comment.
Took a quick glance, just one comment there
Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
project.createKeyand clientaccount.createJWTfrom docs, matching Cloud blocking those methods so leaked credentials cannot mint replacements.users.createJWT, keep Console + ephemeral key flows, and add info notes on the API keys, key rotation, and JWT pages.Test plan
/docs/partners/project/api-keyshas no create-key SDK examples and shows the Creating keys info note/docs/partners/project/key-rotationsends long-lived key creation to the Console and still documents list/update/delete/ephemeral/docs/products/auth/jwtusesusers.createJWTand links the changelog/changelog/entry/2026-08-17renders