Skip to content
AgenticEcom User Guides AgenticEcom User Guides AgenticEcom User Guides

Social Login

VIDEO WALKTHROUGH

Social Login: setup guide

2:41

Recorded on version 1.0.4 · Narrated walkthrough · English captions

Jump to a chapter 8 chapters
Read the full video transcript 
Social Login 1.0.4 — Magento Admin setup

00:00:00 — Set up Social Login
Welcome to the Agentic Ecom Social Login Admin guide. We'll walk through the main setup screens and the checks to make before using the module. This guide assumes the extension is already installed.

00:00:12 — Open settings and choose scope
Start in Magento Admin and open Stores, Configuration. Choose Social Login. Check the Scope selector before editing. Use the appropriate website or store view where the setting supports it. The screen values here are a demonstration; enter the settings and service details that belong to your own store.

00:00:32 — Enable Social Login
In General, enable Social Login for the website you want to configure. This release supports Google, Apple, X, LinkedIn, Facebook and Amazon. Start with one provider and complete its setup before adding the others. Customer password sign-in remains available.

00:00:50 — Configure a provider
Open Google OAuth. Enable Google Login and enter the Client ID and Client Secret from your own provider application. After saving, copy the exact Authorized redirect URI displayed here into Google's developer console. The callback belongs to your Magento installation. Use HTTPS for a public store.

00:01:11 — Choose Luma or headless
For a Luma store, leave Enable Secure Headless Handoff off. A headless storefront needs its Magento OAuth API Base URL and its separate Storefront Callback URL. The storefront must exchange the short-lived one-time code through the module's Graph Q L operation; it must not treat that code as a customer token.

00:01:34 — Check allowed origins
For a headless store, enter each permitted storefront origin in Headless Allowed Redirect URIs. Use the origin only, such as H T T P S, shop dot example dot com, without a page path. Save at the correct website scope, clear configuration cache, and compare the provider callback byte for byte if a redirect is rejected.

00:01:57 — Save and verify your setup
When your required settings are complete, use the screen's Save control and wait for Magento's confirmation. Then reopen the record or configuration and check the saved values at the intended scope. If the storefront still shows earlier settings, refresh the relevant caches. Test your own configuration before using it with customers.

00:02:19 — Your setup checklist
That's the Admin setup walkthrough for Social Login. Check permissions and scope, review the module-specific settings, then save and verify a small staging example. Use the written guide at user guides dot Agentic Ecom dot net for installation details, complete field references and any separate storefront integration steps.
Download videoEnglish captionsDownload transcript

Current direct-store release: 1.0.5. Social Login adds Google, Apple, X, LinkedIn, Facebook and Amazon buttons to Magento Luma customer sign-in and registration. A headless storefront can use a short-lived, single-use code and a GraphQL exchange to obtain a customer token. The token is not placed in the redirect URL. GitHub is not a provider in this release.

Install or upgrade

Section titled “Install or upgrade”

For a direct AgenticEcom purchase, use the Composer repository and licence key in My Licences:

Terminal window
composer config repositories.agenticecom composer https://repo.agenticecom.net
composer config --global --auth http-basic.repo.agenticecom.net <YOUR-LICENCE-KEY> x
composer require agenticecom/module-sociallogin:^1.0.5
php bin/magento module:enable AgenticEcom_SocialLogin
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento cache:flush

For an Adobe Marketplace purchase, use Adobe’s supplied package repository and access method, then run the Magento commands. Keep only one module copy. Check provider credentials and callback URLs after upgrading.

Configure a provider

Section titled “Configure a provider”

Open Stores → Configuration → AgenticEcom → Social Login at the intended website scope. Enable Social Login and the chosen provider, enter that provider’s app credentials and save. The read-only Authorized redirect URIs field under each provider then displays its Magento callback URL. Copy that exact URL into the provider’s developer console. The callback uses the selected website’s effective Magento OAuth API base URL; it is not fixed to an AgenticEcom or demonstration domain.

For example, when the merchant’s Magento API origin is https://api.example.com, the Google callback is https://api.example.com/sociallogin/login/callback/provider/google. The provider callback points to Magento, while the storefront handoff URL is configured separately. Use HTTPS on public callbacks. Apple needs its Service ID, Team ID, Key ID and P8 key. X needs OAuth 2.0 access to the users.email scope.

For a Luma store, leave Enable Secure Headless Handoff off. Fully configured enabled providers appear on customer sign-in and registration. A successful login returns the shopper to the Magento customer account.

Headless storefront setup

Section titled “Headless storefront setup”

Set Enable Secure Headless Handoff to Yes and configure:

  • Magento OAuth API Base URL: the public HTTPS origin of this merchant’s Magento API, such as https://api.example.com. This is used to display the provider callback URLs.
  • Storefront Callback URL: the exact HTTPS page that receives the one-time code, such as https://shop.example.com/social-login/callback.
  • Headless Allowed Redirect URIs: the callback page’s HTTPS origin only, such as https://shop.example.com. Do not enter a path or the Magento API host here. Add each permitted storefront origin explicitly.

Save configuration, clear Magento config cache, and re-check the read-only provider callback URL. Register that Magento URL with each provider. Deploy a storefront callback that exchanges the one-time code through socialLoginExchangeToken before enabling customer sign-in. The code is short-lived and can be exchanged once; the customer token is returned by GraphQL to the storefront, not exposed in the URL.

Account linking and troubleshooting

Section titled “Account linking and troubleshooting”

Returning provider identities sign in to their linked Magento customer account. A new provider identity with a verified matching email can link to an existing customer. Facebook and Amazon require a one-use email confirmation for first-time linking; that link expires after 15 minutes. If a provider does not return an email, sign-in cannot complete; check its scopes and app permissions. Customer password sign-in remains available.

If a button leads to a missing /customer/account/login/ route on a headless storefront, verify that the three headless settings above saved at the active website scope. Clear Magento config cache and the storefront’s product/config cache after changing them. If a provider rejects the redirect, compare its registered URI byte-for-byte with the read-only Magento callback shown after saving.

The package permits PHP 8.3, 8.4 and 8.5. Validate the chosen Magento/PHP pair and provider app setup on staging. Support: support@agenticecom.co.uk.