Industry-standard single sign-on.
Integrate 1Auth over the standards you already know: OAuth 2.0, OpenID Connect, SAML 2.0 and SCIM. Point your app at the discovery document and ship.
- OIDC discovery & JWKS
- PKCE by default
- No proprietary SDK required
Everything you need to integrate
1Auth speaks the protocols your framework and IdP already support, so you wire it up the same way you would any OIDC or SAML provider.
OAuth 2.0 & OIDC
Authorization-code flow with PKCE, OIDC discovery, JWKS and standard ID tokens. Works with your existing OIDC client library.
SAML 2.0
SP- and IdP-initiated SSO for the apps that still need it. Download metadata, map attributes, done.
SCIM provisioning
Sync users and groups automatically with SCIM 2.0, so access follows your directory of record.
JWKS & token signing
Verify tokens against published JWKS. ES256 / RS256 signatures, rotated keys, no shared secrets to leak.
CLI & secrets
Pull secrets into your shell, scripts and CI without hardcoding them, authenticated by your own 1Auth session.
Audit & webhooks
Stream sign-in and membership events to your SIEM, and react to changes in your own systems.
One URL configures the rest
Fetch the discovery document and your client learns every endpoint, supported grant and signing key automatically. No copy-pasting URLs between dashboards.
/.well-known/openid-configuration- Authorization, token, userinfo and JWKS endpoints.
- Rotate keys without breaking clients.
POST /oauth/token grant_type=authorization_code code=bcx… code_verifier=dyS… → { "access_token": "eyJhbGciOiJF…", "id_token": "eyJraWQiOiJr…", "token_type": "Bearer", "expires_in": 3600 }
Standards on the outside, zero-knowledge on the inside. The integration is the boring part, which is how security should be.
Wire up single sign-on in an afternoon.
Create a client in the console, point your app at discovery, and your whole team signs in with one identity.