OIDC and OAuth 2.0
Authorization code with PKCE, refresh tokens, standard discovery and JWKS.
WhyCloud SSOGA
Put your apps behind WhyCloud SSO: people sign in once and reach every company tool. Run the same service on your own server, entirely inside your network.
| App | Type | Status |
|---|---|---|
| Grafana | Web | Active |
| GitLab | Web | Active |
| Mobile app | PKCE | Active |
| CI bot | Machine | Limited |
HOW IT WORKS
In the console → Identity → SSO follow the setup wizard, or create an on-premise server.
Give the app type and redirect; a client ID and secret are created.
Create users, assign groups or connect Google/Microsoft sign-in.
Enter the issuer and client ID in the app; single sign-on is ready.
Capabilities
Authorization code with PKCE, refresh tokens, standard discovery and JWKS.
Users, groups, disabling and password resets in the console.
Federate any OIDC identity provider, with email-domain restrictions.
A dedicated SSO server with its own database on your server, managed from the same console.
Per-tenant signing keys, short-lived tokens and sign-in events.
Successful and failed sign-ins with app and IP.
Users and groups are imported and kept current; passwords are checked at the directory.
Authenticator app with a QR code or an SMS code, for manual, synced and Google/Microsoft users.
USE CASES
One account for mail, Grafana, wiki and internal tools.
An SSO server in your own data center.
Standard OIDC sign-in for your app’s users.
DIRECTORY SYNC
Connect Active Directory, OpenLDAP, FreeIPA or Keycloak once. A test run shows sample users before saving; on schedule, new people are added, changes applied and removed or disabled accounts are disabled here too.
CLOUD OR ON-PREM
Cloud SSO is ready in seconds. When identity data must stay inside, install an “SSO server” on a connected machine; the console is the same and a switcher moves between deployments.
APPS
Choose the app type (web, SPA, mobile or machine), redirect URIs and allowed groups. Connection guides for Grafana, GitLab, Nextcloud and your own apps are on the app page.
FAQ
No. Only SSO directory users who signed in during the last 30 days are billed, hourly.
Yes. Add any OIDC provider; users are linked by verified email or created automatically.
Only the agent’s outbound connection for management; user sign-ins happen entirely on your server.
No. IAM decides what organization members can do in WhyCloud; SSO signs users into your apps. Both live under Identity in the console.
Create an account and connect your first server in under five minutes.