{"id":404519,"date":"2026-11-19T11:20:22","date_gmt":"2026-11-19T11:20:22","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/lean-google-login\/"},"modified":"2026-11-19T11:20:07","modified_gmt":"2026-11-19T11:20:07","slug":"lean-sign-in-with-google","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/lean-sign-in-with-google\/","author":15235348,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.0","stable_tag":"1.0.0","tested":"7.1.5","requires":"6.0","requires_php":"8.1","requires_plugins":null,"header_name":"Lean Sign in with Google","header_author":"pjaudiomv","header_description":"Free, no upsells, no telemetry. Adds a \"Sign in with Google\" button to wp-login.php using the OAuth2 authorization-code flow, with an optional Google Workspace domain allow-list, optional auto-provisioning of new users, and wp-config.php overrides. Password login is never disabled.","last_updated":"2026-11-19 11:20:07","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/github.com\/katamalabs\/lean-sign-in-with-google","header_author_uri":"","rating":0,"author_block_rating":0,"active_installs":0,"downloads":46,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.0":{"tag":"1.0.0","author":"pjaudiomv","date":"2026-11-19 11:20:07","revision":3811357}},"upgrade_notice":{"1.0.0":"<p>First release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3811356,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3811356,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3811356,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3811356,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3811356,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250},"banner.svg":{"filename":"banner.svg","revision":3811356,"resolution":false,"location":"assets","locale":false}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3811356,"resolution":"1","location":"assets","locale":"","width":1200,"height":900},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3811356,"resolution":"2","location":"assets","locale":"","width":1200,"height":900}},"screenshots":{"1":"Settings \u2192 Lean Sign in with Google: paste your Google OAuth client ID and secret, copy the redirect URI into Google Cloud, limit sign-in to one or more Workspace domains, and choose whether new users are created and with which role.","2":"The \"Sign in with Google\" button on the WordPress login screen. Normal password login stays enabled alongside it."}},"plugin_section":[],"plugin_tags":[150,284202,602,2061,2469],"plugin_category":[38],"plugin_contributors":[154957],"plugin_business_model":[],"class_list":["post-404519","plugin","type-plugin","status-publish","hentry","plugin_tags-google","plugin_tags-google-workspace","plugin_tags-login","plugin_tags-oauth","plugin_tags-sso","plugin_category-authentication","plugin_contributors-pjaudiomv","plugin_committers-pjaudiomv"],"banners":{"banner":"https:\/\/ps.w.org\/lean-sign-in-with-google\/assets\/banner-772x250.png?rev=3811356","banner_2x":"https:\/\/ps.w.org\/lean-sign-in-with-google\/assets\/banner-1544x500.png?rev=3811356","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/lean-sign-in-with-google\/assets\/icon.svg?rev=3811356","icon":"https:\/\/ps.w.org\/lean-sign-in-with-google\/assets\/icon.svg?rev=3811356","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/lean-sign-in-with-google\/assets\/screenshot-1.png?rev=3811356","caption":"Settings \u2192 Lean Sign in with Google: paste your Google OAuth client ID and secret, copy the redirect URI into Google Cloud, limit sign-in to one or more Workspace domains, and choose whether new users are created and with which role."},{"src":"https:\/\/ps.w.org\/lean-sign-in-with-google\/assets\/screenshot-2.png?rev=3811356","caption":"The \"Sign in with Google\" button on the WordPress login screen. Normal password login stays enabled alongside it."}],"raw_content":"<!--section=description-->\n<p>Lean Sign in with Google adds a <strong>Sign in with Google<\/strong> button to your WordPress login screen using the standard OAuth2 authorization-code flow. It is deliberately small: one button, a handful of settings, and no bundled Google SDK.<\/p>\n\n<p><strong>Everything is free.<\/strong> There is no pro version, no paid add-ons, no account to create, and no upsell banners in the admin. Nothing phones home \u2014 the plugin makes no network requests other than the Google OAuth calls needed to sign a person in.<\/p>\n\n<ul>\n<li><strong>Workspace domain limiting<\/strong>: restrict sign-in to one or more Google Workspace domains, enforced on the Workspace <code>hd<\/code> claim \u2014 the membership signal Google documents \u2014 not on the email domain alone. An account whose <code>hd<\/code> isn't in your list is turned away. Leave it blank to allow any verified Google account.<\/li>\n<li><strong>Existing users by default<\/strong>: people who already have a WordPress account sign in by matching their verified Google email. A pre-existing account is auto-linked to a first sign-in only when Google is authoritative for the address (a Workspace or Gmail account). Creating accounts for new Google users is an explicit opt-in, with a role you choose.<\/li>\n<li><strong>Account-takeover protection<\/strong>: the Google account id (<code>sub<\/code>) is the primary key for an established link, so a returning user is matched by <code>sub<\/code> first and a later login to the same email must come from the same Google account.<\/li>\n<li><strong>Honors your login policies<\/strong>: core account eligibility (multisite spam\/deleted and site membership) and the <code>wp_authenticate_user<\/code> policy filter that account-disable and 2FA plugins hook are enforced before a session is issued.<\/li>\n<li><strong>Password login stays enabled<\/strong>: the plugin only <em>adds<\/em> a button. Your normal username\/password login keeps working, so there is no way to lock yourself out.<\/li>\n<li><strong>Encrypted secret<\/strong>: the OAuth client secret is AES-256 encrypted at rest, keyed to your site salts, and never echoed back to the browser.<\/li>\n<li><strong>wp-config.php overrides<\/strong>: pin the client ID, secret, or allowed domains in code instead of the database, so credentials can live in environment variables and never diverge between environments.<\/li>\n<\/ul>\n\n<p><strong>Why no One Tap, and why Workspace-friendly without Google verification:<\/strong> this plugin uses only the non-sensitive <code>openid<\/code>, <code>email<\/code>, and <code>profile<\/code> scopes and the server-side redirect flow. That means no Google app-verification process, no client-side JavaScript, and no JWT signature gymnastics \u2014 the identity token is read straight from Google's own TLS response during the code exchange. It works with an External or Internal OAuth consent screen, for Workspace or consumer Google accounts (restrict to your domain to keep it Workspace-only).<\/p>\n\n<p>Consumer-Gmail One Tap and Microsoft 365 login are deliberate non-goals \u2014 they would add client-side token verification and more moving parts than the rest of the plugin combined.<\/p>\n\n<h3>External services<\/h3>\n\n<p>This plugin connects to Google's OAuth 2.0 and OpenID Connect services to authenticate people who choose to sign in with Google. This connection is what makes the \"Sign in with Google\" button work; the plugin does not function without it, and it contacts no other external service.<\/p>\n\n<p>The connection happens only when a site administrator has configured a Google OAuth client and a visitor clicks the \"Sign in with Google\" button. It involves these Google endpoints:<\/p>\n\n<ul>\n<li><code>https:\/\/accounts.google.com\/o\/oauth2\/v2\/auth<\/code> \u2014 the visitor's browser is redirected here to sign in to Google and consent. The plugin sends your configured OAuth client ID, the requested scopes (<code>openid<\/code>, <code>email<\/code>, <code>profile<\/code>), the redirect URI back to your site, and an anti-CSRF <code>state<\/code> value.<\/li>\n<li><code>https:\/\/oauth2.googleapis.com\/token<\/code> \u2014 after the visitor returns, your server exchanges the one-time authorization code for an identity token. The plugin sends your OAuth client ID, client secret, the authorization code, and the redirect URI. In response, Google returns the signed-in person's Google account identifier, email address, email-verified flag, and (if present) name and Workspace hosted-domain claim, which the plugin uses to match or create the WordPress account.<\/li>\n<\/ul>\n\n<p>No data is sent to Google unless and until a visitor initiates a Google sign-in. The plugin sends no analytics, telemetry, or personal data of its own to any service.<\/p>\n\n<p>This service is provided by Google. By using it you are subject to:<\/p>\n\n<ul>\n<li>Google Terms of Service: https:\/\/policies.google.com\/terms<\/li>\n<li>Google Privacy Policy: https:\/\/policies.google.com\/privacy<\/li>\n<li>Google API Services User Data Policy: https:\/\/developers.google.com\/terms\/api-services-user-data-policy<\/li>\n<\/ul>\n\n<!--section=installation-->\n<ol>\n<li>Upload the plugin and activate it.<\/li>\n<li>In the <a href=\"https:\/\/console.cloud.google.com\/\">Google Cloud Console<\/a>, create an OAuth 2.0 Client ID of type <strong>Web application<\/strong> (set the OAuth consent screen to Internal for a Workspace org, or External for consumer accounts).<\/li>\n<li>Go to Settings \u2192 Lean Sign in with Google and copy the <strong>Authorized redirect URI<\/strong> shown there into your OAuth client's \"Authorized redirect URIs\" in Google Cloud (it must match exactly).<\/li>\n<li>Paste the <strong>Client ID<\/strong> and <strong>Client Secret<\/strong> into the plugin and save.<\/li>\n<li>Optionally set one or more <strong>Allowed domains<\/strong>, and decide whether new Google users should get an account.<\/li>\n<li>A \"Sign in with Google\" button now appears on your login screen.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"does%20this%20disable%20password%20login%3F\"><h3>Does this disable password login?<\/h3><\/dt>\n<dd><p>No. It only adds a button. Your normal WordPress login keeps working, so you can never be locked out.<\/p><\/dd>\n<dt id=\"can%20i%20restrict%20sign-in%20to%20my%20company%27s%20google%20workspace%20domain%3F\"><h3>Can I restrict sign-in to my company's Google Workspace domain?<\/h3><\/dt>\n<dd><p>Yes. Enter your domain(s) under Allowed domains. Only accounts whose verified email or Workspace hosted-domain claim match are allowed in.<\/p><\/dd>\n<dt id=\"does%20it%20work%20with%20consumer%20%40gmail.com%20accounts%3F\"><h3>Does it work with consumer @gmail.com accounts?<\/h3><\/dt>\n<dd><p>Yes, if you leave the domain allow-list blank. To keep it Workspace-only, set your Workspace domain in Allowed domains.<\/p><\/dd>\n<dt id=\"does%20it%20need%20a%20google%20app%20verification%20or%20security%20assessment%3F\"><h3>Does it need a Google app verification or security assessment?<\/h3><\/dt>\n<dd><p>No. It uses only the non-sensitive openid \/ email \/ profile scopes, which need no verification.<\/p><\/dd>\n<dt id=\"is%20it%20really%20free%3F%20is%20there%20a%20pro%20version%3F\"><h3>Is it really free? Is there a pro version?<\/h3><\/dt>\n<dd><p>Yes, free. There is no pro version and no upsells.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>Initial release: \"Sign in with Google\" button on wp-login.php via the OAuth2 authorization-code flow, optional Workspace domain allow-list.<\/li>\n<\/ul>","raw_excerpt":"A minimal, secure \"Sign in with Google\" button for WordPress, with an optional Google Workspace domain allow-list. No upsells, no telemetry.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/404519","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=404519"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/pjaudiomv"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=404519"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=404519"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=404519"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=404519"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=404519"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=404519"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}