Hi team,
We are experiencing a critical SSO login issue affecting the entire Loomi Business Team (34+ users). I’m the admin ([email protected]), and I’ve completely lost access to my admin account. None of our users are able to log in via Google SSO, making it impossible for us to use Cursor.
This started after our initial trial team (connected to our domain) was deleted. We created a new team using the same domain and followed the setup tutorial again. However, during login attempts, the redirection seems to use the old Entity ID from the deleted team instead of the new configuration.
Despite configuring Google Workspace to allow all users from the domain, and confirming SAML settings (issuer tag, etc.), the error persists. I’ve already contacted Google Support and validated our setup. The issue clearly occurs after redirecting from Cursor, not from Google.
I’ve also opened multiple support tickets and email threads, but haven’t received any response or resolution. We’ve asked repeatedly for the SSO to be disabled temporarily so we can access the platform and fix the configuration — but nothing has been done.
This is completely blocking our access, and we’re now considering canceling our subscription and requesting a refund if we don’t receive urgent support.
Steps to Reproduce
- Configure SSO with Google Workspace for a new Cursor team using the same domain as a previously deleted team.
- Set Google Workspace to allow login for everyone.
- Attempt to log in with any user from the workspace.
- Error page is shown after redirection from Cursor — referencing old Entity ID.
Screenshots
The full configuration image contains sensitive information and were provided in the support tickets.
Environment
- Access via: Web browser
- OS: Not applicable (browser-based)
- Cursor version: Not applicable (admin panel)
Impact
This issue completely prevents use of Cursor for the entire team. We are unable to access any features or the admin panel.