Describe the Bug
Dear Cursor Support Team,
I’m writing to report an issue with our SSO login configuration that appears to have been affected by a recent update (unspecified in the changelog). The current behavior is as follows:
- Session Validation vs. Actual Error:
• The Single Sign-On Session shows as successful, but the system returns an [internal] internal error.
• Additionally, the user receives a “Verify your email” verification code email, despite SSO being configured to bypass this step.
Domain Allowance Conflict:
• Under SSO configuration, the allowed domains are listed as: futunn.com, my.moomoo.com, and futuhk.com.
• However, clicking Test Sign-in triggers the error:
“Sign-in failed because the email domain futunn.com isn’t allowed. Your configuration does not support any allowed domains. Please contact Cursor support to add one or more allowed domains…
Steps to Reproduce
Requested Actions:
• Clarify if recent updates introduced changes to SSO validation logic.
• Investigate why configured domains are being rejected despite appearing in the settings.
• Confirm whether manual intervention is required from your side to re-enable domain allowances.
Please let us know if you need additional details or logs. We appreciate your prompt assistance to resolve this critical workflow disruption.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 0.48.8 (user setup)
VSCode Version: 1.96.2
Commit: 7801a556824585b7f2721900066bc87c4a09b740
Date: 2025-04-07T20:02:01.084Z
Electron: 34.3.4
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100