Offer familiar sign-in choices
Configure the providers that suit your customers. Luma and headless GraphQL support let you connect social sign-in to the storefront journey.
Let customers use an account they already know. Offer six sign-in providers, with Luma support and GraphQL operations for a headless storefront.
You need provider applications and valid callback URLs. Sign-in and account confirmation depend on the provider and configured flow.
For Magento Open Source 2.4.9. Review the module guide for installation, dependencies and frontend integration requirements. We can help check the fit with your existing store.
Configure the providers that suit your customers. Luma and headless GraphQL support let you connect social sign-in to the storefront journey.
One-time state nonces, provider-verified email checks, encrypted client secrets and redirect allowlists support the authentication flow.
Check the module guide, supported version and setup requirements for your store.
Install and configure on staging. Test the workflows that matter to your team.
Deploy the tested configuration and use the included support when you need help.
Review the supported version and module guide, and test on staging with your current theme and extensions. Luma presentation and headless integration requirements vary by module; contact us if you need help checking compatibility.
The one-time licence includes 12 months of updates and priority support. Purchased versions remain usable. Renewal is optional and never billed automatically; see the current purchase terms for eligibility and renewal details.
Yes. AgenticSuite includes the Astro storefront and all headless and Luma-compatible modules listed on this website. You can buy this module for the store you run today, or discuss the complete platform for a frontend rebuild.
Social Login is a Magento 2 module that lets shoppers sign in with existing accounts from major providers in one click, linking each provider identity to a Magento customer account and showing every linked account in the admin.
A surprising share of abandoned carts come down to one thing: account friction. The shopper is ready to buy, hits "create account", and stalls at inventing yet another password. Social Login removes that wall — one tap signs them in with an account they already have and trust. But sign-in is also where stores get breached, so this module is built security-first: it won't hand someone another customer's account just because they typed the right email. It checks, verifies, and protects every step.
6 providers · One-click sign-in · CSRF state nonces · Verified-email linking · Encrypted secrets · Redirect-URI allow-list · Luma + headless · Check release-specific Magento and PHP compatibility
| The providers shoppers have | Google, Facebook, Apple, X (Twitter), LinkedIn and Amazon — enable the ones that fit your audience. |
|---|---|
| One tap, account ready | First sign-in creates the Magento account automatically; returning customers are straight in. |
| Link & unlink | Existing customers can connect a social account to their login — and remove it again — from their account. |
| Headless-native | A GraphQL flow with state nonces and a redirect-URI allow-list gives Astro storefronts the same secure sign-in. |
Google · Facebook · Apple · X (Twitter) · LinkedIn · Amazon
Enable any combination, set each one's client ID and secret, and order the buttons how you like. First-time sign-in creates the Magento customer account automatically (you can require a real email and send a fallback password), and logged-in customers can link or unlink providers from their account area.
This is where sign-in modules usually get it wrong — and where this one is careful. Every login uses a one-time CSRF state nonce bound to the session, so an intercepted link can't be replayed. An account is only ever linked to a social identity when the provider confirms the email is verified — closing the classic account-takeover hole where someone signs up with your email at a provider that never checked it. Client secrets are stored encrypted, the headless token flow only redirects to URLs on your allow-list, and the public provider query returns client IDs only — never a secret.
| Providers | Google, Facebook, Apple, X (Twitter), LinkedIn, Amazon |
|---|---|
| Accounts | Auto-create on first sign-in; link/unlink from the customer account; optional require-real-email and fallback password |
| CSRF protection | One-time state nonce bound to the session, required on token exchange |
| Anti-takeover | Links only when the provider reports the email as verified |
| Secrets | Client secrets stored encrypted; public query exposes client IDs only |
| Headless | GraphQL state, providers, exchange-token, link and unlink; redirect-URI allow-list and storefront callback |
| Buttons | Per-provider enable and sort order |
| Delivery & licence | Composer install, per-domain licence key, updates via Composer |
Part of the AgenticEcom suite for Sales, Customers & Marketing:
Pairs with Social Share for a complete social layer and GDPR Pro for consent. Included in the AgenticEcom Suite.
Google, Facebook, Apple, X (Twitter), LinkedIn and Amazon. Enable any combination, and order the buttons to suit your audience.
No. The module only links a social identity to a Magento account when the provider confirms the email address is verified, which closes the common account-takeover route. Every sign-in also carries a one-time CSRF state nonce that can't be replayed.
Yes. The first time someone signs in with a provider, their Magento customer account is created. You can require a real email and send them a fallback password, and existing customers can link a provider to their current account.
Yes. A GraphQL flow issues a state nonce, returns enabled providers and client IDs, and exchanges the OAuth code for a customer token — only redirecting to URLs on your configured allow-list.
Check release-specific Magento and PHP compatibility before installation.
New in 1.0.4: Magento Admin shows the website-specific OAuth callback URL for all six providers, including a configured headless API domain.
Latest release: Version 1.0.5
Keep improving the store you run today. When you need a full frontend rebuild, AgenticSuite combines the Astro storefront, visual admin and included module collection.
Your source code.
Your data. Your direction.
Review the setup requirements, choose your module and get started. We’re here if you need to check the fit.