How it works
- One SSO provider per organization. The provider is tied to your organization’s slug, so the sign-in URL you give your IdP is unique to that organization.
- Your IdP handles authentication, LocalOps handles access. SSO doesn’t add anyone to your organization. People still join through an invitation, and their organization and project roles are managed in LocalOps. IdP groups and roles aren’t read, and there’s no SCIM or just-in-time provisioning.
- SSO is enforced once your domain is verified. After you verify the email domain (for example
acme.com), everyone in the organization - Owners and Admins included - has to sign in through the IdP to open the organization in the console. - SSO sits on top of a normal LocalOps sign-in. People sign in to LocalOps as usual (email code, Google, GitHub or GitLab). When they pick an SSO-enabled organization, they’re sent to your IdP and then brought back. Organizations that need SSO have an SSO badge on the organization picker.
- IdP-initiated sign-in works too. Clicking the LocalOps tile in Okta, Microsoft My Apps or Google signs the person in to LocalOps and verifies SSO in one step.
Set up SSO
Open Security settings
Copy the service provider details
Create the SAML app in your IdP
Paste the IdP details into LocalOps
- Domain - your company email domain, for example
acme.com - Identity Provider Single Sign-On URL - the IdP’s SAML sign-in URL
- Identity Provider Issuer - the IdP’s entity ID
- X.509 Certificate - the IdP’s signing certificate, including the
-----BEGIN CERTIFICATE-----and-----END CERTIFICATE-----lines
Verify your domain
Microsoft Entra ID
Create an enterprise application
LocalOps, choose the non-gallery option and click Create.Configure SAML
Check the user identifier
user.userprincipalname. If your users’
UPNs aren’t their email addresses (for example jane@acme.onmicrosoft.com instead of jane@acme.com), change it to
user.mail with the Email address format. LocalOps signs users in by this value, so it has to match the email they
were invited with.Copy the IdP details
Assign users
Okta
Create an app integration
LocalOps and click Next.Configure SAML
email →
user.email, givenName → user.firstName and surname → user.lastName so names show up properly in LocalOps.
Click Next, then Finish.Copy the IdP details
Assign users
Google Workspace
Add a custom SAML app
LocalOps and click Continue.Copy the IdP details
Configure the service provider
Turn the app on
Other SAML identity providers
Any IdP that supports SAML 2.0 works - OneLogin, JumpCloud, Ping Identity, Keycloak, AD FS and so on. Create a SAML app and map these fields:email attribute if your IdP sends one, and from the Name ID otherwise. It reads the
name from givenName and surname, or displayName.
Onboard users
Give them access in your IdP
Invite them to LocalOps
They accept and sign in
Offboard users
Do both:- Remove them in LocalOps. In Settings → Members, remove the member. This cuts off access right away - in the console, the CLI and the API.
- Remove them in your IdP. Unassign or deactivate them so they can’t sign in through SSO again.
Session duration
CLI and API access
SSO is checked for browser sessions in the console. The CLI signs in withops login, which opens the
browser to approve the device and then uses its own token. That token isn’t checked against your IdP:
ops loginand CLI commands keep working for members of an SSO-enabled organization without a trip through the IdP.- A CLI token lasts as long as a LocalOps session - up to 7 days. Run
ops loginagain after it expires. - Organization and project roles still apply, and removing a user from the organization stops their CLI access right away. This is why offboarding needs both steps.
Microsoft Entra ID and Okta FAQ
Do we need one Entra (or Okta) app per LocalOps organization?
Do we need one Entra (or Okta) app per LocalOps organization?
Should members be assigned to the app, or should it be open to everyone and access managed in LocalOps?
Should members be assigned to the app, or should it be open to everyone and access managed in LocalOps?
- Assign users or groups (recommended). In Entra, set Properties → Assignment required? to Yes and assign users or groups. Okta always requires assignment. This gives you two gates, and unassigning a user in the IdP stops them from signing in through SSO.
- Open to everyone in the directory. In Entra, set Assignment required? to No. In Okta, assign the Everyone group. Anyone in your directory can authenticate, but only invited members get into the LocalOps organization. Uninvited people who sign in see no organization.
Can we map Entra or Okta groups to LocalOps roles?
Can we map Entra or Okta groups to LocalOps roles?
Edit or remove the provider
In Settings → Security, use the pencil icon on the provider to update the IdP sign-in URL, issuer or certificate, and the trash icon to remove it. Removing the provider (Remove SSO provider) turns SSO off for the organization, and people go back to signing in with just their LocalOps sign-in method.Gotchas
- Emails must match. LocalOps finds the user by the email your IdP sends. If a user joined LocalOps as
jane@gmail.combut your IdP sendsjane@acme.com, they’re signed in as a different user who isn’t in your organization. Invite people with their IdP email. - Everyone needs an email on the verified domain. A member whose LocalOps email isn’t on your SSO domain (a contractor’s personal address, for example) can’t complete SSO and won’t be able to open the organization in the console. Give them an account in your IdP and invite that email instead.
- Only the Admin who added the provider can verify the domain. If they’ve left, remove the provider and add it again.
- Nothing is enforced until the domain is verified. An Unverified provider doesn’t affect sign-in.
- Owners and Admins aren’t exempt. If your IdP certificate expires or the IdP details change, nobody can open the organization in the console. Rotate certificates ahead of time. If you’re locked out, contact support@localops.co.
- Multiple SSO organizations. Each SSO sign-in starts a new LocalOps session. If you belong to more than one SSO-enabled organization, switching between them sends you through the IdP again.
- Changes take up to 2 minutes. Turning SSO on or off can take up to 2 minutes to apply everywhere.
- Clock skew. SAML responses are accepted with up to 5 minutes of clock difference. A replayed response is rejected.