Skip to main content
Available on the Enterprise plan. Only organization owners can configure identity providers.

Overview

SSO lets your team log in to Wave Connect through your organization’s identity provider (IdP). Instead of managing a separate Wave Connect password, users authenticate with the same credentials they use for everything else. Wave Connect supports SAML 2.0 and OpenID Connect (OIDC) and works with any standards-compliant identity provider, including Okta, Microsoft Entra ID, Google Workspace, OneLogin, JumpCloud, and Ping Identity. You configure it yourself in Settings → Security → Identity providers.

How it works

There are two login paths depending on whether the user already has a Wave Connect account.
Users can also initiate SSO directly with this URL: https://app.wavecnct.com/auth/sso?org=YOUR_ORG_SLUG. Replace YOUR_ORG_SLUG with your Organization Username, found in your organization settings. The same URL is shown as the Start URL when you configure SAML.
No account yet: The user clicks Continue with SSO on the Wave Connect login page and enters your organization’s username in the Org Username field. Wave Connect redirects them to your identity provider, they authenticate, and their account is created automatically on first login. The email asserted by your IdP must be on one of your organization’s verified domains, otherwise the login is refused. Existing account with SSO enforced: The user enters their email as usual. Wave Connect detects that SSO is enforced for their organization and redirects them to your identity provider to authenticate.
We recommend provisioning users in advance with SCIM so accounts are ready, and assigned to the right team, before your team logs in for the first time. If you use Microsoft Entra ID, see the Entra ID guide for setting up both on the same enterprise application.
Accounts created by SSO read the standard claims for first name, last name and email. Microsoft Entra ID’s default name claim, which contains the email, is accepted as the email. Name claims can also carry a phone, city, job title, language and role (USER or ADMIN).

Setup

SAML

1

Open Identity providers

Go to Settings → Security → Identity providers and click Configure next to SAML.
2

Copy Wave connect's details into your IdP

The first step of the Configure SAML modal shows the values your IdP needs:
  • Entity ID: wave-connect
  • Assertion Consumer Service (ACS) URL: https://app.wavecnct.com/__/auth/handler
  • Start URL: https://app.wavecnct.com/auth/sso?org=YOUR_ORG_SLUG
In your identity provider, create a SAML 2.0 application for Wave Connect with these values. Set the Name ID format to email address. Click Next.
3

Enter your IdP's details

From your IdP’s SAML application, copy:
  • Entity Id: the identifier URI of your identity provider
  • SSO Url: the URL of your identity provider’s sign-in page
  • x509 Certificates: the signing certificate in PEM format, from -----BEGIN CERTIFICATE----- to -----END CERTIFICATE-----
4

Save and test

Leave Enforce SSO login for your users off, click Save, and test with one user through the Start URL before enforcing SSO for everyone.
Only one identity provider can be configured at a time. To switch from SAML to OIDC, or to a different IdP, remove the current provider first. Removing it sends all users back to email or phone code sign-in.

OIDC

1

Create an OIDC application in your IdP

Register a web application for Wave Connect with the redirect URI https://app.wavecnct.com/__/auth/handler. Set the client authentication type to Client Secret Basic.
2

Open Identity providers

Go to Settings → Security → Identity providers and click Configure next to OpenID Connect.
3

Enter your IdP's details

In the Configure OIDC modal, fill in Client Id, Client Secret and Issuer (your IdP’s issuer URL). Keep Reponse Type on Code. The implicit flow is available but not recommended.
4

Save and test

Leave Enforce SSO login for your users off, click Save, and test with one user before enforcing SSO for everyone.

Enforcing SSO

Once SSO works, you can require it so all users must log in through your identity provider. This disables email and phone code login for your organization. Open Settings → Security → Identity providers, edit your provider, turn on Enforce SSO login for your users, and click Update. Existing users who try to log in with their email are redirected to your identity provider.
Make sure the owner enforcing SSO can log in through the IdP first. Once enforced, every member of the organization, including owners, must authenticate through it.