logto

Thank you for choosing <a href="https://logto.io/?ref=wpp" rel="nofollow ugc">Logto</a>! By integrating Logto into your WordPress site, you are not only enhancing the security and user experience of your site, but also enabling a unified login experience across all your applications.
<h3>Why Logto?</h3>
Logto is an open-source Auth0 alternative and a modern authentication and authorization solution for all your applications, including your WordPress sites. With Logto, you can:
<ul>
<li>Enable passwordless login, social login, single sign-on (SSO), and multi-factor authentication (MFA) for your WordPress site.</li>
<li>Use role-based access control (RBAC) to manage user permissions.</li>
<li>Support generic OAuth2, OpenID Connect, and SAML protocols.</li>
<li>Customize the login and registration pages to match your brand.</li>
</ul>
In addition, Logto offers dozens of out-of-the-box integrations with popular social login providers, including Google, GitHub, Entra ID (Azure AD), Facebook, and more. Check out the <a href="https://docs.logto.io/integrations" rel="nofollow ugc">full list of built-in integrations and social login providers</a>.
<h3>Get started</h3>
If you are new to Logto, we recommend checking out our <a href="https://docs.logto.io/" rel="nofollow ugc">introduction page</a> to have a quick overview of Logto concepts and features.
If you are looking for a step-by-step guide to set up Logto, please refer to our <a href="https://docs.logto.io/quick-start/wordpress-plugin" rel="nofollow ugc">WordPress plugin quick start guide</a>.
If you have any questions or feedback, please feel free to:
<ul>
<li><a href="https://discord.com/invite/UEPaF3j5e6" rel="nofollow ugc">Join our Discord server</a> to get help from the community.</li>
<li><a href="https://github.com/logto-io/wordpress/issues" rel="nofollow ugc">Open an issue on GitHub</a> to report bugs or request features.</li>
<li><a href="https://logto.io/" rel="nofollow ugc">Subscribe to a paid plan</a> to get access to official support and more features.</li>
</ul>
<h3>From WordPress admin panel</h3>
<ol>
<li>Go to Plugins > Add New.</li>
<li>Search for “Logto”.</li>
<li>Click Install Now.</li>
<li>Click Activate.</li>
<li>Go to Settings > Logto to configure the plugin.</li>
<li>Follow the <a href="https://docs.logto.io/quick-start/wordpress-plugin" rel="nofollow ugc">quick start guide</a> to set up Logto.</li>
</ol>
<h3>From WordPress.org</h3>
<ol>
<li>Search for “Logto” in the <a href="https://wordpress.org/plugins/" rel="ugc">WordPress.org plugin directory</a>.</li>
<li>Download the plugin ZIP file.</li>
<li>Go to Plugins > Add New in your WordPress admin panel.</li>
<li>Click Upload Plugin.</li>
<li>Select the downloaded ZIP file and click Install Now.</li>
<li>Click Activate.</li>
<li>Go to Settings > Logto to configure the plugin.</li>
<li>Follow the <a href="https://docs.logto.io/quick-start/wordpress-plugin" rel="nofollow ugc">quick start guide</a> to set up Logto.</li>
</ol>

Logto – User Authentication and Authorization

Enable beautiful and secure user authentication, including passwordless, social login, single sign-on, multi-factor authentication (MFA), and more.

Automattic

Manzoor Wani

Gergely J

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.
<h4>Features</h4>
<ul>
<li>“Sign in with Telegram” button 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>Account linking from the user profile screen — existing WordPress users can connect or disconnect their Telegram account.</li>
<li>Profile sync — display name and avatar from the user’s Telegram profile flow through to the WordPress profile automatically.</li>
<li>No automatic account merging — 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>Secure by default — 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>Settings page 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>
Telegram’s older Login Widget (used by most existing Telegram-login plugins on the directory) is not 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:
<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>
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.
<h3>External services</h3>
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.
What is sent, and when:
<ul>
<li>Sign-in start. 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 Settings → Sign in with Telegram), 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>Sign-in callback. 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>Discovery + JWKS lookup. 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>
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.

Sign in with Telegram

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

Logto – User Authentication and Authorization vs Sign in with Telegram