feat(elliptic-proxy): BYOK screening with client-supplied Elliptic creds - #832
Draft
avi-starkware wants to merge 1 commit into
Draft
feat(elliptic-proxy): BYOK screening with client-supplied Elliptic creds#832avi-starkware wants to merge 1 commit into
avi-starkware wants to merge 1 commit into
Conversation
Collaborator
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Jun 18, 2026
When allowByok is enabled, a client that is not a registered partner may screen by supplying its own Elliptic key + secret in x-elliptic-key / x-elliptic-secret headers and self-signing the request (x-access-sign) with that secret. auth.ts gates and verifies the BYOK request and returns a synthetic 'byok:<hash>' rate-limit id (never the raw key); handler.ts sources the upstream creds from the BYOK result (guarding the partners lookup) and labels the verdict source 'byok'. The verdict is still signed with the proxy key, so the path is off by default. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
avi-starkware
force-pushed
the
avi/elliptic-byok/auth-and-routing
branch
from
June 18, 2026 12:33
a5880dc to
d64e7a0
Compare
avi-starkware
force-pushed
the
avi/elliptic-byok/config-gate
branch
from
June 18, 2026 12:33
96b2f1f to
087ee6e
Compare
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.
When allowByok is enabled, a client that is not a registered partner may screen
by supplying its own Elliptic key + secret in x-elliptic-key / x-elliptic-secret
headers and self-signing the request (x-access-sign) with that secret. auth.ts
gates and verifies the BYOK request and returns a synthetic 'byok:'
rate-limit id (never the raw key); handler.ts sources the upstream creds from
the BYOK result (guarding the partners lookup) and labels the verdict
source 'byok'. The verdict is still signed with the proxy key, so the path is
off by default.
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com
This change is