Athenian Social Sign-on
Overview
Product overview
WordPress and WooCommerce stores often lose conversions at the account wall. Native login flows create friction, social login plugins vary in quality, credential handling is inconsistent, and merchants are left stitching together separate login experiences for wp-login, My Account, and custom landing pages.
Athenian Social Sign-on solves that by providing a unified Google and Facebook/Meta sign-on layer built specifically for WordPress and WooCommerce. It supports official provider flows, shortcode-based placement, automatic login CTA injection, SecureStore-backed credential preference, provider-subject account matching and explicit authenticated connections, and profile avatar synchronization so social sign-on behaves like a coherent platform feature rather than a fragile add-on.
Use cases
- Social login
- Account linking
- Identity onboarding
- Passwordless-style access
Developer
Developer starting point
This baseline documents the Social Sign-on architecture. It does not claim that an OAuth authorization, token exchange, account link, login, or authenticated session has been exercised.
Ecosystem integration story
WordPress core
Athenian Social Sign-on extends native WordPress authentication instead of replacing it. It plugs into standard login screens, user creation, user meta, avatar rendering, and callback routing so stores retain WordPress compatibility while adding social identity flows.
WooCommerce
Within WooCommerce, the plugin improves account-access ergonomics by rendering social sign-in options in customer login flows and redirecting authenticated users back into account-oriented destinations. It helps reduce friction at the point where account access can directly affect checkout completion and repeat purchasing.
Athenian Secure API Key Manager
This is the plugin's most important Athenian ecosystem integration. Athenian Social Sign-on prefers provider credentials from SecureStore, can display masked secure configuration state in admin, and includes migration paths from local fallback values into centralized secret storage. That makes it a better fit for platform-managed deployments than generic social login plugins.
Custom storefronts and landing pages
Shortcode support allows teams to place Google and Facebook/Meta sign-in controls exactly where they want them. This is useful for branded login experiences, campaign pages, gated product experiences, and onboarding flows that do not rely solely on default WordPress templates.
2026-09-08 implementation update
Version 1.1.2 verifies Google signatures, binds provider callbacks to the initiating browser, validates Meta token identity, and supports explicit Connect Google/Facebook controls for signed-in users. Connections preserve local account data and never establish license ownership. See [current security, shortcode and validation details](social-connections-1.1.2.md).
Install
- Reviewed source folder: athenian-social-signon
- Plugin version reviewed: 1.1.6
- Local source inventory: 13 files (temporary, test, and Git metadata excluded).
- GitHub baseline: https://github.com/Athenian-Brands/athenian-social-signon at baseline/devdocs-1.1.6-20261006f / 3a9325e4e0bf0bc3bcc9748ad8600b4a3880fd45.
- WordPress and the configured identity provider.
- OAuth credentials, redirects, token validation, account creation, linking, and authenticated session behavior require separate verification.
Configuration
- Working positioning — see the linked technical reference excerpt.
- Executive summary — see the linked technical reference excerpt.
- Core marketing message — see the linked technical reference excerpt.
- The problem it solves — see the linked technical reference excerpt.
- What Athenian Social Sign-on does — see the linked technical reference excerpt.
- Ecosystem integration story — see the linked technical reference excerpt.
- Why this matters commercially — see the linked technical reference excerpt.
- Key differentiators — see the linked technical reference excerpt.
- Suggested messaging pillars — see the linked technical reference excerpt.
- Short-form copy options — see the linked technical reference excerpt.
- Sales narrative — see the linked technical reference excerpt.
- Best-fit use cases — see the linked technical reference excerpt.
- Positioning statement — see the linked technical reference excerpt.
- Platform-focused primary functionality copy — see the linked technical reference excerpt.
Usage
- Shortcodes detected in local PHP source: 8
- Static action/filter hooks detected in local PHP source: 15
- REST route registrations detected in local PHP source: 0
Shortcodes
- ath_facebook_login_button — athenian-social-sign-on.php
- ath_facebook_signin_link — athenian-social-sign-on.php
- ath_google_signin_link — athenian-social-sign-on.php
- ath_google_signin — athenian-social-sign-on.php
- facebook_login_button — athenian-social-sign-on.php
- facebook_signin_link — athenian-social-sign-on.php
- google_signin_link — athenian-social-sign-on.php
- google_signin — athenian-social-sign-on.php
REST Endpoints
- No register_rest_route calls were detected by the baseline scanner.
Hooks
- admin_init — athenian-social-sign-on.php
- admin_menu — athenian-social-sign-on.php
- admin_post_ath_sso_migrate_to_securestore — athenian-social-sign-on.php
- get_avatar_url — athenian-social-sign-on.php
- init — athenian-social-sign-on.php
- login_enqueue_scripts — athenian-social-sign-on.php
- login_form — athenian-social-sign-on.php
- login_head — athenian-social-sign-on.php
- pre_get_avatar_data — athenian-social-sign-on.php
- query_vars — athenian-social-sign-on.php
- template_redirect — athenian-social-sign-on.php
- woocommerce_login_form_end — athenian-social-sign-on.php
- wp_enqueue_scripts — athenian-social-sign-on.php
- wp_headers — athenian-social-sign-on.php
- wp_head — athenian-social-sign-on.php
Data Model
- Ecosystem integration story — described in the local technical reference.
API Reference
- Local source digest: 5a84277f206d23f29306acc9729f729e19decc50a71f7ce72bb853c509eb1366
- Repository URL: https://github.com/Athenian-Brands/athenian-social-signon
- Repository reference: baseline/devdocs-1.1.6-20261006f
- Repository commit: 3a9325e4e0bf0bc3bcc9748ad8600b4a3880fd45
Source files include: .gitignore, assets/js/google-frontend.js, athenian-social-sign-on.php, docs/athenian-platform-marketing.md, docs/athenian-platform-technical.md, docs/athenian-social-sign-on-marketing-document.md, docs/profile-capture.md, docs/security-1.1.4.md, docs/social-connections-1.1.2.md, docs/technical-marketing.md, includes/class-ath-sso-google-token.php, tools/security-identity-test.php, tools/verify-live-security.php
Troubleshooting
This baseline documents the Social Sign-on architecture. It does not claim that an OAuth authorization, token exchange, account link, login, or authenticated session has been exercised.
- Confirm the deployed plugin version, active dependencies, and current repository tree before using implementation details as a release contract.
Treat payment, carrier, vendor, shipment, inventory, account, credential, tax, AI, and external-provider behavior as integration-dependent until exercised in the target environment.
FAQ
What is this page intended to establish?
A versioned, product-linked starting point for iterative developer documentation. It combines the local implementation reference with a detected-code inventory and a committed GitHub baseline.
Is the linked repository baseline verified?
Yes. The repository URL, ref, and commit recorded on this page were verified from the clean GitHub baseline prepared for this documentation pass. That does not by itself prove fleet deployment parity.
What remains for release-grade documentation?
Reconcile the recorded source baseline with the deployed plugin version, then exercise the relevant authenticated, store, provider, payment, tax, carrier, or generated-artifact paths in the target environment.