Improve local development credential documentation #402
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
Contributor
|
@ivanauth is attempting to deploy a commit to the authzed Team on Vercel. A member of the Team first needs to authorize it. |
ivanauth
force-pushed
the
fix/clarify-insecure-credentials-docs
branch
3 times, most recently
from
fa43b84 to
67e90b9
Compare
Fix Node.js credential constant to include the correct v1.ClientSecurity. namespace prefix matching the @authzed/authzed-node client library API. Update documentation to be more precise about local development scenarios.
ivanauth
force-pushed
the
fix/clarify-insecure-credentials-docs
branch
from
67e90b9 to
5780910
Compare
miparnisari
force-pushed
the
fix/clarify-insecure-credentials-docs
branch
from
4071db3 to
1b9626a
Compare
miparnisari
approved these changes
Dec 9, 2025
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Addresses #350 by clarifying when to use
INSECURE_PLAINTEXT_CREDENTIALSvsINSECURE_LOCALHOST_ALLOWEDfor local development scenarios.Changes
Context
Teams using Orbstack or Docker with non-localhost hostnames (e.g.,
*.orb.local) were confused about which security setting to use. This makes it clear that insecure plaintext credentials work for all local development scenarios including localhost, Docker, Orbstack, and other non-TLS setups.Fixes #350