--- name: implementing-google-workspace-sso-configuration-224350697ba2 description: Configure SAML 2.0 single sign-on for Google Workspace with a third-party identity provider, enabling centralized authentication and enforcing organization-wide access policies. domain: cybersecurity subdomain: identity-access-management tags: - google-workspace - sso - saml - identity-provider - authentication - federation version: '1.0' author: mahipal license: Apache-2.0 nist_csf: - PR.AA-01 - PR.AA-02 - PR.AA-05 - PR.AA-06 mitre_attack: - T1078 - T1110 - T1556 - T1098 --- # 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:** 1. Navigate to Applications > Add Application > Search "Google Workspace" 2. Configure the Google Workspace app with your domain 3. Assign users/groups to the application 4. Download the IdP metadata or note: SSO URL, Entity ID, Certificate **For Azure AD (Microsoft Entra ID):** 1. Navigate to Enterprise Applications > New Application > Google Cloud/Workspace 2. Configure Single sign-on > SAML 3. 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` 4. Download Federation Metadata XML or Certificate (Base64) **For ADFS:** 1. Add Relying Party Trust using federation metadata 2. Configure claim rules to pass NameID as email address 3. Export the token-signing certificate ### Step 2: Configure Google Workspace SSO 1. Sign in to Google Admin Console (admin.google.com) as Super Admin 2. Navigate to Security > Authentication > SSO with third-party IdP 3. 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 ``` 1. Navigate to Security > Authentication > SSO with third-party IdP 2. Select the SSO profile to assign 3. Choose organizational units or groups 4. 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 1. Open an incognito browser window 2. Navigate to `https://mail.google.com/a/{your-domain}` 3. Verify redirect to IdP sign-in page 4. Authenticate at the IdP 5. Verify successful redirect back to Google Workspace 6. Test sign-out flow redirects to IdP logout page 7. Test with user not assigned in IdP (should fail) ## Validation Checklist - [ ] IdP SAML application configured with correct ACS URL and Entity ID - [ ] IdP signing certificate uploaded to Google Admin Console - [ ] SSO profile assigned to target organizational units/groups - [ ] SAML assertion includes correct NameID (email format) - [ ] MFA enforced at IdP for all Google Workspace users - [ ] Sign-out URL configured to terminate IdP session - [ ] Network masks configured if internal/external access differs - [ ] Break-glass Super Admin accounts bypass SSO (use Google auth) - [ ] SSO tested with multiple user types (admin, standard, contractor) - [ ] SAML response signature validated successfully - [ ] Error handling tested (expired cert, invalid user, clock skew) ## References - [Google Workspace SSO Configuration Guide](https://support.google.com/a/answer/12032922) - [Set Up Custom SAML App - Google](https://support.google.com/a/answer/6087519) - [Okta Google Workspace SAML Guide](https://saml-doc.okta.com/SAML_Docs/How-to-Enable-SAML-2.0-in-Google-Apps.html) - [SAML 2.0 Technical Overview - OASIS](https://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html) --- Source attribution: 26zl Original project: https://github.com/26zl/cybersec-toolkit/blob/2ad2519d437cda1f8a822ef7adc336993601a5ac/.claude/skills/implementing-google-workspace-sso-configuration/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Dave AI. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. Please do not remove or change the license header comment from a contributed file except when necessary. Copyright 2026 mukul975 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Dave AI resource metadata Creator / publisher: 26zl Original project: https://github.com/26zl/cybersec-toolkit/blob/2ad2519d437cda1f8a822ef7adc336993601a5ac/.claude/skills/implementing-google-workspace-sso-configuration/SKILL.md Attribution basis: Source repository record Fields of work: Operations, Sales Roles: Customer Success Manager, IT Operations Specialties: API Tools: Adfs, Azure Ad, Okta Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 613ae0b065c2dcb07ef249876c6e1f74244a04ddf83a6149790e5bf9c12a1476