New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Implementing Google Workspace Sso Configuration

by mukul975 in mukul975/Anthropic-Cybersecurity-Skills

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…

Apache-2.0Auto-check passedBackend & APIs

Install Implementing Google Workspace Sso Configuration

skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-google-workspace-sso-configuration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills implementing-google-workspace-sso-configuration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/implementing-google-workspace-sso-configuration .claude/skills/implementing-google-workspace-sso-configuration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
implementing-google-workspace-sso-configuration
GitHub stars
34k
Token cost
~2k tokens
SKILL.md length
682 words
Files
8 (incl. scripts, references, assets)
Skills in repo
644
Repo updated
First seen
Licence
Apache-2.0

At a glance

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…

  • Works in 5 steps: Prepare the Identity Provider → Configure Google Workspace SSO → Assign SSO Profile to Users → …
  • Troubleshooting Google Workspace SSO/SAML federation
  • SKILL.md covers Overview, When to Use, Prerequisites and Core Concepts, plus 3 more sections
  • Runs Python scripts from its folder; reaches google.com and mail.google.com

What it does

Implementing Google Workspace Sso Configuration is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. 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.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/api-reference.md` and `references/standards.md`).

It sits in Backend & APIs, covering Authentication, Cloud office suites and OAuth and OpenID Connect. It works with Google Workspace, Microsoft Entra ID and Okta. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.

When your agent uses it

  • Troubleshooting Google Workspace SSO/SAML federation
  • Migrating from native Google passwords to an external IdP

Example prompts

  • “Use the implementing-google-workspace-sso-configuration skill to configure SAML 2.0 single sign-on for Google Workspace against a third-party…”
  • “/implementing-google-workspace-sso-configuration”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Prepare the Identity Provider
  2. Configure Google Workspace SSO
  3. Assign SSO Profile to Users
  4. Configure Network Masks (Optional)
  5. Test SSO

What it can do on your machine

Read from SKILL.md and the folder at commit 54a7988. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • google.com
    • mail.google.com

    Also links to:

    • support.google.com
    • saml-doc.okta.com
    • docs.oasis-open.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Implementing Google Workspace Sso Configuration loads about 2k tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 106 tokens; SKILL.md has 682 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~106
When it runs · the whole SKILL.md, loaded when a task matches
~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from mukul975/Anthropic-Cybersecurity-Skills at commit 54a7988, republished under its Apache-2.0 licence (© mukul975). 682 words, ~1,958 tokens.

Download SKILL.mdSave it as .claude/skills/implementing-google-workspace-sso-configuration/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
implementing-google-workspace-sso-configuration
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.
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
mitre_f3.version
1.1
mitre_f3.tactics
initial-access, positioning

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
ParameterValue
ACS URLhttps://www.google.com/a/{your-domain}/acs
Entity IDgoogle.com/a/{your-domain} or google.com
NameID Formaturn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress
NameID ValueUser's primary Google Workspace email
BindingHTTP-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:

SettingValue
Set up SSO with third-party IdPEnabled
Sign-in page URLIdP's SAML SSO endpoint (e.g., https://idp.example.com/sso/saml)
Sign-out page URLIdP's logout URL (e.g., https://idp.example.com/slo)
Change password URLIdP's password change URL
Verification certificateUpload IdP's X.509 signing certificate
Use a domain-specific issuerEnabled (uses google.com/a/{domain} as entity ID)
Show full SKILL.md (275 more words)Show less
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

© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (scripts, references, assets) in skills/implementing-google-workspace-sso-configuration of mukul975/Anthropic-Cybersecurity-Skills.

  • SKILL.md
  • LICENSE
  • assets/template.md
  • references/api-reference.md
  • references/standards.md
  • references/workflows.md
  • scripts/agent.py
  • scripts/process.py

Open the folder on GitHubat commit 54a7988

Compare with similar skills

Implementing Google Workspace Sso Configuration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Implementing Google Workspace Sso Configuration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Implementing Google Workspace Sso Configuration this skillmukul975/Anthropic-Cybersecurity-Skills34k—~2kAutomated safety check: PassApache-2.0
Cursor Sso Integrationjeremylongshore/tons-of-skills-marketplace2.8k—~2kAutomated safety check: PassMIT
Identity Access Managementsickn33/agentic-awesome-skills47k1 repos~2.9kAutomated safety check: PassMIT
Iam Auditbriiirussell/cybersecurity-skills413—~3.1kAutomated safety check: NotesMIT
Google WorkspaceRedWoodOG/Hermes-Desktop177—~2.1kAutomated safety check: PassMIT
Google Chatsanjay3290/ai-skills432—~1.2kAutomated safety check: PassApache-2.0

Similar skills

  • Cursor Sso Integration

    jeremylongshore/tons-of-skills-marketplace

    Configure SAML 2.0 and OIDC SSO for Cursor with Okta, Microsoft Entra ID, and Google Workspace.

    2.8k GitHub stars~2k tokensUpdated today
    Backend & APIsAuto-check passed

  • Identity Access Management

    sickn33/agentic-awesome-skills

    Set up and manage SSO, SCIM provisioning, and MFA for startup teams using Google Workspace, Okta, or Azure AD.

    47k GitHub starsUsed in 1 repo~2.9k tokens
    Backend & APIsAuto-check passed

  • Iam Audit

    briiirussell/cybersecurity-skills

    Audit, design, and migrate Identity and Access Management — cloud provider IAM (AWS, GCP, Azure), identity providers (Okta, Entra ID / Azure AD, Auth0, Google Workspace), application authorization…

    413 GitHub stars~3.1k tokensUpdated 4 mo ago
    Backend & APIsAuto-check: notes

  • Google Workspace

    RedWoodOG/Hermes-Desktop

    Gmail, Calendar, Drive, Contacts, Sheets, and Docs integration via Python.

    177 GitHub stars~2.1k tokensUpdated 4 mo ago
    Backend & APIsAuto-check passed

  • Google Chat

    sanjay3290/ai-skills

    Interact with Google Chat - send, read, edit, delete and react to messages, share images and files, reply in threads, and manage spaces and DMs.

    432 GitHub stars~1.2k tokensUpdated 29 days ago
    Backend & APIsAuto-check passed

  • API Gateway

    CraftOS-dev/CraftBot

    Connect to 100+ APIs (Google Workspace, Microsoft 365, Notion, Slack, Airtable, HubSpot, etc.) with managed OAuth.

    392 GitHub starsUsed in 3 repos~7.1k tokens
    Backend & APIsAuto-check passed

More from mukul975/Anthropic-Cybersecurity-Skills

All 644 skills in this repo

  • Campaign Attribution Evidence Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Weighs infrastructure, TTP, malware code and timing evidence with the Diamond Model and competing hypotheses to reach a confidence-rated attribution.

    34k GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Go Malware Analysis in Ghidra

    mukul975/Anthropic-Cybersecurity-Skills

    Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed

  • LNK and Jump List Forensics

    mukul975/Anthropic-Cybersecurity-Skills

    Guides forensic analysis of Windows LNK shortcut files and Jump Lists with LECmd, JLECmd and manual parsing to show file access and program execution.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed

  • Malware Persistence Analysis with Autoruns

    mukul975/Anthropic-Cybersecurity-Skills

    Hunts Windows malware persistence with Sysinternals Autoruns, covering run keys, services, scheduled tasks and drivers, with baseline comparison.

    34k GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

  • NTFS MFT Deleted File Recovery

    mukul975/Anthropic-Cybersecurity-Skills

    Guides a Windows forensic examination of the NTFS Master File Table to recover deleted-file evidence, build timelines and spot timestomping.

    34k GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed

  • Network Covert Channel Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.

    34k GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Implementing Google Workspace Sso Configuration

What does Implementing Google Workspace Sso Configuration do?

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…. Implementing Google Workspace Sso Configuration is an agent skill from mukul975/Anthropic-Cybersecurity-Skills.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.

When should I use Implementing Google Workspace Sso Configuration?

Implementing Google Workspace Sso Configuration fits situations like: troubleshooting Google Workspace SSO/SAML federation; migrating from native Google passwords to an external IdP.

How do I install Implementing Google Workspace Sso Configuration in Claude Code?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-google-workspace-sso-configuration -a claude-code`. Or copy the skill folder (skills/implementing-google-workspace-sso-configuration in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/implementing-google-workspace-sso-configuration in your project. Claude Code loads it when a task matches its description.

How do I install Implementing Google Workspace Sso Configuration in Codex?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-google-workspace-sso-configuration -a codex`. Or copy the skill folder (skills/implementing-google-workspace-sso-configuration in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/implementing-google-workspace-sso-configuration in your project. Codex loads it when a task matches its description.

Can I use Implementing Google Workspace Sso Configuration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-google-workspace-sso-configuration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/implementing-google-workspace-sso-configuration, .gemini/skills/implementing-google-workspace-sso-configuration, .github/skills/implementing-google-workspace-sso-configuration and .opencode/skills/implementing-google-workspace-sso-configuration in your project.

What does Implementing Google Workspace Sso Configuration need to run?

Going by SKILL.md and its folder, Implementing Google Workspace Sso Configuration needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Implementing Google Workspace Sso Configuration access the network?

SKILL.md names 5 domains. In commands or code: google.com and mail.google.com; the agent is likely to contact these when it follows the instructions. As links in the text: support.google.com, saml-doc.okta.com and docs.oasis-open.org. This is read from the text; nothing was executed.

Is Implementing Google Workspace Sso Configuration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Implementing Google Workspace Sso Configuration use?

Implementing Google Workspace Sso Configuration is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Implementing Google Workspace Sso Configuration use?

About 2k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.

What are the alternatives to Implementing Google Workspace Sso Configuration?

Skills that share tags, products or a category with Implementing Google Workspace Sso Configuration: Cursor Sso Integration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Identity Access Management (sickn33/agentic-awesome-skills, 47k stars), Iam Audit (briiirussell/cybersecurity-skills, 413 stars) and Google Workspace (RedWoodOG/Hermes-Desktop, 177 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Implementing Google Workspace Sso Configuration?

mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 34,116 GitHub stars. The repository holds 644 skills in this directory. The repository was last updated on August 31, 2026.

Source: mukul975/Anthropic-Cybersecurity-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.