Skip to content

feat(elliptic-proxy): map upstream 401/403 to a clear error for BYOK - #834

Draft
avi-starkware wants to merge 1 commit into
avi/elliptic-byok/docsfrom
avi/elliptic-byok/elliptic-auth-passthrough
Draft

feat(elliptic-proxy): map upstream 401/403 to a clear error for BYOK#834
avi-starkware wants to merge 1 commit into
avi/elliptic-byok/docsfrom
avi/elliptic-byok/elliptic-auth-passthrough

Conversation

@avi-starkware

@avi-starkware avi-starkware commented Jun 18, 2026

Copy link
Copy Markdown
Collaborator

When a BYOK request's own Elliptic credentials are rejected upstream (401/403),
return 401 'elliptic rejected credentials' instead of the generic 502, so a
BYOK client can distinguish bad credentials from an Elliptic outage. The
operator-managed partner path keeps the 502.

Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com


This change is Reviewable

avi-starkware commented Jun 18, 2026

Copy link
Copy Markdown
Collaborator Author

When a BYOK request's own Elliptic credentials are rejected upstream (401/403),
return 401 'elliptic rejected credentials' instead of the generic 502, so a
BYOK client can distinguish bad credentials from an Elliptic outage. The
operator-managed partner path keeps the 502.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@avi-starkware
avi-starkware force-pushed the avi/elliptic-byok/elliptic-auth-passthrough branch from 98437e8 to e969ecc Compare June 18, 2026 12:33
@avi-starkware
avi-starkware force-pushed the avi/elliptic-byok/docs branch from 6948948 to f215c9f Compare June 18, 2026 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant