Add guide on disabling default social logins via Google Workspace#3502
Open
xnox wants to merge 2 commits into
Open
Add guide on disabling default social logins via Google Workspace#3502xnox wants to merge 2 commits into
xnox wants to merge 2 commits into
Conversation
Documents the interim workaround for SSO/OIDC customers whose users accidentally sign in with "Login with Google", creating accounts outside their organization. Explains how a Google Workspace admin can block the Chainguard app via API access control, with break-glass guidance to scope the block by organizational unit. Published as a draft pending screenshots. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
|
||
| * You have a [backup account](/chainguard/administration/custom-idps/custom-idps/#backup-accounts) that does not rely on Google sign-in — for example, an [assumable identity](/chainguard/administration/iam-organizations/assumable-ids/) — so you retain a recovery path. | ||
|
|
||
| You will also need administrator access to your organization's [Google Workspace Admin console](https://admin.google.com). |
Collaborator
There was a problem hiding this comment.
I'm not sure what's going on with the apostrophes being interpreted as formatting marks. @SharpRake do you know?
Collaborator
There was a problem hiding this comment.
From here down to line 81, alternating several times.
Co-authored-by: Matthew Helmke <matthew.helmke@chainguard.dev> Signed-off-by: Mark Drake <33191761+SharpRake@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a new article: Disabling Default Social Logins at
content/chainguard/administration/custom-idps/disabling-social-logins/index.md.It documents the interim workaround for SSO/OIDC customers whose users keep clicking Login with Google out of habit — creating accounts outside their organization that owners then have to clean up and re-provision.
Why
This is a recurring, high-frequency customer pain point (reported ~3x/week for one customer). A native org-level setting to hide/disable the default social logins is on the Q3 roadmap, but this Google Workspace-side block solves it today and is worth publicising.
Approach
Rather than a Chainguard-side toggle (which doesn't exist yet), the guide explains how a Google Workspace admin blocks the Chainguard app via Security > Access and data control > API controls > App access control, scoping the block by organizational unit. It includes:
Error 400: admin_policy_enforced)Notes for reviewers
draft: true— pending cropped screenshots of the Google Admin console (steps 3–6). ATODOcomment marks where they go and the naming convention. Flip todraft: falseonce screenshots are added.🤖 Generated with Claude Code