WandoDocs
Home
Sign in
Overview

Single sign-on

  • Microsoft Entra ID
  • Google Workspace
  • OktaOkta
  • Auth0
  • Generic OIDC

SCIM provisioning

  • Microsoft Entra ID
  • OktaOkta
  • Auth0

More provider guides are added as we ship them. Need one we don't cover? hej@wando.app

Browse all guides
Overview

Single sign-on

  • Microsoft Entra ID
  • Google Workspace
  • OktaOkta
  • Auth0
  • Generic OIDC

SCIM provisioning

  • Microsoft Entra ID
  • OktaOkta
  • Auth0
© 2026 WandoDocs are continuously updated as the product ships.
Wando docs

Setup and configuration guides

Short, opinionated walkthroughs for plugging Wando into the identity providers your IT team already runs. Every guide ends with the exact values to paste into the Wando admin.

Single sign-on

Wire up an identity provider

OpenID Connect against the four IdPs Wando has first-class support for, plus a generic OIDC path for everything else.

  • Microsoft Entra ID

    ~10 min

    Set up OpenID Connect sign-in against Microsoft Entra ID (formerly Azure AD). Once configured, members whose email matches your tenant's domain land on the Microsoft sign-in flow automatically.

  • Google Workspace

    ~10 min

    Sign in with Google accounts from your Workspace domain. Configure an OAuth 2.0 client in Google Cloud Console and Wando handles the rest via standard OIDC discovery.

  • Okta

    Okta

    ~10 min

    Configure OpenID Connect sign-in against Okta. Create a Web Application integration, point it at Wando's callback URL, then assign the users or groups who should be able to sign in.

  • Auth0

    ~8 min

    Use Auth0 as the identity provider for an organisation. You'll register a Regular Web Application, set the callback URL to Wando, and copy the tenant credentials over.

  • Generic OIDC

    ~10 min

    For any OpenID Connect 1.0 provider not covered by a dedicated guide — Keycloak, Authelia, Ping Identity, Curity, JumpCloud, OneLogin, and others. The steps below are the universal shape; consult your provider's docs for the exact menu labels.

SCIM 2.0 provisioning

Sync members from your directory

Push users and groups from your IdP so Wando members and roles stay in lockstep with your source of truth.

  • Microsoft Entra ID

    ~15 min

    Provision members from Entra ID into Wando automatically. Entra pushes user and group changes to Wando's SCIM 2.0 endpoint over a bearer token, and Wando maps groups to roles.

  • Okta

    Okta

    ~15 min

    Provision members from Okta into Wando over SCIM 2.0. Okta pushes user lifecycle events (create / update / deactivate) and group assignments to Wando's SCIM endpoint, and Wando maps groups to roles.

  • Auth0

    ~5 min

    Auth0 does not push SCIM to downstream applications — its SCIM 2.0 support is inbound only (a way for an upstream IdP to provision users *into* Auth0). Pick one of the options below depending on where your user directory actually lives.

Missing a provider?

The Generic OIDC guide covers any standards-compliant IdP. If you want a dedicated walkthrough for your provider, get in touch at hej@wando.app.