Repository navigation
feat(host-cloudflare): ExecutorInternal service-binding entrypoint - #12
Merged
Merged
Conversation
Export a WorkerEntrypoint whose fetch serves the same app and MCP routes as the public fetch for workers in the same account that reach it over a service binding. The binding is the trust boundary, so a request carries no Access credentials: it acts as the configured delegator service, or as the subject named in X-Executor-Subject. The trusted mode lives on a config only the entrypoint builds, never on env or a request, so the public fetch cannot enter it.
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.
Adds a second door to the Cloudflare host: an
ExecutorInternalWorkerEntrypoint that a worker in the same account binds withentrypoint: "ExecutorInternal".ACCESS_DELEGATION_COMMON_NAME, the same rows that service token reaches through Access).X-Executor-Subject/X-Executor-Subject-Emailit acts for that person, same mapping asapplyDelegatedSubject. An email with no subject is rejected.loadConfig(env, { internal: true })). Nothing inenvor a request can put the publicfetchin that mode.Tests:
internalPrincipalcases, and both doors through the realmakeAccessVerifier(public rejects a delegation header with no assertion, internal accepts it). Mutation-checked: disabling the internal branch fails the door test.Deploy this before any caller declares the entrypoint binding.