Configure provider applications, credentials, callback URLs, and testing for VentraConnect Social Login.
Each Social Login provider requires its own application or developer configuration before users can authenticate with it on your WordPress site.
This guide covers:
- The shared provider setup process
- Application / Client IDs and secrets
- Callback and redirect URLs
- Enabling providers in VentraConnect
- Testing provider authentication
- The 16 providers supported by VentraConnect
- Common configuration mistakes
How Provider Setup Works
Although each provider has its own developer dashboard and terminology, the general setup process is similar.
Typical setup flow:
- Create or open an application in the provider's developer portal
- Copy the callback / redirect URL shown by VentraConnect
- Add that URL to the provider application's allowed callback or redirect settings
- Copy the provider credentials into VentraConnect
- Enable the provider
- Save the settings
- Test the complete login flow while logged out
The exact field names vary by provider. For example, one provider may use Client ID while another uses App ID. Use the field labels shown in VentraConnect and the provider dashboard as your source of truth.
Provider Credentials
Most Social Login providers require credentials that identify your WordPress site or provider application.
Keep provider secrets private. Do not publish Client Secrets or App Secrets in documentation, screenshots, support forums, or public code repositories.
Callback / Redirect URL
The callback URL is the address the provider sends the user back to after they authenticate.
The callback URL usually needs to match exactly. A different domain, protocol, path, trailing slash, or environment can cause the provider to reject the login request.
If you have separate staging and production sites, treat them as separate environments and make sure the provider configuration matches the site you are actually testing.
Enable the Provider in VentraConnect
In WordPress:
- Go to VentraConnect → Login Methods
- Select the provider you want to configure
- Enter the credentials required for that provider
- Confirm the callback / redirect URL matches the provider application
- Turn the provider Active
- Save your changes
You can enable only the providers that make sense for your site. There is no requirement to activate all supported providers.
Supported Providers
VentraConnect currently supports 16 Social Login providers:
Provider dashboards and approval requirements can change independently of VentraConnect. Always follow the current configuration requirements shown by the provider when creating or editing its application.
Test the Provider End to End
Recommended test:
- Open a private/incognito browser window
- Go to the WordPress login surface where the provider is enabled
- Click the provider button
- Confirm you are sent to the correct provider
- Authenticate with a test provider account
- Confirm the provider returns to your WordPress site
- Confirm the correct WordPress account is authenticated or created according to your account-creation rules
- Confirm the post-login redirect is correct
- Repeat the test on each Pro integration placement you intend to use
Test with a clean browser session. Existing provider and WordPress sessions can hide problems that only appear during a fresh OAuth login.
Common Configuration Problems
Provider Setup vs Account-Creation Rules
Configuring a provider controls whether Social Login can authenticate through that provider. It does not by itself decide whether a new WordPress account may be created.
Social Login does not use the Magic Link / Email OTP Login Only / Login & Register selector. On standard login surfaces, its account-creation behaviour follows the master account-creation control.
