Skip to content
Esc
↑↓navigate↵open⌘Jpreview
On this page

Google Workspace OIDC

Connect Modem to Google Workspace with an OIDC client

This guide sets up Enterprise SSO with Google Workspace using OIDC. Read the overview first if you haven’t — it covers domain verification, roles, and the limitations that apply to every provider.

Google’s consoles are redesigned regularly, so treat the menu paths and field labels below as a guide; the exact labels move between releases.

Why OIDC and not SAML

Google Workspace can also act as a SAML identity provider, but Modem recommends OIDC here. Google’s OIDC sub claim is a stable, globally unique user id — Google’s discovery document advertises subject_types_supported: ["public"] — so there is no identifier to map and nothing to get wrong. With SAML you would have to choose and configure one yourself.

Prerequisites

  • Enterprise SSO enabled for your Modem organization, and the owner role in it
  • Access to the Google Cloud project attached to your Workspace, with permission to create OAuth credentials
  • Access to DNS for the email domain you are claiming

Setup

Copy Modem's redirect URI

In the Modem dashboard, go to Settings → Single Sign-On and choose OpenID Connect (OIDC). Keep the page open: it shows the redirect URI Google needs, which looks like https://app.modem.dev/api/auth/sso/callback/org-<id>.

Configure the OAuth consent screen

In the Google Cloud Console for the project attached to your Workspace, open APIs & Services → OAuth consent screen and set the user type to Internal, so only users in your Workspace can use the app.

Create the OAuth client

Go to APIs & Services → Credentials → Create credentials → OAuth client ID, and choose the application type Web application. Give it a name such as Modem.

Under Authorized redirect URIs, add the redirect URI from Modem exactly as the page shows it.

Copy the client id and secret

Create the client and copy the Client ID and Client secret. The secret is shown once — if you lose it, create a new one rather than guessing.

Register Google in Modem

Back on Modem’s Single Sign-On page, enter:

Field Value
Issuer URL https://accounts.google.com
Client ID The client id from step 4
Client secret The client secret from step 4

Modem reads Google’s discovery document from the issuer to fill in the authorization, token, and JWKS endpoints, and always uses PKCE. Enter the email domain you are claiming at the same time.

Verify your email domain

Publish the DNS TXT record Modem shows on the SSO settings page and click verify. Sign-in is refused until this succeeds — see Domain verification.

Scopes

Modem requests these three scopes and no others:

Scope Why
openid Issues the id token carrying the sub claim
email The user’s email address
profile The user’s name

The identity Modem stores

Modem stores the OIDC sub claim as the account identity. There is nothing to configure — Google’s sub is already a stable, globally unique id for the user, and it does not change when someone’s email address does.

Teams that already sign in with Google

Most teams arriving here have been using the Continue with Google button, and that is the easy case: those people keep the same Modem account, the same organization membership, the same role, and everything already in it.

The first time each of them signs in through Continue with SSO, Modem moves them onto single sign-on automatically. There is nothing for you to do — no accounts to re-invite, nothing for them to disconnect first — and your team can move across one at a time, at whatever pace suits your rollout.

Moving across is the point, and it settles per person: from then on, single sign-on is simply how that person signs in, and Continue with Google no longer signs them in. That does not wait on anything you switch on — each person’s own first single sign-on is what moves them.

Restricting who can sign in

Because the consent screen is Internal, only users in your Workspace can complete the flow.

Modem does not refuse a Workspace user whose address is off the verified domain: they join as a member, and Modem never marks that address as verified.

If you need a narrower set of people, restrict access to the app from the Google Workspace Admin console, or connect Directory Sync so that only people your directory lists as active can sign in.

Testing the sign-in

Sign out of Modem, or use a private window, then:

  1. Go to https://app.modem.dev
  2. Click Continue with SSO
  3. Enter your work email address, or your Modem organization slug
  4. Complete the Google prompt

You should land back in Modem signed in. A user who has never used Modem before gets an account and joins as a member, unless they had a pending invitation carrying a different role.

Troubleshooting

Google reports redirect_uri_mismatch

The redirect URI registered on the OAuth client does not match Modem’s exactly. Copy it again from the SSO settings page — it ends in your organization’s provider id, org-<id>, and Google compares the whole string character for character, including the scheme and any trailing characters.

Single sign-on is not finished being set up

The domain has not been verified yet. Publish the DNS TXT record from the SSO settings page and click verify. DNS can take minutes to hours to propagate; retrying is safe.

No single sign-on provider for that address

The address typed at Continue with SSO is not on the verified domain. Personal Google accounts, and Workspace users on a secondary domain you have not verified, will not resolve to your provider.

Your account is already connected another way

A member who previously signed in with Continue with Google is normally moved onto single sign-on automatically, but a few cases are held back deliberately. The person cannot clear this themselves and does not need to change anything. Contact support@modem.ai with the error code shown on their screen, account_provider_conflict, and we will finish the move.

Google says the app is blocked or the user is not allowed

The consent screen is Internal, so users outside your Workspace are refused by Google before the flow reaches Modem. Check the user’s account, and any app access restrictions set in the Google Workspace Admin console.

The client secret was rotated

Modem holds the secret it was given, so rotating it in Google Cloud breaks the exchange. Enter the new secret on the Modem SSO settings page.

Was this page helpful?