AGENT SKILL

implementing-google-workspace-sso-configuration

Configures SAML 2.0 single sign-on for Google Workspace against a third-party identity provider (Okta, Azure AD/Entra ID, ADFS), with Workspace as the Service Provider, to centralize authentication and enable immediate access revocation. Use when setting up or troubleshooting Google Workspace SSO/SAML federation or migrating from native Google passwords to an external IdP.

License 许可
Apache-2.0
最近更新
2026-09-11
Stars
★ 0
Forks
0

01 前言 Front Matter

name
implementing-google-workspace-sso-configuration
tags
[ "google-workspace", "sso", "saml", "identity-provider", "authentication", "federation" ]
author
mahipal
domain
cybersecurity
license
Apache-2.0
version
1.0
mitre_f3
{ "tactics": [ "initial-access", "positioning" ], "version": "1.1", "techniques": [ { "id": "T1110", "name": "Brute Force", "source": "attack", "tactic": "initial-access" }, { "id": "T1110.004", "name": "Brute Force: Credential Stuffing", "source": "attack", "tactic": "initial-access" }, { "id": "T1539", "name": "Steal Web Session Cookie", "source": "attack", "tactic": "positioning" }, { "id": "F1004", "name": "Access with Stolen Session Cookie", "source": "f3", "tactic": "initial-access" }, { "id": "F1006", "name": "Account Takeover", "source": "f3", "tactic": "initial-access" } ] }
nist_csf
[ "PR.AA-01", "PR.AA-02", "PR.AA-05", "PR.AA-06" ]
subdomain
identity-access-management
description
Configures SAML 2.0 single sign-on for Google Workspace against a third-party identity provider (Okta, Azure AD/Entra ID, ADFS), with Workspace as the Service Provider, to centralize authentication and enable immediate access revocation. Use when setting up or troubleshooting Google Workspace SSO/SAML federation or migrating from native Google passwords to an external IdP.
mitre_attack
[ "T1078", "T1110", "T1556", "T1098" ]

02 资源文件 7

03 SKILL.md 正文

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

04 同仓库更多 Skills

NeelakshSaxena
NeelakshSaxena/Vayu

runpodctl

Runpod CLI for managing GPU/CPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send/receive). Use for terminal/CI/scripting, Hub browse/deploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod

Start here for any Runpod task — running GPU/CPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-usage

How Runpod works and how to work it — pods vs serverless, GPU/VRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv/apt). Use to answer "how does X work", "which GPU", "how do I build a container", or "how do I stand up a workload on a pod". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-templates

Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says "run <X> on a pod" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-migrate

Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-mcp

Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU/CPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.

★ 0