2 min readMay 26, 2026by jakub

Installation

1. Require the metapackage

Choose the metapackage that matches your storefront theme. Both pull in Base + OAuth2 + OpenID + all 20 providers.

Luma / default theme:

Bash
composer require qoliber/social-login

Hyvä theme (adds the Hyvä-compatible, CSP-safe templates):

Bash
composer require qoliber/social-login-hyva-suite

ℹ️ The Hyvä suite automatically pulls qoliber/hyva-module-registration and the Hyvä theme modules. The registration package is what tells the Hyvä Tailwind build to scan this module's templates — so its utility classes survive the CSS purge. No extra install step; just don't forget hyva:config:generate below.

Optional — headless / PWA (GraphQL):

Bash
composer require qoliber/social-login-graphql

ℹ️ The mock providers (testing only) are intentionally not part of these metapackages and must not be installed on production. Passwordless / passkey sign-in is a separate product (qoliber/passkey) — it isn't part of the social-login suite.

2. Enable and upgrade

Bash
bin/magento module:enable --all
bin/magento setup:upgrade
bin/magento setup:di:compile          # production mode only
bin/magento setup:static-content:deploy   # production mode only
bin/magento cache:flush

3. Hyvä storefronts only

qoliber/social-login-hyva registers itself with Hyvä through qoliber/hyva-module-registration (a sequenced dependency) and the CompatModuleFallback, so its Alpine, CSP-safe templates replace the Luma ones on Hyvä store views and its Tailwind classes are kept by the theme build.

Regenerate the Hyvä config so that registration is picked up:

Bash
bin/magento hyva:config:generate

Then rebuild the Hyvä theme CSS (npm run build in your Hyvä theme) so the social-login utility classes are compiled in rather than purged.

⚠️ Run hyva:config:generate before setup:di:compile on a fresh install — the registration package must be present (it comes with the suite) or compilation can't resolve the Hyvä registration observer.

4. Turn it on

The suite ships disabled. Enable it in the admin (next page), then configure at least one provider.

📸 Screenshot — Admin · Stores → Configuration → Qoliber → Social Login → General Settings The "Enable Social Login" toggle set to Yes.

Verify the install

Bash
bin/magento module:status | grep Qoliber_SocialLogin

You should see Qoliber_SocialLoginBase, …OAuth2, …OpenID, and one module per enabled provider.

Continue to Configuration →

Social Login — Installation — Social Login for Magento 2 — Marketing — Extensions | qoliber Docs