Tanner Record

Chris Kindred

<p>This plugin gives your users the ability to sign in with their G Suite account. If they don’t have a user account on your site and they try to sign in, an account will be created for them (if their email address domain is listed in the restricted domains).<br />
This is great for Agencies or sites that have lots of users and need a way to make signing in a quick and painless process.</p>
<h4>Features</h4>
<ul>
<li>Show/Hide the “Log In with Google” button on the login form</li>
<li>Restrict user logins to a specific domain</li>
<li>If a user is already logged in to Google, they will be automatically redirected without much fuss</li>
<li>Connect existing user accounts with a Google account</li>
<li>A custom login parameter can be added to the URL of the site as a “hidden” login. For example adding <code>?mysitename_login</code> to your url (for example: <code>https://mysitename.com/?mysitename_login</code>) will log in the user, or redirect them to log in with Google.</li>
</ul>
<h4>WARNING</h4>
<p>If you leave the “Log in with Google” button shown on the login form, make sure that you are comfortable with the new user role that is set. Since this plugin creates user accounts for those that do not already have an account on the site, use domain restriction or set a low level role to the users.</p>
<h3>Development</h3>
<p>Active plugin development is handled on <a href="https://www.github.com/tarecord/sign-in-with-google" rel="nofollow ugc">Github</a>. Bugs and issues will be tracked and handled there.</p>


Sign In With Google

Seems lightweight plugin (& more secure too), without bunch of dependencies.
thanks!

Clean and lightweight

Clean, easy, simple and works (even in multisite).

Awesome plugin.

Works perfectly

Adds a "Log in with Google" option to the login form so users can sign in with their G Suite account.

Automattic

Manzoor Wani

Gergely J

<p>Sign in with Telegram lets your visitors log in with their Telegram account — no extra password to remember, no new account to create. Unlike older Telegram-login plugins that rely on a script embedded from Telegram (which modern privacy-focused browsers often block), this plugin uses <a href="https://core.telegram.org/bots/telegram-login" rel="nofollow ugc">Telegram’s standard OpenID Connect login</a>: a secure redirect to Telegram and back. It works reliably in every browser, including ones with strict tracker blocking turned on.</p>
<h4>Features</h4>
<ul>
<li><strong>“Sign in with Telegram” button</strong> on the standard <code>wp-login.php</code> screen, as a <code>[telegram_signin_button]</code> shortcode anywhere on your site, or as a Block Editor block.</li>
<li><strong>Account linking</strong> from the user profile screen — existing WordPress users can connect or disconnect their Telegram account.</li>
<li><strong>Profile sync</strong> — display name and avatar from the user’s Telegram profile flow through to the WordPress profile automatically.</li>
<li><strong>No automatic account merging</strong> — a Telegram identity can only attach to an existing WordPress user through an explicit click-to-link action from a logged-in session, so a stranger who happens to share an email address can never take over an account.</li>
<li><strong>Secure by default</strong> — uses the same kind of modern, signed redirect flow that “Sign in with Google” and “Sign in with Apple” use. No shared bot-token secret on your server, no manual key rotation.</li>
<li><strong>Settings page</strong> in wp-admin where you paste the bot’s Client ID + Client Secret, pick the default role for new users, and optionally collect the visitor’s verified phone number or request permission for your bot to message them directly.</li>
</ul>
<h4>How it compares to the legacy Login Widget</h4>
<p>Telegram’s older Login Widget (used by most existing Telegram-login plugins on the directory) is <strong>not</strong> OAuth or OpenID Connect. It loads a JavaScript file from telegram.org that renders Telegram’s button on your page and then hands the auth result either to a JavaScript callback or to a server URL. Either mode still needs the embedded script to render the button in the first place. That setup is increasingly fragile:</p>
<ul>
<li>Browsers with strict third-party-script blocking — Brave with default shields, Firefox Enhanced Tracking Protection on Strict, Safari Lockdown Mode, uBlock Origin filter lists — frequently block the embedded script outright, so the button never renders and visitors have no way to start the flow.</li>
<li>The widget’s authentication hash is an HMAC-SHA256 over your bot token, so anyone who wants to verify a login has to hold a copy of that secret. There’s no standard JWT / JWKS story to lean on.</li>
<li>Key rotation is manual — changing the HMAC key means rotating the bot token in BotFather and updating it on every server that verifies logins.</li>
</ul>
<p>Sign in with Telegram uses Telegram’s newer OpenID Connect provider instead — a standard server-side redirect flow with a properly signed RS256 <code>id_token</code>. No third-party scripts on your pages, no shared bot-token secret with verifiers, automatic key rotation via JWKS. It behaves the same regardless of how privacy-locked-down the visitor’s browser is.</p>
<h3>External services</h3>
<p>This plugin connects to Telegram’s OpenID Connect provider at <code>oauth.telegram.org</code> so visitors can sign in with their Telegram account. No data is sent to Telegram unless a visitor actively starts a sign-in.</p>
<p>What is sent, and when:</p>
<ul>
<li><strong>Sign-in start.</strong> When a visitor clicks the “Sign in with Telegram” button, their browser is redirected to <code>oauth.telegram.org</code> with the bot’s Client ID, the requested scopes (always <code>openid</code> and <code>profile</code>; additionally <code>phone</code> and / or <code>telegram:bot_access</code> if you enabled those in <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Sign in with Telegram</strong>), a random <code>state</code>, a random <code>nonce</code>, and a PKCE <code>code_challenge</code> (SHA-256). The only user-specific traffic at this step is the browser redirect itself. If the discovery cache is cold (see below), building the redirect URL also triggers an anonymous server-side GET of the discovery document — no user data in that request.</li>
<li><strong>Sign-in callback.</strong> After the visitor approves the sign-in on Telegram’s side, Telegram redirects them back to your site with an authorization <code>code</code>. The plugin then makes a single server-to-server POST to Telegram’s token endpoint, sending the Client ID + Client Secret (as HTTP Basic auth), the <code>code</code>, the matching PKCE <code>code_verifier</code>, and the redirect URI. Telegram responds with a signed <code>id_token</code> containing the visitor’s Telegram identifier, name, profile picture URL, and (if the <code>phone</code> scope was granted) phone number.</li>
<li><strong>Discovery + JWKS lookup.</strong> The first sign-in after activation (and again after the local cache expires, 12 hours) triggers a one-off, anonymous GET to Telegram’s OpenID Connect discovery document and JSON Web Key Set (JWKS) at <code>oauth.telegram.org</code>. Both responses are cached in WordPress transients. If a later <code>id_token</code> references a signing key that isn’t in the cache (Telegram rotated keys), the JWKS is re-fetched once; a short cooldown prevents repeated refresh attempts. No user data is sent in any of these requests.</li>
</ul>
<p>This service is provided by Telegram. Refer to Telegram’s <a href="https://telegram.org/tos" rel="nofollow ugc">Terms of Service</a> and <a href="https://telegram.org/privacy" rel="nofollow ugc">Privacy Policy</a> for details on how Telegram handles the sign-in.</p>


Sign in with Telegram

Add Telegram login to your WordPress site. Visitors sign in with their existing Telegram account — no new password to remember.

Sign In With Google vs Sign in with Telegram