Let users sign in to WordPress with trusted social and identity providers instead of creating another password.
Social Login lets users authenticate with an account they already have at a supported provider such as Google, Facebook, Microsoft, GitHub, LinkedIn, Discord, and others.
Social Login is included in VentraConnect Free for supported core WordPress login experiences. VentraConnect Pro extends the same authentication methods into supported WooCommerce, membership, LMS, community, comments, and other integration placements.
This guide covers:
- Supported Social Login providers
- How to enable a provider
- Provider credentials and callback URLs
- Existing-user matching and account linking
- Account creation and Guardrails
- Redirect behaviour
- Security and verified-email matching
- Testing Social Login end to end
Supported Social Login Providers
VentraConnect currently supports 16 Social Login providers:
You only need to enable the providers that make sense for your audience. Each provider is configured separately.
Enable a Social Login Provider
The exact credential names differ by provider, but the setup flow is generally the same.
Basic setup:
- Go to VentraConnect → Login Methods
- Select the Social Login provider you want to configure
- Create or open the corresponding application in that provider's developer dashboard
- Copy the callback / redirect URL shown by VentraConnect into the provider application
- Enter the provider credentials requested by VentraConnect
- Enable the provider
- Save the settings
- Test the login flow while logged out
Use the callback URL shown by VentraConnect for that provider. OAuth providers normally require the callback/redirect URI to match the configured application exactly.
Provider Credentials & Configuration
Most Social Login providers require you to create an application in their developer portal before users can authenticate on your WordPress site.
Provider dashboards use different terminology and setup screens. Use the dedicated Social Login Providers & Configuration guide for provider-specific setup details.
Existing Users & Account Linking
When a Social Login provider returns a trusted identity, VentraConnect can authenticate or link that identity to the appropriate WordPress user according to the provider data and VentraConnect's account-matching rules.
Do not create duplicate accounts as a workaround for a linking problem. If an existing user cannot authenticate with a provider, troubleshoot the account match or provider identity first.
Account Creation & Guardrails
Social Login behaves differently from Magic Link and Email OTP when it comes to method-level registration controls.
The master account-creation control has priority on the default login surfaces it governs. If new account creation is disabled there, Social Login can authenticate existing users but must not create a new user from that login surface.
Social Login Security & Verified Email Matching
VentraConnect hardened Social Login account matching in Free v1.4.4.
This hardening reduces the risk of linking a Social Login identity to an existing WordPress account based only on an email address the provider has not explicitly confirmed as verified.
Redirects After Social Login
Social Login can use VentraConnect's normal redirect system after authentication.
Where Social Login Appears
Placement controls where the provider button appears. Account-creation rules are a separate concern and are governed by VentraConnect Guardrails and the surrounding registration flow.
Test Social Login End to End
Recommended test:
- Test while logged out in a private/incognito browser session
- Click the configured provider button
- Authenticate at the provider
- Confirm the provider returns to your WordPress site successfully
- Confirm the correct existing user is authenticated when testing an existing account
- Confirm the Social Login identity is linked as expected
- Confirm the post-login redirect is correct
- Test a new provider account separately if new account creation is intentionally allowed
- Test the same provider on each integration placement you intend to use
Do not test only while already signed in to the provider and WordPress. Use a clean browser session when validating the full OAuth flow.
