Internal Server error on openid callback

[RicardoOM-AC]

What happened?

Using the Social openid, azure account, when selected the account, it return "An unknown error ocurred" and the console shows the 500 error

Looks like this error is because secrets are not correctly set:

"error_description":"AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app 'XXXXX8-3179-4ae7-bafd-26f7XXXXXXX'

I expected a managed error, not just "An unknown error ocurred"

No big deal, is a small adjustment.

Version Information

ghcr.io/danny-avila/librechat-dev-api latest c02b71a0c7c8 19 hours ago 1.26GB
ghcr.io/danny-avila/librechat-rag-api-dev-lite latest 8858d2bd9ff5 3 weeks ago 1.48GB

Steps to Reproduce

1. Followed: https://www.librechat.ai/docs/configuration/authentication/OAuth2-OIDC/azure
2. Try to login using Social Button
3. Select azure account
4. Boom.

What browsers are you seeing the problem on?

Chrome

Relevant log output

{
  "cause": {
    "correlation_id": "949b1a14-eb60-4daa-ab69-ade704808f26",
    "error": "invalid_client",
    "error_codes": [
      7000215
    ],
    "error_description": "AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app '02XXXXXX28-3179-4ae7-bafd-2XXXXXXXXX'. Trace ID: 18bf6172-d55f-4477-a6ee-68794d917e00 Correlation ID: 949b1a14-eb60-4daa-ab69-ade704808f26 Timestamp: 2025-08-05 16:59:32Z",
    "error_uri": "https://login.microsoftonline.com/error?code=7000215",
    "timestamp": "2025-08-05 16:59:32Z",
    "trace_id": "18bf6172-d55f-4477-a6ee-68794d917e00"
  },
  "code": "OAUTH_RESPONSE_BODY_ERROR",
  "error": "invalid_client",
  "error_description": "AADSTS7000215: Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app '024e2b28-3179-4ae7-bafd-26f75e2d1350'. Trace ID: 18bf6172-d55f-4477-a6ee-68794d917e00 Correlation ID: 949b1a14-eb60-4daa-ab69-ade704808f26 Timestamp: 2025-08-05 16:59:32Z",
  "level": "error",
  "message": "ErrorController => error server responded with an error in the response body",
  "name": "ResponseBodyError",
  "stack": "ResponseBodyError: server responded with an error in the response body\n    at checkOAuthBodyError (file:///app/node_modules/oauth4webapi/build/index.js:889:19)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async processGenericAccessTokenResponse (file:///app/node_modules/oauth4webapi/build/index.js:1165:5)\n    at async processAuthorizationCodeOAuth2Response (file:///app/node_modules/oauth4webapi/build/index.js:1397:20)\n    at async Module.authorizationCodeGrant (file:///app/api/node_modules/openid-client/build/index.js:942:18)\n    at async CustomOpenIDStrategy.authorizationCodeGrant (file:///app/api/node_modules/openid-client/build/passport.js:135:28)",
  "status": 401
}

Screenshots

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

can you screenshot where you are seeing the "An unknown error ocurred" message? Just to take a quick look how we can improve the UX here

[RicardoOM-AC]

[danny-avila]

You will be acting as {{char}} in a dynamic roleplaying session between Human and Assistant. When I write BEGIN DIALOGUE you will enter this role and continue the roleplay. Please follow these important rules:

- Assistant will assume the role of {{char}} and write {{char}}’s next reply in a fictional roleplay between {{char}} and {{user}}. - Write short replies that are 3 to 4 paragraphs in length. - Always include {{char}}’s actions and dialogue in each reply. - Never write the actions or dialogue of {{user}}. - Write in a [whimsical] narrative style like that of [Tove Jansson.] - Keep the tone of the story [quirky] and [lighthearted.] - Be detailed, creative, and humorous. - Assistant will reply with "Understood" after analyzing these instructions.

BEGIN DIALOGUE