Wapu Auth – Social Login for WordPress and WooCommerce
by Victor Flores 1 (0 reviews)

Wapu Auth – Social Login for WordPress and WooCommerce

Google and Facebook social login for WordPress and WooCommerce through Wapu Auth Broker, with secure account linking, sessions and local analytics.

Wapu Auth ranks #18,488 among WordPress.org plugins with 70+ active installations, is #427 of 1,659 in the Authentication category, a 1/5 rating from 0 reviews, and was last updated Aug 12, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 6.9 (Current: 7.1.4)
v2.1.0 Current Version v2.1.0
Updated 2 months ago Last Update on 12 Aug, 2026
Refreshed 1 week ago Last Refreshed on
#427 of 1,659 in Authentication Top 25% by installs Downloads -20% this week
View on WordPress.org
Rank
#18,488
— No change
Active Installs
70+
+16.7%
KW Avg Position
83.5
0.2 worse
Downloads
280
+4 today
Support Resolved
100%
— No change
Rating
20%
Review 1 out of 5
1 (0 reviews)

Next Milestone 80

Total Progress 70%
70+ 80+
1,211
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 3 more installs to reach 80+

Rank Changes

17,564 18,026 18,488 18,950 19,412 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
18,351 18,411 18,471 18,531 18,591 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
Current #18,488
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
0 10 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0
0 reviews
Overall 20%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Support Threads Overview

Resolved
Unresolved
1
Total Threads
1
Resolved
0
Unresolved
100%
Resolution Rate

Frequently Asked Questions

Common questions about Wapu Auth – Social Login for WordPress and WooCommerce

Redirect-based Google and Facebook login still requires no provider credentials in WordPress. Optional native Google One Tap requires only the site's public Google OAuth Web application Client ID, because Google requires the storefront's exact Authorized JavaScript Origin. Wapu Auth never asks for a Client Secret for One Tap.
Open Wapu Auth > Providers > Google One Tap and select How to get the Client ID. Complete the project's Branding and Audience configuration, then create a Web application client. The modal shows the exact HTTPS origin to add under Authorized JavaScript origins and links directly to Google Auth Platform. Paste the resulting Web Client ID and enable One Tap. Do not add a Client Secret or an Authorized Redirect URI for this flow. Google changes can take a few minutes; an origin_mismatch error normally means the configured scheme, host, or port is not an exact match. If the site uses full-page or CDN caching, purge that cache after first enabling or disabling One Tap so every cached page has the current script set. Client ID changes are additionally bound to the current server-created session, preventing stale HTML from selecting an outdated audience.
Keep the site's Content Security Policy compatible with Google Identity Services and the Broker. At minimum, allow the versionless script https://accounts.google.com/gsi/client, the Google Identity Services resources under https://accounts.google.com/gsi/, and browser connections to https://auth.wapuos.com. A stricter policy may require matching script-src, frame-src and connect-src entries. The normal Google redirect button remains the fallback if the prompt is blocked or unavailable.
The normal causes are a non-public or non-HTTPS URL, localhost or a reserved hostname, Basic Auth, maintenance mode, a firewall blocking the verification endpoint, disabled WP-Cron, outbound HTTPS restrictions, DNS mismatch, or a cloned database carrying credentials for another origin. Correct the environment and use Retry automatic connection. Do not paste broker secrets into support requests.
No. A verified credential bound to the current origin short-circuits registration. Pending proof-of-control work is reused under a lock. An ambiguous one-time verification response stops for explicit recovery instead of starting a replacement automatically.
No. It proves that WordPress can decrypt the local secret and build a valid signature. The current broker contract has no authenticated credential-health endpoint. Provider availability and an end-to-end staging login remain separate checks.
Yes. Canonical mappings are provider-specific and enforce one subject per provider and one provider identity per WordPress user. Cross-provider linking requires an authenticated user and a fresh broker flow.
Wapu Auth follows the broker's nullable Facebook-email contract. It does not invent or silently trust an email. The account-linking flow must resolve safely under the configured local policy.
No. Native WordPress and WooCommerce login remain available. Pausing broker mode stops only new social-login starts.
No. Wapu Auth works with WordPress alone. WooCommerce hooks and My Account features are loaded only when WooCommerce is active.

Sign In / Register

You need to sign in or register to use this feature.