{"entries":[{"lastCommit":{"author":{"email":"levy@andes.is","name":"Jón Levy","when":"2025-11-21T14:44:52.000000Z"},"committer":{"email":"danny@librechat.ai","name":"Danny Avila","when":"2025-11-21T09:51:11.000000-05:00"},"hash":"ef3bf0a9321eb8b0a3c1cab7b8b2cec4794ab346","message":"🆔 feat: Add OpenID Connect Federated Provider Token Support (#9931)\n\n* feat: Add OpenID Connect federated provider token support\n\nImplements support for passing federated provider tokens (Cognito, Azure AD, Auth0)\nas variables in LibreChat's librechat.yaml configuration for both custom endpoints\nand MCP servers.\n\nFeatures:\n- New LIBRECHAT_OPENID_* template variables for federated provider tokens\n- JWT claims parsing from ID tokens without verification (for claim extraction)\n- Token validation with expiration checking\n- Support for multiple token storage locations (federatedTokens, openidTokens)\n- Integration with existing template variable system\n- Comprehensive test suite with Cognito-specific scenarios\n- Provider-agnostic design supporting Cognito, Azure AD, Auth0, etc.\n\nSecurity:\n- Server-side only token processing\n- Automatic token expiration validation\n- Graceful fallbacks for missing/invalid tokens\n- No client-side token exposure\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)\n\nCo-Authored-By: Claude \n\n* fix: Add federated token propagation to OIDC authentication strategies\n\nAdds federatedTokens object to user during authentication to enable\nfederated provider token template variables in LibreChat configuration.\n\nChanges:\n- OpenID JWT Strategy: Extract raw JWT from Authorization header and\n attach as federatedTokens.access_token to enable {{LIBRECHAT_OPENID_TOKEN}}\n placeholder resolution\n- OpenID Strategy: Attach tokenset tokens as federatedTokens object to\n standardize token access across both authentication strategies\n\nThis enables proper token propagation for custom endpoints and MCP\nservers that require federated provider tokens for authorization.\n\nResolves missing token issue reported by @ramden in PR #9931\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)\n\nCo-Authored-By: Denis Ramic \nCo-Authored-By: Claude \n\n* test: Add federatedTokens validation tests for OIDC strategies\n\nAdds comprehensive test coverage for the federated token propagation\nfeature implemented in the authentication strategies.\n\nTests added:\n- Verify federatedTokens object is attached to user with correct structure\n (access_token, refresh_token, expires_at)\n- Verify both tokenset and federatedTokens are present in user object\n- Ensure tokens from OIDC provider are correctly propagated\n\nAlso fixes existing test suite by adding missing mocks:\n- isEmailDomainAllowed function mock\n- findOpenIDUser function mock\n\nThese tests validate the fix from commit 5874ba29f that enables\n{{LIBRECHAT_OPENID_TOKEN}} template variable functionality.\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)\n\nCo-Authored-By: Claude \n\n* docs: Remove implementation documentation file\n\nThe PR description already contains all necessary implementation details.\nThis documentation file is redundant and was requested to be removed.\n\n* fix: skip s256 check\n\n* fix(openid): handle missing refresh token in Cognito token refresh response\n\nWhen OPENID_REUSE_TOKENS=true, the token refresh flow was failing because\nCognito (and most OAuth providers) don't return a new refresh token in the\nrefresh grant response - they only return new access and ID tokens.\n\nChanges:\n- Modified setOpenIDAuthTokens() to accept optional existingRefreshToken parameter\n- Updated validation to only require access_token (refresh_token now optional)\n- Added logic to reuse existing refresh token when not provided in tokenset\n- Updated refreshController to pass original refresh token as fallback\n- Added comments explaining standard OAuth 2.0 refresh token behavior\n\nThis fixes the \"Token is not present. User is not authenticated.\" error that\noccurred during silent token refresh with Cognito as the OpenID provider.\n\nFixes: Authentication loop with OPENID_REUSE_TOKENS=true and AWS Cognito\n\n* fix(openid): extract refresh token from cookies for template variable replacement\n\nWhen OPENID_REUSE_TOKENS=true, the openIdJwtStrategy populates user.federatedTokens\nto enable template variable replacement (e.g., {{LIBRECHAT_OPENID_ACCESS_TOKEN}}).\n\nHowever, the refresh_token field was incorrectly sourced from payload.refresh_token,\nwhich is always undefined because:\n1. JWTs don't contain refresh tokens in their payload\n2. The JWT itself IS the access token\n3. Refresh tokens are separate opaque tokens stored in HTTP-only cookies\n\nThis caused extractOpenIDTokenInfo() to receive incomplete federatedTokens,\nresulting in template variables remaining unreplaced in headers.\n\n**Root Cause:**\n- Line 90: `refresh_token: payload.refresh_token` (always undefined)\n- JWTs only contain access token data in their claims\n- Refresh tokens are separate, stored securely in cookies\n\n**Solution:**\n- Import `cookie` module to parse cookies from request\n- Extract refresh token from `refreshToken` cookie\n- Populate federatedTokens with both access token (JWT) and refresh token (from cookie)\n\n**Impact:**\n- Template variables like {{LIBRECHAT_OPENID_ACCESS_TOKEN}} now work correctly\n- Headers in librechat.yaml are properly replaced with actual tokens\n- MCP server authentication with federated tokens now functional\n\n**Technical Details:**\n- passReqToCallback=true in JWT strategy provides req object access\n- Refresh token extracted via cookies.parse(req.headers.cookie).refreshToken\n- Falls back gracefully if cookie header or refreshToken is missing\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)\n\nCo-Authored-By: Claude \n\n* fix: re-resolve headers on each request to pick up fresh federatedTokens\n\n- OpenAIClient now re-resolves headers in chatCompletion() before each API call\n- This ensures template variables like {{LIBRECHAT_OPENID_TOKEN}} are replaced\n with actual token values from req.user.federatedTokens\n- initialize.js now stores original template headers instead of pre-resolved ones\n- Fixes template variable replacement when OPENID_REUSE_TOKENS=true\n\nThe issue was that headers were only resolved once during client initialization,\nbefore openIdJwtStrategy had populated user.federatedTokens. Now headers are\nre-resolved on every request with the current user's fresh tokens.\n\n* debug: add logging to track header resolution in OpenAIClient\n\n* debug: log tokenset structure after refresh to diagnose missing access_token\n\n* fix: set federatedTokens on user object after OAuth refresh\n\n- After successful OAuth token refresh, the user object was not being\n updated with federatedTokens\n- This caused template variable resolution to fail on subsequent requests\n- Now sets user.federatedTokens with access_token, id_token, refresh_token\n and expires_at from the refreshed tokenset\n- Fixes template variables like {{LIBRECHAT_OPENID_TOKEN}} not being\n replaced after token refresh\n- Related to PR #9931 (OpenID federated token support)\n\n* fix(openid): pass user object through agent chain for template variable resolution\n\nRoot cause: buildAgentContext in agents/run.ts called resolveHeaders without\nthe user parameter, preventing OpenID federated token template variables from\nbeing resolved in agent runtime parameters.\n\nChanges:\n- packages/api/src/agents/run.ts: Add user parameter to createRun signature\n- packages/api/src/agents/run.ts: Pass user to resolveHeaders in buildAgentContext\n- api/server/controllers/agents/client.js: Pass user when calling createRun\n- api/server/services/Endpoints/bedrock/options.js: Add resolveHeaders call with debug logging\n- api/server/services/Endpoints/custom/initialize.js: Add debug logging\n- packages/api/src/utils/env.ts: Add comprehensive debug logging and stack traces\n- packages/api/src/utils/oidc.ts: Fix eslint errors (unused type, explicit any)\n\nThis ensures template variables like {{LIBRECHAT_OPENID_TOKEN}} and\n{{LIBRECHAT_USER_OPENIDID}} are properly resolved in both custom endpoint\nheaders and Bedrock AgentCore runtime parameters.\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)\n\nCo-Authored-By: Claude \n\n* refactor: remove debug logging from OpenID token template feature\n\nRemoved excessive debug logging that was added during development to make\nthe PR more suitable for upstream review:\n\n- Removed 7 debug statements from OpenAIClient.js\n- Removed all console.log statements from packages/api/src/utils/env.ts\n- Removed debug logging from bedrock/options.js\n- Removed debug logging from custom/initialize.js\n- Removed debug statement from AuthController.js\n\nThis reduces the changeset by ~50 lines while maintaining full functionality\nof the OpenID federated token template variable feature.\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)\n\nCo-Authored-By: Claude \n\n* test(openid): add comprehensive unit tests for template variable substitution\n\n- Add 34 unit tests for OIDC token utilities (oidc.spec.ts)\n- Test coverage for token extraction, validation, and placeholder processing\n- Integration tests for full OpenID token flow\n- All tests pass with comprehensive edge case coverage\n\n🤖 Generated with Claude Code\nCo-Authored-By: Claude \n\n* test: fix OpenID federated tokens test failures\n\n- Add serverMetadata() mock to openid-client mock configuration\n * Fixes TypeError in openIdJwtStrategy.js where serverMetadata() was being called\n * Mock now returns jwks_uri and end_session_endpoint as expected by the code\n\n- Update outdated initialize.spec.js test\n * Remove test expecting resolveHeaders call during initialization\n * Header resolution was refactored to be deferred until LLM request time\n * Update test to verify options are returned correctly with useLegacyContent flag\n\nFixes #9931 CI failures for backend unit tests\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)\n\nCo-Authored-By: Claude \n\n* chore: fix package-lock.json conflict\n\n* chore: sync package-log with upstream\n\n* chore: cleanup\n\n* fix: use createSafeUser\n\n* fix: fix createSafeUser signature\n\n* chore: remove comments\n\n* chore: purge comments\n\n* fix: update Jest testPathPattern to testPathPatterns for Jest 30+ compatibility\n\n---------\n\nCo-authored-by: Claude \nCo-authored-by: Denis Ramic \nCo-authored-by: kristjanaapro \n\nchore: import order and add back JSDoc for OpenID JWT callback\n","tree":"9eb3a8c74c976e9215748d12376aaa3842186a35"},"mode":"0100644","name":"oidc-integration.test.ts","size":16208}],"lastCommit":{"author":{"email":"levy@andes.is","name":"Jón Levy","when":"2025-11-21T14:44:52.000000Z"},"committer":{"email":"danny@librechat.ai","name":"Danny Avila","when":"2025-11-21T09:51:11.000000-05:00"},"hash":"ef3bf0a9321eb8b0a3c1cab7b8b2cec4794ab346","message":"🆔 feat: Add OpenID Connect Federated Provider Token Support (#9931)\n\n* feat: Add OpenID Connect federated provider token support\n\nImplements support for passing federated provider tokens (Cognito, Azure AD, Auth0)\nas variables in LibreChat's librechat.yaml configuration for both custom endpoints\nand MCP servers.\n\nFeatures:\n- New LIBRECHAT_OPENID_* template variables for federated provider tokens\n- JWT claims parsing from ID tokens without verification (for claim extraction)\n- Token validation with expiration checking\n- Support for multiple token storage locations (federatedTokens, openidTokens)\n- Integration with existing template variable system\n- Comprehensive test suite with Cognito-specific scenarios\n- Provider-agnostic design supporting Cognito, Azure AD, Auth0, etc.\n\nSecurity:\n- Server-side only token processing\n- Automatic token expiration validation\n- Graceful fallbacks for missing/invalid tokens\n- No client-side token exposure\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)\n\nCo-Authored-By: Claude \n\n* fix: Add federated token propagation to OIDC authentication strategies\n\nAdds federatedTokens object to user during authentication to enable\nfederated provider token template variables in LibreChat configuration.\n\nChanges:\n- OpenID JWT Strategy: Extract raw JWT from Authorization header and\n attach as federatedTokens.access_token to enable {{LIBRECHAT_OPENID_TOKEN}}\n placeholder resolution\n- OpenID Strategy: Attach tokenset tokens as federatedTokens object to\n standardize token access across both authentication strategies\n\nThis enables proper token propagation for custom endpoints and MCP\nservers that require federated provider tokens for authorization.\n\nResolves missing token issue reported by @ramden in PR #9931\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)\n\nCo-Authored-By: Denis Ramic \nCo-Authored-By: Claude \n\n* test: Add federatedTokens validation tests for OIDC strategies\n\nAdds comprehensive test coverage for the federated token propagation\nfeature implemented in the authentication strategies.\n\nTests added:\n- Verify federatedTokens object is attached to user with correct structure\n (access_token, refresh_token, expires_at)\n- Verify both tokenset and federatedTokens are present in user object\n- Ensure tokens from OIDC provider are correctly propagated\n\nAlso fixes existing test suite by adding missing mocks:\n- isEmailDomainAllowed function mock\n- findOpenIDUser function mock\n\nThese tests validate the fix from commit 5874ba29f that enables\n{{LIBRECHAT_OPENID_TOKEN}} template variable functionality.\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)\n\nCo-Authored-By: Claude \n\n* docs: Remove implementation documentation file\n\nThe PR description already contains all necessary implementation details.\nThis documentation file is redundant and was requested to be removed.\n\n* fix: skip s256 check\n\n* fix(openid): handle missing refresh token in Cognito token refresh response\n\nWhen OPENID_REUSE_TOKENS=true, the token refresh flow was failing because\nCognito (and most OAuth providers) don't return a new refresh token in the\nrefresh grant response - they only return new access and ID tokens.\n\nChanges:\n- Modified setOpenIDAuthTokens() to accept optional existingRefreshToken parameter\n- Updated validation to only require access_token (refresh_token now optional)\n- Added logic to reuse existing refresh token when not provided in tokenset\n- Updated refreshController to pass original refresh token as fallback\n- Added comments explaining standard OAuth 2.0 refresh token behavior\n\nThis fixes the \"Token is not present. User is not authenticated.\" error that\noccurred during silent token refresh with Cognito as the OpenID provider.\n\nFixes: Authentication loop with OPENID_REUSE_TOKENS=true and AWS Cognito\n\n* fix(openid): extract refresh token from cookies for template variable replacement\n\nWhen OPENID_REUSE_TOKENS=true, the openIdJwtStrategy populates user.federatedTokens\nto enable template variable replacement (e.g., {{LIBRECHAT_OPENID_ACCESS_TOKEN}}).\n\nHowever, the refresh_token field was incorrectly sourced from payload.refresh_token,\nwhich is always undefined because:\n1. JWTs don't contain refresh tokens in their payload\n2. The JWT itself IS the access token\n3. Refresh tokens are separate opaque tokens stored in HTTP-only cookies\n\nThis caused extractOpenIDTokenInfo() to receive incomplete federatedTokens,\nresulting in template variables remaining unreplaced in headers.\n\n**Root Cause:**\n- Line 90: `refresh_token: payload.refresh_token` (always undefined)\n- JWTs only contain access token data in their claims\n- Refresh tokens are separate, stored securely in cookies\n\n**Solution:**\n- Import `cookie` module to parse cookies from request\n- Extract refresh token from `refreshToken` cookie\n- Populate federatedTokens with both access token (JWT) and refresh token (from cookie)\n\n**Impact:**\n- Template variables like {{LIBRECHAT_OPENID_ACCESS_TOKEN}} now work correctly\n- Headers in librechat.yaml are properly replaced with actual tokens\n- MCP server authentication with federated tokens now functional\n\n**Technical Details:**\n- passReqToCallback=true in JWT strategy provides req object access\n- Refresh token extracted via cookies.parse(req.headers.cookie).refreshToken\n- Falls back gracefully if cookie header or refreshToken is missing\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)\n\nCo-Authored-By: Claude \n\n* fix: re-resolve headers on each request to pick up fresh federatedTokens\n\n- OpenAIClient now re-resolves headers in chatCompletion() before each API call\n- This ensures template variables like {{LIBRECHAT_OPENID_TOKEN}} are replaced\n with actual token values from req.user.federatedTokens\n- initialize.js now stores original template headers instead of pre-resolved ones\n- Fixes template variable replacement when OPENID_REUSE_TOKENS=true\n\nThe issue was that headers were only resolved once during client initialization,\nbefore openIdJwtStrategy had populated user.federatedTokens. Now headers are\nre-resolved on every request with the current user's fresh tokens.\n\n* debug: add logging to track header resolution in OpenAIClient\n\n* debug: log tokenset structure after refresh to diagnose missing access_token\n\n* fix: set federatedTokens on user object after OAuth refresh\n\n- After successful OAuth token refresh, the user object was not being\n updated with federatedTokens\n- This caused template variable resolution to fail on subsequent requests\n- Now sets user.federatedTokens with access_token, id_token, refresh_token\n and expires_at from the refreshed tokenset\n- Fixes template variables like {{LIBRECHAT_OPENID_TOKEN}} not being\n replaced after token refresh\n- Related to PR #9931 (OpenID federated token support)\n\n* fix(openid): pass user object through agent chain for template variable resolution\n\nRoot cause: buildAgentContext in agents/run.ts called resolveHeaders without\nthe user parameter, preventing OpenID federated token template variables from\nbeing resolved in agent runtime parameters.\n\nChanges:\n- packages/api/src/agents/run.ts: Add user parameter to createRun signature\n- packages/api/src/agents/run.ts: Pass user to resolveHeaders in buildAgentContext\n- api/server/controllers/agents/client.js: Pass user when calling createRun\n- api/server/services/Endpoints/bedrock/options.js: Add resolveHeaders call with debug logging\n- api/server/services/Endpoints/custom/initialize.js: Add debug logging\n- packages/api/src/utils/env.ts: Add comprehensive debug logging and stack traces\n- packages/api/src/utils/oidc.ts: Fix eslint errors (unused type, explicit any)\n\nThis ensures template variables like {{LIBRECHAT_OPENID_TOKEN}} and\n{{LIBRECHAT_USER_OPENIDID}} are properly resolved in both custom endpoint\nheaders and Bedrock AgentCore runtime parameters.\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)\n\nCo-Authored-By: Claude \n\n* refactor: remove debug logging from OpenID token template feature\n\nRemoved excessive debug logging that was added during development to make\nthe PR more suitable for upstream review:\n\n- Removed 7 debug statements from OpenAIClient.js\n- Removed all console.log statements from packages/api/src/utils/env.ts\n- Removed debug logging from bedrock/options.js\n- Removed debug logging from custom/initialize.js\n- Removed debug statement from AuthController.js\n\nThis reduces the changeset by ~50 lines while maintaining full functionality\nof the OpenID federated token template variable feature.\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)\n\nCo-Authored-By: Claude \n\n* test(openid): add comprehensive unit tests for template variable substitution\n\n- Add 34 unit tests for OIDC token utilities (oidc.spec.ts)\n- Test coverage for token extraction, validation, and placeholder processing\n- Integration tests for full OpenID token flow\n- All tests pass with comprehensive edge case coverage\n\n🤖 Generated with Claude Code\nCo-Authored-By: Claude \n\n* test: fix OpenID federated tokens test failures\n\n- Add serverMetadata() mock to openid-client mock configuration\n * Fixes TypeError in openIdJwtStrategy.js where serverMetadata() was being called\n * Mock now returns jwks_uri and end_session_endpoint as expected by the code\n\n- Update outdated initialize.spec.js test\n * Remove test expecting resolveHeaders call during initialization\n * Header resolution was refactored to be deferred until LLM request time\n * Update test to verify options are returned correctly with useLegacyContent flag\n\nFixes #9931 CI failures for backend unit tests\n\n🤖 Generated with [Claude Code](https://claude.com/claude-code)\n\nCo-Authored-By: Claude \n\n* chore: fix package-lock.json conflict\n\n* chore: sync package-log with upstream\n\n* chore: cleanup\n\n* fix: use createSafeUser\n\n* fix: fix createSafeUser signature\n\n* chore: remove comments\n\n* chore: purge comments\n\n* fix: update Jest testPathPattern to testPathPatterns for Jest 30+ compatibility\n\n---------\n\nCo-authored-by: Claude \nCo-authored-by: Denis Ramic \nCo-authored-by: kristjanaapro \n\nchore: import order and add back JSDoc for OpenID JWT callback\n","tree":"9eb3a8c74c976e9215748d12376aaa3842186a35"}}