Social Login

Social login is an authentication method that lets a person sign in to a service using an account they already hold with a provider such as Facebook, Google, Apple, or LinkedIn. Instead of creating a new username and password, the user authorises the provider to confirm their identity and share agreed profile fields with the service, using the OAuth 2.0 authorisation framework, usually with OpenID Connect layered on top for identity.

How the flow works

1. The user taps "Continue with Google" (or another provider) and is redirected to the provider's own sign-in page.
2. The provider authenticates the user and shows exactly which fields will be shared (typically name and email).
3. On approval, the provider sends an authorisation code back to the service, which exchanges it for a token and reads the agreed profile fields.
4. The service creates or matches the account - no new password ever exists for the user to forget or reuse.

Social login on captive portals

On guest WiFi, social login lives on the splash page as an alternative to the email form. The complication is that the guest is not yet online, so the network's walled garden must allow the provider's authentication domains before sign-in completes. When social login "spins forever" on a portal, a missing walled-garden entry is the usual cause.

Advantages and limitations

• Less friction - one or two taps, no typing, which raises completion and opt-in rates on splash pages.
• Verified data - the email comes from a real, active account rather than a hand-typed field.
• Provider dependency - available fields and policies are set by the provider and change over time, so services should always keep a plain email path as a fallback.