Google Workspace
1. Create an OAuth client
Section titled “1. Create an OAuth client”In the Google Cloud console, in a project owned by your Workspace organization:
- OAuth consent screen: user type Internal. That alone limits sign-in to your Workspace.
- Credentials → Create credentials → OAuth client ID, type Web application.
- Authorized redirect URI:
https://<your-bunker>/auth/callback - Copy the client ID and client secret.
2. Connect Bunker
Section titled “2. Connect Bunker”Admin → Sign-in → Google Workspace: paste the client ID and secret and enter your Workspace domain, for example example.com. You can list several domains, separated by commas.
The domain is required. Bunker refuses Google sign-in without one, and refuses public domains like gmail.com, outlook.com or icloud.com, so personal accounts can never get in.
What Bunker checks
Section titled “What Bunker checks”- The ID token’s
hd(hosted domain) claim must be one of your domains. When you have one domain, Bunker also sendshd=to Google so the account picker only offers work accounts. - PKCE, state and nonce on every sign-in.
Groups
Section titled “Groups”Google doesn’t put group memberships in its sign-in token. To share by group with Google sign-in, use groups on built-in accounts or share with people by email. Directory groups for Google are on the roadmap.