Troubleshooting common SSO issues
If you're experiencing trouble setting up or logging in with SSO (e.g., Okta, Azure, Google), here are the most frequent causes and how to fix them.
Check your user attribute mapping
StatusGator requires that your SAML assertion include a user attribute named email. This is critical for authentication.
If the email attribute is missing or misconfigured, you may see blank screens or "incorrect URL" errors during login.
For best results, also pass first_name and last_name so your users’ names display correctly in StatusGator.
Example: Okta attribute statements
Here’s how attributes should be configured in Okta:
| Name | Name Format | Value |
|---|---|---|
| first_name | Basic | user.FirstName |
| last_name | Basic | user.LastName |
| Basic | user.email |
Note: StatusGator does not rely on NameID or Subject. The email attribute is required.
Reconnect your SSO integration
Sometimes resetting the connection resolves issues. Disconnect SSO in your identity provider and reconnect it to StatusGator.
Verify you're still logged in to StatusGator
Expired sessions can interrupt SSO flows. Log out fully, clear cookies (or try incognito mode), and attempt SSO again.
Advanced troubleshooting
If problems persist, check for:
- Invalid or expired certificates
- Time synchronization issues between your system and IdP
- Network/firewall rules blocking SAML traffic
- Incorrect ACS URL, Entity ID, or metadata in your SSO config
Quick checklist
| Step | Action |
|---|---|
| 1 | Confirm email (and optionally first_name, last_name) are included in your SAML assertion |
| 2 | Disconnect and reconnect SSO |
| 3 | Log out and retry the login flow |
| 4 | Check SAML config (ACS URL, Entity ID, certificates) |
| 5 | Test in incognito or a different browser |