Vast.io - help with custom authentication headers (Cloudflare Tunnel, API Tokens) #510
Unanswered
Floflobel
asked this question in
User Support
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Problem Summary
GuideLLM v0.4.0 fails to authenticate when connecting to backends protected by Cloudflare Tunnel or other custom authentication mechanisms that require specific HTTP headers or non-standard authentication tokens.
I use the vast.io service to try to perform benchmarks to compare GPU models.
Current Behavior
Token in URL query string: When using authentication tokens as query parameters (e.g.,
https://example.com/?token=xyz), GuideLLM appends paths like/healthand/v1/chat/completions, which breaks the authentication.Environment variable
OPENAI_API_KEY: Setting this variable doesn't pass the token to Cloudflare-protected endpoints, resulting in 401 Unauthorized errors.--backend-kwargsapproach: Attempting to pass custom headers via--backend-kwargs '{"extra_headers": {...}}'results in:Expected Behavior
According to the v0.3.0 release notes, PR #230 added "CLI options for custom headers and SSL verification" with "support for custom headers, SSL verification control, query parameters, and request body modifications" for the OpenAI Backend.[2]
However, the correct CLI syntax for passing custom authentication headers does not appear to be documented in:
guidellm benchmark --helpoutputQuestions
CF-Access-Client-Secret,X-Auth-Token, orAuthorization: Bearer)?--request-headersor--custom-headersflag that should be used?Examples
Environment
Beta Was this translation helpful? Give feedback.
All reactions