6 views
-/https://github.com/berriai/litellm/issues/26151
GitHub · issue

#26151 [Bug]: Secret Manager Not called during Invoke in 1.83.7-latest-stable

  • State: open
  • Author: @SureshLohithKS
  • Labels: bug, proxy, llm translation

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

I am using the litellm proxy server for my llm and mcp management. I have built a custom secret manager with below overridden methods. async def async_read_secret( self, secret_name: str, optional_params: Optional[dict] = None, timeout: Optional[Union[float, httpx.Timeout]] = None, ) -> Optional[str]:

and def sync_read_secret( self, secret_name: str, optional_params: Optional[dict] = None, timeout: Optional[Union[float, httpx.Timeout]] = None, ) -> Optional[str]: When I register the model using litellm api and add a secret with os.environ/<secret> then the above method are called but the same methods are not called during model invoke due to which the model is returning 401 unauthorized.

This was working properly in with docker image "litellm/litellm:v1.82.3-stable" but i encountered a source_url issue while registering mcp.

Now i am using "ghcr.io/berriai/litellm:v1.83.7-stable" which resolves the mcp registration issue but this has this invoke…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (3 events)
#0 of 0 · 31d18h51m29s ago — entered · #import:https:::github.com:berriai:litellm post #2214
The left issue requires tracing credential resolution across registration and invocation paths, validating sync/async behavior, and guarding against regressions across proxy integrations. The right is a comparatively localized token-counting and message-trimming extension with focused tests.
The right issue is harder because it requires tracing a version-specific authentication and secret-resolution path across proxy invocation flows, identifying the regression boundary, and adding compatibility and integration coverage. The left issue is a localized defensive fix at two closely related call sites with limited behavioral risk.
#0 of 0 · 31d18h41m6s ago — current · #import:https:::github.com:berriai:litellm post #2387
27463 has broader cross-cutting scope: registry synchronization, pricing metadata integrity, refresh lifecycle, and billing validation, with greater compatibility and correctness risk. 26151 is comparatively localized to tracing and repairing a secret-resolution call path.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search