- 1.Ensure you're logged into your SSO provider (Google, Microsoft, etc.) in the same browser
- 2.Clear your browser cookies and cache, then try the SSO login again
- 3.Check if third-party cookies are enabled in your browser - SSO requires them to work
- 4.Disable browser extensions that block trackers or cookies (Privacy Badger, uBlock Origin)
- 5.Try the SSO login in incognito/private browsing mode to test without extensions
- 6.For organization SSO: Contact your IT administrator to verify your account has Wubble access
- 7.Verify your SSO provider account email matches the email you used to register with Wubble
- 8.Try a different browser - Chrome and Firefox have the best SSO compatibility
- 9.Check if your organization's SSO has granted permission to Wubble - you may need admin approval
- 10.If SSO continues to fail, try resetting your Wubble password and using email/password login instead
If Single Sign-On (SSO) authentication is failing when you try to log in with Google, Microsoft, GitHub, or your organization's SSO provider, these troubleshooting steps will help resolve the connection issue.