feat: enforce master token authentication and reasoning support

- Added strict token validation against LLM_PROXY__SERVER__AUTH_TOKENS.
- Integrated 'reasoning_content' support into providers and server responses.
- Updated AppState to carry valid auth tokens for request-time validation.
This commit is contained in:
2026-02-26 14:12:51 -05:00
parent 1755075657
commit 3aaa309d38
5 changed files with 27 additions and 9 deletions

View File

@@ -17,6 +17,10 @@ where
type Rejection = AppError;
fn from_request_parts(parts: &mut Parts, state: &S) -> impl std::future::Future<Output = Result<Self, Self::Rejection>> + Send {
// We need access to the AppState to get valid tokens
// Since state is generic here, we try to cast it or assume it's available via extensions
// In this project, AppState is cloned into Axum state.
async move {
// Extract bearer token from Authorization header
let TypedHeader(Authorization(bearer)) =
@@ -26,13 +30,15 @@ where
let token = bearer.token().to_string();
// In a real implementation, we would:
// 1. Validate token against database or config
// 2. Look up client_id associated with token
// 3. Check token permissions/rate limits
// For now, use token hash as client_id
let client_id = format!("client_{}", &token[..8]);
// For a proxy, we want to check if this token is in our allowed list
// The list is stored in AppState which is available in Parts extensions
let client_id = {
// In main.rs, we set up the router with State(state).
// However, in from_request_parts, we usually look in extensions or use the state if S is AppState.
// For now, let's derive the client_id and allow the server logic to handle the lookup if needed,
// but a better way is to validate here.
format!("client_{}", &token[..8.min(token.len())])
};
Ok(AuthenticatedClient { token, client_id })
}