Single sign-on with Okta
Gate treats your enterprise identity provider as core platform, not a bolt-on. Connecting Okta means your team signs in to Kilimanjaro with the credentials, MFA, and group memberships they already manage in Okta — enforced by Okta, honored by Gate. There's no extension to install and no separate identity silo to keep in sync; federation is native to the platform's Identity-Aware Kernel.
If you're consolidating SSO across your tooling, this is the on-ramp: point Okta at Gate once, and every Kilimanjaro project your org runs inherits the same corporate sign-in.
You configure this once at the org level, under Org scope → Identity provider. Because changing which identity providers your org trusts is an admin-impactful action, the change routes through Maker-Checker approval by default — one admin proposes it, a second approves.
1. Prerequisites
In the Okta admin console, create an application for Kilimanjaro:
- OIDC (recommended) — create an OIDC Web application. Note the client ID, client secret, and your Okta domain (
https://your-org.okta.com). - SAML — create a SAML 2.0 application. You'll need Okta's IdP SSO URL and the X.509 signing certificate.
You'll also need the role to manage org identity providers in Kilimanjaro (an org admin).
2. Create the identity-provider config
In Org scope → Identity provider, add a provider and choose Okta. Pick the protocol:
- OIDC — supply the issuer (
https://your-org.okta.com), client ID, and client secret. Gate resolves the authorize, token, and JWKS endpoints from Okta's/.well-known/openid-configuration, which it caches and refreshes automatically. - SAML — supply the IdP SSO URL and paste the X.509 signing certificate. The audience is Gate's entity ID, shown on the config screen.
Paste the client secret (or signing certificate) when you create the config. Gate stores it in the Vault and references it from then on — it's never displayed again, and rotating it is a Vault operation with a ledger entry, not an untracked edit.
3. Exchange metadata
Gate shows its service-provider (SAML) or relying-party (OIDC) metadata on the config screen — the ACS/redirect URL, entity ID, and the sign-in start URL. Paste these into your Okta application so Okta knows where to send authenticated users. For OIDC, the redirect URI is the one Gate displays; for SAML, paste Gate's ACS URL and entity ID into Okta's SP settings.
4. Map attributes and groups to roles
Gate maps Okta's token claims onto Kilimanjaro identity fields:
| Okta claim | Maps to |
|---|---|
email | |
given_name | first name |
family_name | last name |
groups | cached group membership (drives role assignment) |
Then map Okta groups to Kilimanjaro roles: an Okta group like kilimanjaro-admins can grant PROJECT_ADMIN, engineering can grant PROJECT_EDITOR, and so on. Group membership is re-evaluated on each sign-in, so moving someone between groups in Okta moves their access in Kilimanjaro.
5. Enable lifecycle sync (optional)
For proactive provisioning and deactivation — so a deactivated Okta user loses Kilimanjaro access without waiting for their next sign-in — enable SCIM. Okta pushes user create/update/deactivate events to Gate, which applies them to your roster in real time. Without SCIM, access still reconciles on next sign-in (group membership is read from the token); SCIM adds the push path for immediate deactivation.
6. Availability
Okta federation — OIDC, SAML, and SCIM lifecycle — is available on every plan.
7. Test and verify
Use the sign-in start URL from the config screen (or have a team member sign in through your org's normal Kilimanjaro entry point — Okta now appears as a sign-in option). On first sign-in, Gate provisions the user just-in-time from their Okta identity: no pre-creating accounts. Confirm the new user lands with the role their Okta group maps to, and check the audit log for the sign-in event.
See also
- Microsoft Entra ID SSO · Google Workspace SSO — the other workforce providers.
- Migrating from Okta — if you're replacing Okta as your auth vendor rather than federating it.
- Org scope — where org-level identity providers are configured.
- API → Auth — the federation substrate (OIDC / SAML / SCIM / JIT).