Conversation
Author
|
Withdrawing this PR before merge so the web-import URL fragment can use the clearer |
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
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
tfCLI instance.http://127.0.0.1:43110-43119. TokenRouter adds no backend import or authentication endpoints, and API keys do not pass through the TokenRouter backend./keys#tf=1.<port>.<secret>sessions initiated bytf login --from-web. Router initialization strips every#tffragment before auth redirects and retains valid sessions in module memory for 10 minutes.group_idandgroup_namefor standard keys, while composite keys omit source group metadata.tf.ed4df86. This branch is based on TokenRouter v0.1.276 (07fc006c3).Security and compatibility
X-TF-Session-Proofheader verify only possession of the active session secret and request payload integrity. They do not authenticate the web page, API key, local binary, gateway results, freshness, or replay resistance.tfprocesses the request.deploy/config.example.yamlexplicitly allowhttp://127.0.0.1:43110throughhttp://127.0.0.1:43119without wildcards.Validation
vue-tsc --noEmitpassed.pnpm buildpassed with only existing lottie eval, chunk-size, and mixed static/dynamic import warnings.go test ./...passed.git diff --checkpassed.tfCLI checks covered verified proof headers with an emptyReferer, the unverified warning flow, terminal confirmation, HTTP 202 handling, composite metadata omission, responsive desktop/mobile layouts, and isolated0600credential persistence.