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

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

সোশ্যাল লগইন

এক ক্লিকে Google, Facebook, LinkedIn, GitHub বা X দিয়ে সাইন-ইন; পুরনো অ্যাকাউন্ট ই-মেইলে মেলে, নতুনটা তখনই তৈরি হয়। ফ্রি।

প্লাগইন হালনাগাদ ৬ নভে ২০২৬ ২৪ / ৫০

The Social Login plugin adds "Continue with Google / Facebook / LinkedIn / GitHub / X" buttons to the sign-in and registration pages. One click and the visitor is in: an existing member is matched by e-mail address, a stranger gets an account made on the spot. It talks plain OAuth 2 to each provider, so there is no SDK to install and nothing to update.

Who it is for

Sites that want sign-ups without a password form - most consumer file hosts. It is also a quiet way to cut fake registrations, since every account is backed by a real Google or Facebook login.

Switching it on

Social Login is free and works with every licence; a fresh install switches it on. Otherwise open Admin → Extensions → Plugins (Manage Plugins) and switch it on. Its page appears under Extensions as Social Login (/admin/plugin/social-login). Switching it on makes the table bp_social_accounts, which remembers which provider id belongs to which member.

No button shows until at least one provider is enabled and has a client id.

Registering your site with a provider

Every provider wants the same two things: your site's redirect (callback) URL, which the settings page prints at the top and is always

https://your-site/plugins/social-login/callback

and in return gives you a client id and a client secret. Where to get them:

ProviderWhereNotes
GoogleGoogle Cloud Console → APIs & Services → Credentials → OAuth client (Web application)Add the redirect URL under Authorised redirect URIs.
Facebookdevelopers.facebook.com → your app → Facebook Login → Valid OAuth Redirect URIsThe app must be live, not in development mode, for strangers to sign in.
LinkedInlinkedin.com/developers → your app → AuthAdd the product Sign In with LinkedIn using OpenID Connect.
GitHubgithub.com/settings/developers → OAuth AppsThe callback URL goes in Authorization callback URL.
X (Twitter)developer.x.com → your app → User authentication settings (OAuth 2.0, Web App)X does not share e-mail addresses: the account is matched by its X id only.

Our other products: AIO Video, MyMeetBook, AIO Downloader

Three more buttons sign a visitor in with an account from another faruk.bd script - AIO Video (aiovideo.com), MyMeetBook (mymeetbook.com) and AIO Downloader (aiovideodl.com), or any site that runs those scripts. Their cards sit under the heading Sign in with our other products on the settings page, and each needs one more thing than the providers above: the address of the site that signs people in.

  1. On the other site, switch on its oauth-server (or Developer API) plugin and create an app under its Developer / OAuth apps page.
  2. Paste BoxPuff's callback URL as the app's redirect URL. The card prints it - it is the same https://your-site/plugins/social-login/callback as for every provider.
  3. Copy the app's client id and client secret back here, and fill in the card's site address (for example https://aiovideo.com, no trailing slash; a port or a folder is fine).
  4. Tick the card's enabled box and save.

The plugin then talks OpenID-style OAuth with PKCE to that site's /oauth/authorize, /oauth/token and /oauth/userinfo, asking for the openid email profile scopes. Such a card is ready only when the site address, client id and secret are all filled in. The visitor is matched by e-mail like everywhere else, with one rule on top: if the other site says the e-mail address is not verified there, it is not matched to an existing account here.

The settings page

One card per provider with three fields: Google enabled (and so on), Google client id, Google client secret. A saved secret shows A secret is saved; type a new one to replace it; leaving the box empty keeps it. Under the cards:

  • Create an account when the e-mail is new (on by default). Off: only members who already have an account with that e-mail may use the buttons; strangers see No account with that e-mail address exists. Please register first.

The page also counts Linked accounts so far.

What happens on a click

  1. The visitor presses a provider button on /login or /register. The site sends them to the provider at /plugins/social-login/login?provider=<code> with a signed state.
  2. The provider sends them back to the callback with a code; the plugin trades it for a token and reads the profile (id, name, e-mail where the provider shares it).
  3. A provider id already linked to a member signs that member in. Otherwise the e-mail is looked up; a match links the provider to that existing account.
  4. No match: when Create an account when the e-mail is new is on and Site Options → Enable user registration is on, an account is made. The username comes from the provider's username or the part of the e-mail before @ (letters, numbers, dots, dashes and underscores, up to 16 characters, with a number added when taken), the name is split into first and last name, a random password is set, and the e-mail counts as verified because the provider vouched for it. Admin approves registrations is honoured: such accounts wait as awaiting approval. An affiliate cookie from the Rewards Program is honoured too.
  5. The member lands in the file manager.

Members who came in this way have no password they know. They can set one with Forgot password on the login page, which e-mails a reset link, and from then on both doors work.

Tips

  • Start with Google; it is the one most visitors have and the quickest to set up.
  • Keep Create an account when the e-mail is new on unless registration on your site is by invitation.
  • If a provider answers with a redirect-URI error, the URL you registered differs from the one printed on the settings page by a character - check https against http, www, and a trailing slash.
  • X never gives an e-mail, so an X member who later registers normally with an e-mail ends up with two accounts; prefer Google or Facebook where e-mail matters.
  • A member cannot unlink a provider themselves in this version; delete the row from bp_social_accounts in System Tools → Database Browser if ever asked.
এটি কি কাজে লেগেছে?
এই অধ্যায়টি শেয়ার করুন