পণ্যের অংশে চলে যান
LCPanelলাইসেন্স সেন্টার প্যানেল
MMB MyMeetBook টি অধ্যায়

MyMeetBook ডকুমেন্টেশন

সোশ্যাল লগইন

Google, Facebook, X, LinkedIn, GitHub, Discord বা Apple দিয়ে লগইন ও যোগদান: কী কোথায় পাবেন আর কোন ঠিকানা বসাবেন।

প্লাগিনগুলো হালনাগাদ ৬ নভে ২০২৬ ২৩ / ৪০

The Social login plugin puts Continue with … buttons on the log-in and sign-up pages. Visitors join in two clicks, without making up another password, and members connect the accounts they already have.

Since version 1.1.0 it knows 23 services — Google, Facebook, X, LinkedIn, GitHub, Discord, Apple, Microsoft, Yahoo, Twitch, Reddit, Amazon, TikTok, LINE, VK, Spotify, GitLab, Dropbox, Slack, WordPress.com, Yandex, Pinterest and Telegram — plus your own AIO Video and AIO Downloader sites and three custom slots for any other OAuth 2.0 / OpenID Connect server.

It needs the PHP extensions curl and openssl, which nearly every host has, and for most providers a site on HTTPS.

What members get

  • Continue with … buttons above the log-in form and, when you allow it, above the sign-up form. Up to six providers are shown as a list of wide buttons with the words; from seven on the page shows a wrapping grid of round buttons with the brand mark, and the name appears as a tooltip (and is read out by screen readers).
  • Signing in: a member who connected that account before is signed in at once.
  • Joining: a new visitor gets an account with their name, a username made from their name or e-mail, and their profile picture from the provider. The site then behaves as for any new member: the welcome e-mail goes out, and admin approval applies when you have it on. E-mail confirmation is only asked for when the provider has not confirmed the address itself.
  • One more step: X, Reddit, TikTok, Pinterest, Telegram and some GitHub accounts do not share an e-mail address. The visitor then types the address their account should use, once. These providers carry a No e-mail mark on the admin page.
  • Settings → Connected accounts: every provider you switched on, with Connect or Disconnect. Members who joined through a provider have no password yet; the same tab offers Set a password so they can always log in, even without that service. The last connected account cannot be disconnected until a password is set.

The site only reads the name, e-mail address and picture, and never posts anything to the member's other accounts. If a member also uses Two-factor sign-in, the code is still asked after a social sign-in.

How accounts are matched

  1. The provider account is already connected to a member: that member is signed in.
  2. Otherwise, the provider says the e-mail address is confirmed and a member already uses that address: with Link by e-mail on, the account is connected to that member and they are signed in. A member still waiting to confirm their e-mail counts as confirmed now.
  3. Otherwise, a member already uses that address but the provider has not confirmed it: the visitor is asked to log in with their password and connect the provider under Settings → Connected accounts. Nobody can take over an account just by typing someone's address at a provider.
  4. Otherwise a new member is made, when joining is open.

Which providers count as confirmed: Google, LinkedIn, Yahoo, GitLab, Dropbox, Slack, WordPress.com and the AIO sites say so in their answer; Facebook, GitHub (verified addresses only), Discord (when verified), Twitch, Amazon, LINE and Yandex only hand out addresses they verified themselves; Microsoft counts for personal accounts and for work accounts whose token carries the verified mark; Spotify and VK addresses are treated as unconfirmed; a custom slot is confirmed only when its answer has email_verified: true.

No new accounts are made when New members may join with a social account is off, when registration is closed, or when the site is invite-only.

Setting it up

Admin → Plugin pages → Social login.

The providers are grouped — Popular, More, AIO sites, Custom — with a row of jump links at the top that also counts how many are on in each group. Every provider has its own card with:

  • Show "Continue with …": the switch for its button;
  • Redirect address to paste in the developer console, with a copy button. It is always https://your-site/auth/<provider>/callback, for example https://your-site/auth/google/callback (Telegram is the exception: it wants your domain instead, see below);
  • Client ID and Client secret. The secret is stored encrypted and never shown again; leave the field empty to keep it, type a new one to replace it;
  • a short guide to where the keys are and Open the console, a link to the provider's developer pages.

The card says On, Off, or Keys missing when it is switched on without complete keys; then its button stays hidden.

ProviderWhere the keys come from
GoogleGoogle Cloud console → APIs & Services → Credentials → OAuth client ID (Web application). Paste the redirect address under Authorised redirect URIs.
FacebookMeta for Developers → your app → Facebook Login → Settings: Valid OAuth Redirect URIs. App ID and App Secret are under App settings → Basic.
XDeveloper portal → your app → User authentication settings: OAuth 2.0, type Web App. Use the OAuth 2.0 Client ID and Client Secret, not the API key. No e-mail.
LinkedInYour app → Products: add Sign In with LinkedIn using OpenID Connect; Auth tab: add the redirect address.
GitHubSettings → Developer settings → OAuth Apps → New OAuth App; Authorization callback URL = the redirect address.
DiscordDeveloper portal → your application → OAuth2: add the redirect address under Redirects.
AppleMarked Advanced. Make a Services ID (that is the client ID) with Sign in with Apple, your domain and the redirect address; make a key with Sign in with Apple and download the .p8 file. Fill in Services ID, Team ID, Key ID and paste the .p8 private key. Needs HTTPS.
MicrosoftMicrosoft Entra admin centre (or the Azure portal) → App registrations → New registration: account type Personal Microsoft accounts and any organisation, platform Web with the redirect address. Application (client) ID is the client ID; Certificates & secrets → New client secret gives the secret (paste its value, not its ID). Personal and work accounts both sign in.

More

ProviderWhere the keys come from
Yahoodeveloper.yahoo.com → Create an app: Web application, the redirect address, permissions OpenID Connect with e-mail and profile.
Twitchdev.twitch.tv → Console → Register your application: OAuth redirect URL = the redirect address, category Website integration; the Client ID and a new secret from Manage.
Redditreddit.com/prefs/apps → create another app: type web app, redirect uri = the redirect address. The client ID is the short line under the app name, the secret is next to secret. No e-mail.
AmazonLogin with Amazon console → new security profile → Web Settings: your site under Allowed origins, the redirect address under Allowed return URLs.
TikTokdevelopers.tiktok.com → Manage apps → your app: add the Login Kit product, Redirect URI = the redirect address, scope user.info.basic. The Client key goes in the client ID field. No e-mail.
LINELINE Developers console → a provider → new LINE Login channel: Callback URL = the redirect address; Channel ID = client ID, Channel secret = the secret. Apply for the email permission on the channel to receive addresses.
VKid.vk.com → business → your app: platform Web, Trusted redirect URL = the redirect address, base domain = your domain. Paste the App ID; no secret is needed, the sign-in uses PKCE.
Spotifydeveloper.spotify.com → Dashboard → Create app: Redirect URI = the redirect address, API Web API; keys under Settings. Addresses count as unconfirmed.
GitLabgitlab.com → User settings → Applications: Redirect URI = the redirect address, scopes openid profile email. Application ID = client ID.
DropboxDropbox App Console → Create app (Scoped access): Redirect URI = the redirect address; permissions openid email profile. App key = client ID, App secret = the secret.
Slackapi.slack.com/apps → Create app → OAuth & Permissions: Redirect URL = the redirect address, User Token Scopes openid email profile. Keys under Basic Information. Sign in with Slack (OpenID Connect).
WordPress.comdeveloper.wordpress.com/apps → Create new application: Redirect URL = the redirect address, type Web.
Yandexoauth.yandex.com → Create new client: platform Web services, Redirect URI = the redirect address; data access e-mail, name, avatar.
Pinterestdevelopers.pinterest.com → My apps → Create app: Redirect URI = the redirect address, scope user_accounts:read. App id = client ID, App secret key = the secret. No e-mail.
TelegramSee Telegram below: a bot token instead of OAuth keys. No e-mail.

Telegram (the Login Widget)

Telegram has no OAuth keys. Talk to @BotFather in Telegram:

  1. /newbot — pick a name and a username; BotFather answers with the bot token (123456789:AAH…).
  2. /setdomain — choose the bot and give it your site's domain exactly as shown on the card (for example social.example.com). Without this step Telegram refuses the sign-in.
  3. On the card, paste the bot username (without @) and the bot token, switch the button on.

On the log-in page the Telegram button opens Telegram's own small window (the official widget script); the visitor confirms in the Telegram app and comes back signed in. When that script cannot load, the same button leads to Telegram's sign-in page, which brings the visitor back by itself. Either way the answer is checked the way Telegram prescribes — an HMAC-SHA256 over the data with the SHA-256 of the bot token as the key — must be fresh, and cannot be used twice. Telegram gives the name, username and photo, no e-mail: new members type their address once.

AIO sites

Members of your AIO Video or AIO Downloader site can log in here with that account. On the other site, under Admin → Settings → Sign in with this site, make a client with this card's redirect address. Then on the card type only the site address members open — for example https://aiovideo.com or https://aiovideodl.com — plus the client ID and secret. The sign-in addresses are derived from it (/oauth/authorize, /oauth/token, /oauth/userinfo) and shown under the field once saved. The exchange uses PKCE and the OpenID openid email profile scope; a confirmed e-mail on the other site links the accounts.

Custom providers

Three slots for any other OAuth 2.0 / OpenID Connect server (a company SSO, Keycloak, Authentik, Auth0, Okta, Nextcloud, a Mastodon instance …). Register the slot's redirect address there, then fill in:

  • Name on the button and an icon — an emoji, or a small square picture you upload (shown round on the log-in page);
  • Authorize address, Token address, User info address and the scope (openid email profile for OpenID Connect);
  • Client ID and Client secret;
  • the field names of the user-info answer for the id, name, e-mail and picture. They default to the OpenID names sub, name, email, picture. Dots dig into nested objects (data.user.id), a|b tries b when a is empty. The e-mail counts as confirmed only when the answer carries email_verified: true.

PKCE (S256) and the state check are always on; the token call sends the client id and secret as form fields.

Sign-up rules

  • New members may join with a social account: off means only existing members can connect a provider.
  • Link by e-mail: see How accounts are matched.
  • Show the buttons on the sign-up page too.

Numbers

How many providers are on, connected accounts, members with one or more, and per provider the connections, sign-ups and use in the last 30 days, with the latest connections.

Coming from WoWonder

When the WoWonder Migration plugin found social login keys on the old site, this page shows Keys from your old site with Import keys from the old site. The Google, Facebook, Twitter (as X), LinkedIn, VK, Discord, Reddit, Twitch, Dropbox, WordPress, Microsoft and Yahoo keys are copied into empty providers; others are listed as not supported. Then add the new redirect addresses in each developer console: the old WoWonder addresses do not work here.

When something goes wrong

  • The sign-in took too long or was started in another browser: the visitor waited more than 15 minutes at the provider, or the session was lost. Trying again works. The same words appear when a Telegram answer is replayed.
  • The provider shows redirect_uri mismatch or similar: the address in its console is not exactly the one on the card. Copy it again, including https://.
  • Telegram says Bot domain invalid: run /setdomain in BotFather with the domain shown on the card.
  • A provider that refuses the sign-in writes the reason to cache/logs/social-login.log (Admin → Logs → Files). Tokens and secrets are never written there.
  • The secrets are encrypted with the site's own secret key, MMB_SECRET in config.php. Keep that file when you move the site; with a new key the saved secrets cannot be read and must be typed again.
এটি কি কাজে লেগেছে?
এই অধ্যায়টি শেয়ার করুন