website/src/app/kb/authenticate/google/readme.mdx
import Alert from "@/components/DocsAlert"; import PlanBadge from "@/components/PlanBadge"; import SupportOptions from "@/components/SupportOptions";
<PlanBadge plans={["starter", "team", "enterprise"]}>
Firezone supports authenticating users with Google using Firezone's public OAuth client. This works with both personal Google accounts (Gmail) and Google Workspace accounts. Only one Google provider can be configured per Firezone account.
<Alert color="info"> Looking for directory sync? See the [Google directory sync guide](/kb/directory-sync/google) to automatically provision users and groups from Google Workspace. </Alert>To enable Google authentication:
Settings -> Authentication in your admin portal.Users will now see this provider as an option on the Firezone sign-in page.
Firezone uses a public OAuth client to authenticate users with Google. When a user signs in:
iss and sub claims from Google. For
users provisioned via directory sync, this
identity already exists. For manually created users, Firezone matches by
email on first sign-in and saves the Google identity for subsequent sign-ins.No Google Cloud project or OAuth client setup is required on your end.
Firezone requests the following scopes from Google:
openid — Required for authenticationemail — Used to match users on first sign-inprofile — Used for the user's display nameFirezone does not access your contacts, calendar, or any other Google data.
The Google provider supports:
@gmail.com or custom
domain linked to a personal Google accountUsers must exist in Firezone before they can sign in with Google. You can:
If a user sees a "user not found" or similar error when signing in, it means no matching user exists in Firezone. The user must be created manually or provisioned via directory sync before they can sign in.
Google Workspace admins can restrict which third-party apps users are allowed to sign into. If a user sees "Access blocked" or "This app is blocked", the Workspace admin will need to allow Firezone in the Google Admin console under Security → API controls → App access control.
Users can revoke Firezone's access to their Google account from their Google Account security settings. Revoking access does not delete the user from Firezone or end their active sessions, but they will need to re-authorize on their next sign-in.
<SupportOptions />