Describe the Bug
We are currently locked out of our administrator account for the application. The lockout was triggered after we had to recreate our SAML SSO configuration in our Identity Provider (Google Workspace). The application’s login process is now forcing us into a broken SSO loop, preventing us from logging in to fix the configuration.
Steps to Reproduce
Background and Sequence of Events:
Initial State: SAML Single Sign-On via Google Workspace was working correctly for all our users.
Accidental Deletion: The SAML app configuration was accidentally deleted and then immediately recreated within our Google Workspace admin console.
New Certificate: This action automatically generated a new x.509 signing certificate on Google’s side. The application, however, is still configured to expect the old, now-invalid certificate.
Resulting Lockout: This certificate mismatch now causes all SSO login attempts to fail with a 403 error after successful authentication with Google.
Expected Behavior
The core issue is that we cannot bypass the broken SSO flow to fix it. The login should provide a bypass or fallback Login URL.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.1.7 (Universal)
VSCode Version: 1.96.2
Commit: 7111807980fa9c93aedd455ffa44b682c0dc1350
Date: 2025-07-01T07:26:06.233Z (2 days ago)
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0