Remove SSO configuration for organization
sso
Remove SSO configuration for organization
Remove SSO configuration for the current user’s organization.
Disables the SSO configuration by setting is_active=False. This is a soft delete that preserves the configuration for potential future reactivation.
Context:
- Soft delete (sets is_active=False, preserves data)
- Users will fall back to password authentication
- Configuration can be reactivated by creating a new SSO config
- Does not delete the Supabase SSO provider
Impact:
- Immediate: Users can no longer authenticate via SSO
- Existing sessions may remain active until expiration
- Users must use password authentication
- Organization admins can recreate SSO configuration
Security Considerations:
- Disabling SSO immediately affects all users in configured domains
- Ensure alternative authentication methods are available
- Consider communication to affected users before disabling
Use Cases:
- Temporary SSO maintenance or troubleshooting
- Migrating to a different SSO provider
- Emergency access restoration via password auth
- Decommissioning SSO integration
Related Endpoints:
- POST /auth/sso - Create new SSO configuration
- GET /auth/sso - Check current configuration status
DELETE
Remove SSO configuration for organization
Authorizations
API key authentication. Include your API key in the X-API-Key header as: X-API-Key YOUR_API_KEY
Example:
JWT Bearer token authentication. Include your access token in the Authorization header as: Bearer YOUR_ACCESS_TOKEN
Example:
Response
SSO configuration disabled successfully