[Bug] OAuth SSO Disabled When Using Only NEXT_AUTH_SECRET

[nikkoxgonzales]

📦 Environment

Docker

📌 Version

1.1.4

💻 Operating System

Ubuntu

🌐 Browser

Edge

🐛 Bug Description

The application incorrectly disables Single Sign-On (SSO) functionality when only the NEXT_AUTH_SECRET environment variable is set. This occurs despite the deprecation message suggesting that setting NEXT_AUTH_SECRET should be sufficient for SSO to work.

📷 Recurrence Steps

1. Set up the application with only the NEXT_AUTH_SECRET environment variable.
2. Attempt to use OAuth SSO functionality.
3. Observe that SSO is disabled.

🚦 Expected Behavior

OAuth SSO should remain functional when NEXT_AUTH_SECRET is set, without requiring the deprecated ENABLE_OAUTH_SSO variable.

📝 Additional Information

• The application log shows the following deprecation message:
• "'ENABLE_OAUTH_SSO' is deprecated and will be removed in LobeChat 1.0. just set 'NEXT_AUTH_SECRET' enough',"
• This message implies that setting NEXT_AUTH_SECRET should be sufficient for SSO to work.
• The current behavior contradicts the deprecation message, as SSO is disabled when only NEXT_AUTH_SECRET is set.
• This issue may impact users who have removed the ENABLE_OAUTH_SSO variable based on the deprecation notice.

[lobehubbot]

👀 @nikkoxgonzales

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. Please make sure you have given us as much context as possible.\ 非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[cy948]

We already notice this problem and it will be fixed at #2935