Cyberia Auth Management
06 / Federation
Third-Party SSO
Google, Microsoft, Apple, Facebook, X and more — per application.
In this feature
- Google, Microsoft, Apple, Facebook, X, GitHub, GitLab, Discord, Slack, Twitch
- Providers enabled and disabled per application
- Provider credentials stored server side, never in the client bundle
- Account linking when a user arrives through a second provider
- Status column showing exactly what is live right now
// In the console
What it looks like
Enable social and enterprise identity providers per application from a catalog, with credentials stored server side and providers toggled without a redeploy.
Third-Party SSO
Third-Party SSO — detail
Coverage
Consumer and workplace identity
Microsoft and Google cover the enterprise buyer; Apple, Facebook and X cover consumer products; GitHub, GitLab, Slack and Discord cover developer and community tools.
Control
Per-app provider sets
An internal admin can accept Microsoft only while the public product accepts everything. Providers are attached to the application, not the whole server.
Safety
Secrets stay on the server
Client identifiers and secrets live in the auth server. The React component only ever learns which providers to render.
Included out of the box
Google, Microsoft, Apple, Facebook, X, GitHub, GitLab, Discord, Slack, Twitch
Providers enabled and disabled per application
Provider credentials stored server side, never in the client bundle
Account linking when a user arrives through a second provider
Status column showing exactly what is live right now