docs: make CF Access optional, clarify security model#6
Open
Conversation
- CF Access is now clearly optional (only needed for admin UI) - Added warning about CF Access blocking aX webhooks if enabled on entire domain - Reordered authentication layers: gateway token and HMAC are primary security - Added HMAC webhook verification to security docs - Added aX webhook troubleshooting tip - Updated secrets reference: CF_ACCESS_* marked as optional Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
ax-moltworker | 05d8986 | Feb 04 2026, 07:45 PM |
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
1 participant
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
/_admin/CF_ACCESS_TEAM_DOMAINandCF_ACCESS_AUDas optional in the secrets tableContext
CF Access was listed as a required setup step, but enabling it on the entire
workers.devdomain blocks all external requests including aX Platform webhooks to/ax/dispatch. The worker is already secured by the gateway token (Control UI), HMAC verification (webhooks), and device pairing.Test plan
🤖 Generated with Claude Code