Repository navigation
docs: OIDC LLM forwarding design + implementation plans - #18
Merged
Merged
Conversation
Two-PR plan:
- PR-1 merges upstream danny-avila/LibreChat @ v0.8.6 (756 commits), preserving
the legacy uid-${openidId} flow so production continues to function.
- PR-2 replaces uid-${openidId} with forwarding the user's real OIDC
access_token as the LLM gateway credential (apiKey = access_token, per-SDK
header chosen by the SDK). Adds ensureLLMBearer + refreshOIDCAccessToken
helpers, a 60s pre-refresh leeway with per-user in-process dedup, and a
startup guard rejecting non-OIDC providers when OIDC_FORWARD_TO_LLM=true.
Reuses upstream infrastructure where it already exists: federatedTokens
propagation (LibreChat-AI#9931), per-user resolveHeaders (LibreChat-AI#13616), refreshTokenGrant +
setOpenIDAuthTokens, OPENID_REUSE_MAX_SESSION_AGE_MS (LibreChat-AI#13546).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…orwarding)
PR-1 plan: step-by-step conflict resolution for the 756-commit upstream
merge to danny-avila/LibreChat @ v0.8.6, preserving fork-only customizations
and the legacy uid-${openidId} flow.
PR-2 plan: TDD-driven implementation of OIDC access_token forwarding to
the LLM gateway, in 6 commits matching the design doc structure (helper,
null-res patch, bridge, initializer wiring, legacy removal, startup guard).
Both plans live under docs/superpowers/plans/ and use checkbox-tracked
bite-sized steps suitable for subagent-driven-development or
executing-plans skills.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The PR-2 design covers chat-completion endpoints (openAI / anthropic / custom / assistants / azureAssistants). Bedrock and google use AWS SigV4 and GCP service-account auth flows that are incompatible with bearer-token forwarding; document the exclusion explicitly in both section 5.3.3 (per-file insertion points) and section 6.5 (security invariants) so future readers do not assume the omission is a bug. Also adds the regular OpenAI Assistants initializer (api/server/services/Endpoints/assistants/initalize.js) to the per-file table — it was missed in the original design and added in PR-2 C8. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Lands the design spec and the two implementation plans so subsequent PR-1 (#16) and PR-2 (#17) reference real paths on `main`.
Contents
Merge order
🤖 Generated with Claude Code