Skip to content

Clarify credential binding destination approval - #26720

Open
dvdksn wants to merge 4 commits into
mainfrom
docsflow/docs-ep8mm
Open

dvdksn wants to merge 4 commits into
mainfrom
docsflow/docs-ep8mm

Conversation

@dvdksn

@dvdksn dvdksn commented Nov 20, 2026

Copy link
Copy Markdown
Contributor

Clarify that credential bindings must approve destinations separately for API keys and OAuth, and that bindings with no destinations are treated as missing. Document the exception for custom secrets in authentication headers on kit routes denied by binding approval.

Validation: the changed page passes rumdl and Vale. Runtime tests could not run because the installed Go toolchain is older than the required version.

Credential guidance implied that mechanism presence alone grants approval and that custom secrets always replace header placeholders. Require approved destinations for each mechanism and explain authentication header stripping on denied kit routes.
@netlify

netlify Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 9146ff0
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/6b005f3f2bfeed1597ceed8a
😎 Deploy Preview https://deploy-preview-26720--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

The credential guide described routing internals instead of explaining what readers need to approve. Put separate API key and OAuth domain approvals next to the binding example and explain how denied requests affect custom secrets.
@dvdksn dvdksn added this to the sbx/v0.55.0 milestone Nov 20, 2026
The credential guide repeated kit scope and mixed approval concepts. Explain the domain lists beside the example and state what happens to custom secrets in blocked authentication headers.
Credential approval applies regardless of kit schema version. Refer to kits
without a v2 qualifier in the inherited-credential guidance.
@dvdksn
dvdksn marked this pull request as ready for review November 20, 2026 15:39
@dvdksn
dvdksn requested review from a team and mdelapenya November 20, 2026 15:39

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants