markmont

This plugin is for a very specific use case: Your WordPress website is part of an organization that uses OpenID Connect (OIDC) for web single-sign-on as well as for group-based authorization. In that case, this plugin will let you restrict access to parts of your WordPress website based on OIDC login and group membership information.
This plugin has been tested with:
<ul>
<li><a href="https://www.shibboleth.net/" rel="nofollow ugc">Shibboleth</a> OIDC using the <code>edumember_ismemberof</code> attribute for LDAP group membership.</li>
</ul>
Features:
<ul>
<li>Allow site visitors to log in via OIDC without needing a WordPress user account.</li>
<li>Optionally allow WordPress users to log in via OIDC instead of using their WordPress password.</li>
<li>Optionally restrict access to the entire site to logged-in users or only members of specific groups.</li>
<li>Optionally restrict access to specific pages and posts to logged-in users or only members of specific groups.</li>
<li>Show parts of pages/posts/widgets only to logged-in users or members of specific groups.</li>
<li>Access restrictions apply to site visitors, feeds, the REST API, and XMLRPC.</li>
<li>Shortcodes (Gutenberg blocks planned for a future release)
<ul>
<li><code>umich_oidc_button</code> – Generate a login or logout button.</li>
<li><code>umich_oidc_link</code> – Generate a login or logout link.</li>
<li><code>umich_oidc_logged_in</code> – Show content only if the visitor is logged in.</li>
<li><code>umich_oidc_member</code> – Show content only if the visitor is a member of one or more groups.</li>
<li><code>umich_oidc_not_logged_in</code> – Show content only if the visitor is NOT logged in.</li>
<li><code>umich_oidc_not_member</code> – Show content only if the visitor NOT a member of the specified groups.</li>
<li><code>umich_oidc_url</code> – Generate a login or logout URL.</li>
<li><code>umich_oidc_userinfo</code> – Display information about the currently-logged-in OIDC user.</li>
</ul>
</li>
</ul>
<h3>Restricting private content in search results</h3>
You can prevent content from showing up in web search engine results by restricting access to particular pages/posts.
Search results from WordPress’ built-in search will only show content that the searching user has access to.
WARNING: WordPress search plugins may show content that the user does not have access to, leaking private information. Please test search plugins before enabling them. If a search plugin provides an appropriate WordPress hook for limiting search results, contact us, and we may be able to add support for it to UMich OIDC Login.
<h3>Copyright and license information</h3>
Copyright (c) 2022 Regents of the University of Michigan.
This file is part of the UMich OIDC Login WordPress plugin.
UMich OIDC Login is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
UMich OIDC Login is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with UMich OIDC Login. If not, see <a href="https://www.gnu.org/licenses/" rel="nofollow ugc">https://www.gnu.org/licenses/</a>.

UMich OIDC Login

Restrict access to the whole site or only certain parts based on OpenID Connect (OIDC) login and group membership information.

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.

UMich OIDC Login vs Sign in with Telegram