Implementing Google Workspace SSO Configuration
Overview
Single Sign-On (SSO) for Google Workspace allows organizations to authenticate users through their existing identity provider (IdP) such as Okta, Azure AD (Microsoft Entra ID), or ADFS, rather than managing separate Google passwords. This is implemented using SAML 2.0 protocol where Google Workspace acts as the Service Provider (SP) and the organization's IdP handles authentication. SSO centralizes credential management, enforces MFA policies at the IdP, and enables immediate access revocation when users leave the organization.
When to Use
- When deploying or configuring implementing google workspace sso configuration capabilities in your environment
- When establishing security controls aligned to compliance requirements
- When building or improving security architecture for this domain
- When conducting security assessments that require this implementation
Prerequisites
- Google Workspace Business, Enterprise, or Education edition
- Super Admin access to Google Admin Console
- Identity Provider with SAML 2.0 support (Okta, Azure AD, ADFS, Ping Identity)
- IdP signing certificate (X.509 PEM format, RSA or DSA)
- DNS verification for the Google Workspace domain
Core Concepts
SAML 2.0 SSO Flow
User navigates to Google Workspace app (Gmail, Drive, etc.)
│
├── Google checks: Is SSO configured for this domain?
│
├── YES → Redirect user to IdP Sign-In Page URL
│ (SAML AuthnRequest sent via browser redirect)
│
├── User authenticates at IdP (credentials + MFA)
│
├── IdP generates SAML Response with signed assertion
│
├── Browser POSTs SAML Response to Google ACS URL:
│ https://www.google.com/a/{domain}/acs
│
├── Google validates SAML signature against uploaded certificate
│
└── User is granted access to Google Workspace
Key SAML Parameters
| Parameter |
Value |
| ACS URL |
https://www.google.com/a/{your-domain}/acs |
| Entity ID |
google.com/a/{your-domain} or google.com |
| NameID Format |
urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress |
| NameID Value |
User's primary Google Workspace email |
| Binding |
HTTP-POST (for ACS), HTTP-Redirect (for SSO URL) |
Workflow
Step 1: Prepare the Identity Provider
For Okta:
- Navigate to Applications > Add Application > Search "Google Workspace"
- Configure the Google Workspace app with your domain
- Assign users/groups to the application
- Download the IdP metadata or note: SSO URL, Entity ID, Certificate
For Azure AD (Microsoft Entra ID):
- Navigate to Enterprise Applications > New Application > Google Cloud/Workspace
- Configure Single sign-on > SAML
- Set Basic SAML Configuration:
- Identifier (Entity ID):
google.com
- Reply URL (ACS):
https://www.google.com/a/{your-domain}/acs
- Sign on URL:
https://www.google.com/a/{your-domain}/ServiceLogin
- Download Federation Metadata XML or Certificate (Base64)
For ADFS:
- Add Relying Party Trust using federation metadata
- Configure claim rules to pass NameID as email address
- Export the token-signing certificate
Step 2: Configure Google Workspace SSO
- Sign in to Google Admin Console (admin.google.com) as Super Admin
- Navigate to Security > Authentication > SSO with third-party IdP
- Click "Add SSO profile" or configure the default profile
Third-Party SSO Profile Settings:
| Setting |
Value |
| Set up SSO with third-party IdP |
Enabled |
| Sign-in page URL |
IdP's SAML SSO endpoint (e.g., https://idp.example.com/sso/saml) |
| Sign-out page URL |
IdP's logout URL (e.g., https://idp.example.com/slo) |
| Change password URL |
IdP's password change URL |
| Verification certificate |
Upload IdP's X.509 signing certificate |
| Use a domain-specific issuer |
Enabled (uses google.com/a/{domain} as entity ID) |
Step 3: Assign SSO Profile to Users
SSO profiles can be applied at different scopes:
Organization-wide (all users)
│
├── Org Unit level (specific departments)
│ ├── Engineering OU → SSO via Okta
│ ├── Marketing OU → SSO via Azure AD
│ └── Contractors OU → SSO via specific IdP
│
└── Group level (specific security groups)
└── VPN Users → SSO with additional MFA
- Navigate to Security > Authentication > SSO with third-party IdP
- Select the SSO profile to assign
- Choose organizational units or groups
- Save and wait for propagation (up to 24 hours, typically minutes)
Step 4: Configure Network Masks (Optional)
Network masks control when SSO is enforced based on the user's IP:
- If the user's IP matches a network mask, they use Google's sign-in page
- If the user's IP does NOT match, they are redirected to the IdP
This is useful for allowing direct Google login from corporate network while enforcing SSO for external access.
Step 5: Test SSO
- Open an incognito browser window
- Navigate to
https://mail.google.com/a/{your-domain}
- Verify redirect to IdP sign-in page
- Authenticate at the IdP
- Verify successful redirect back to Google Workspace
- Test sign-out flow redirects to IdP logout page
- Test with user not assigned in IdP (should fail)
Validation Checklist
References
1---2name: implementing-google-workspace-sso-configuration3description: Configures SAML 2.0 single sign-on for Google Workspace against a third-party4 identity provider (Okta, Azure AD/Entra ID, ADFS), with Workspace as the Service5 Provider, to centralize authentication and enable immediate access revocation.6 Use when setting up or troubleshooting Google Workspace SSO/SAML federation or7 migrating from native Google passwords to an external IdP.8domain: cybersecurity9subdomain: identity-access-management10tags:11- google-workspace12- sso13- saml14- identity-provider15- authentication16- federation17version: '1.0'18author: mahipal19license: Apache-2.020nist_csf:21- PR.AA-0122- PR.AA-0223- PR.AA-0524- PR.AA-0625mitre_attack:26- T107827- T111028- T155629- T109830mitre_f3:31 version: '1.1'32 tactics:33 - initial-access34 - positioning35 techniques:36 - id: T111037 name: Brute Force38 tactic: initial-access39 source: attack40 - id: T1110.00441 name: 'Brute Force: Credential Stuffing'42 tactic: initial-access43 source: attack44 - id: T153945 name: Steal Web Session Cookie46 tactic: positioning47 source: attack48 - id: F100449 name: Access with Stolen Session Cookie50 tactic: initial-access51 source: f352 - id: F100653 name: Account Takeover54 tactic: initial-access55 source: f356metadata:57 source: https://skillmd.com/skills/26zl/implementing-google-workspace-sso-configuration58---5960# Implementing Google Workspace SSO Configuration6162## Overview6364Single Sign-On (SSO) for Google Workspace allows organizations to authenticate users through their existing identity provider (IdP) such as Okta, Azure AD (Microsoft Entra ID), or ADFS, rather than managing separate Google passwords. This is implemented using SAML 2.0 protocol where Google Workspace acts as the Service Provider (SP) and the organization's IdP handles authentication. SSO centralizes credential management, enforces MFA policies at the IdP, and enables immediate access revocation when users leave the organization.656667## When to Use6869- When deploying or configuring implementing google workspace sso configuration capabilities in your environment70- When establishing security controls aligned to compliance requirements71- When building or improving security architecture for this domain72- When conducting security assessments that require this implementation7374## Prerequisites7576- Google Workspace Business, Enterprise, or Education edition77- Super Admin access to Google Admin Console78- Identity Provider with SAML 2.0 support (Okta, Azure AD, ADFS, Ping Identity)79- IdP signing certificate (X.509 PEM format, RSA or DSA)80- DNS verification for the Google Workspace domain8182## Core Concepts8384### SAML 2.0 SSO Flow8586```87User navigates to Google Workspace app (Gmail, Drive, etc.)88 │89 ├── Google checks: Is SSO configured for this domain?90 │91 ├── YES → Redirect user to IdP Sign-In Page URL92 │ (SAML AuthnRequest sent via browser redirect)93 │94 ├── User authenticates at IdP (credentials + MFA)95 │96 ├── IdP generates SAML Response with signed assertion97 │98 ├── Browser POSTs SAML Response to Google ACS URL:99 │ https://www.google.com/a/{domain}/acs100 │101 ├── Google validates SAML signature against uploaded certificate102 │103 └── User is granted access to Google Workspace104```105106### Key SAML Parameters107108| Parameter | Value |109|-----------|-------|110| ACS URL | `https://www.google.com/a/{your-domain}/acs` |111| Entity ID | `google.com/a/{your-domain}` or `google.com` |112| NameID Format | `urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress` |113| NameID Value | User's primary Google Workspace email |114| Binding | HTTP-POST (for ACS), HTTP-Redirect (for SSO URL) |115116## Workflow117118### Step 1: Prepare the Identity Provider119120**For Okta:**1211. Navigate to Applications > Add Application > Search "Google Workspace"1222. Configure the Google Workspace app with your domain1233. Assign users/groups to the application1244. Download the IdP metadata or note: SSO URL, Entity ID, Certificate125126**For Azure AD (Microsoft Entra ID):**1271. Navigate to Enterprise Applications > New Application > Google Cloud/Workspace1282. Configure Single sign-on > SAML1293. Set Basic SAML Configuration:130 - Identifier (Entity ID): `google.com`131 - Reply URL (ACS): `https://www.google.com/a/{your-domain}/acs`132 - Sign on URL: `https://www.google.com/a/{your-domain}/ServiceLogin`1334. Download Federation Metadata XML or Certificate (Base64)134135**For ADFS:**1361. Add Relying Party Trust using federation metadata1372. Configure claim rules to pass NameID as email address1383. Export the token-signing certificate139140### Step 2: Configure Google Workspace SSO1411421. Sign in to Google Admin Console (admin.google.com) as Super Admin1432. Navigate to Security > Authentication > SSO with third-party IdP1443. Click "Add SSO profile" or configure the default profile145146**Third-Party SSO Profile Settings:**147148| Setting | Value |149|---------|-------|150| Set up SSO with third-party IdP | Enabled |151| Sign-in page URL | IdP's SAML SSO endpoint (e.g., `https://idp.example.com/sso/saml`) |152| Sign-out page URL | IdP's logout URL (e.g., `https://idp.example.com/slo`) |153| Change password URL | IdP's password change URL |154| Verification certificate | Upload IdP's X.509 signing certificate |155| Use a domain-specific issuer | Enabled (uses `google.com/a/{domain}` as entity ID) |156157### Step 3: Assign SSO Profile to Users158159SSO profiles can be applied at different scopes:160161```162Organization-wide (all users)163 │164 ├── Org Unit level (specific departments)165 │ ├── Engineering OU → SSO via Okta166 │ ├── Marketing OU → SSO via Azure AD167 │ └── Contractors OU → SSO via specific IdP168 │169 └── Group level (specific security groups)170 └── VPN Users → SSO with additional MFA171```1721731. Navigate to Security > Authentication > SSO with third-party IdP1742. Select the SSO profile to assign1753. Choose organizational units or groups1764. Save and wait for propagation (up to 24 hours, typically minutes)177178### Step 4: Configure Network Masks (Optional)179180Network masks control when SSO is enforced based on the user's IP:181182- If the user's IP matches a network mask, they use Google's sign-in page183- If the user's IP does NOT match, they are redirected to the IdP184185This is useful for allowing direct Google login from corporate network while enforcing SSO for external access.186187### Step 5: Test SSO1881891. Open an incognito browser window1902. Navigate to `https://mail.google.com/a/{your-domain}`1913. Verify redirect to IdP sign-in page1924. Authenticate at the IdP1935. Verify successful redirect back to Google Workspace1946. Test sign-out flow redirects to IdP logout page1957. Test with user not assigned in IdP (should fail)196197## Validation Checklist198199- [ ] IdP SAML application configured with correct ACS URL and Entity ID200- [ ] IdP signing certificate uploaded to Google Admin Console201- [ ] SSO profile assigned to target organizational units/groups202- [ ] SAML assertion includes correct NameID (email format)203- [ ] MFA enforced at IdP for all Google Workspace users204- [ ] Sign-out URL configured to terminate IdP session205- [ ] Network masks configured if internal/external access differs206- [ ] Break-glass Super Admin accounts bypass SSO (use Google auth)207- [ ] SSO tested with multiple user types (admin, standard, contractor)208- [ ] SAML response signature validated successfully209- [ ] Error handling tested (expired cert, invalid user, clock skew)210211## References212213- [Google Workspace SSO Configuration Guide](https://support.google.com/a/answer/12032922)214- [Set Up Custom SAML App - Google](https://support.google.com/a/answer/6087519)215- [Okta Google Workspace SAML Guide](https://saml-doc.okta.com/SAML_Docs/How-to-Enable-SAML-2.0-in-Google-Apps.html)216- [SAML 2.0 Technical Overview - OASIS](https://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html)