Social / OAuth logins
Accounts & logins
Social / OAuth logins
VulaSocial uses Socialstream to support GitHub, Google, Facebook, Twitter/X, LinkedIn and GitLab as login providers. Members can sign in with their social account in addition to (or instead of) email + password.
How configuration works
Providers are enabled per-provider. Each needs an OAuth app from the
provider with a Client ID, a Client Secret and a redirect URI.
Credentials are read from the services.* config (populated from .env) and
can be overridden via settings if an admin UI for them is present on your
version.
1. Create an OAuth app at the provider
| Provider | Console | Redirect URI |
|---|---|---|
| GitHub | github.com/settings/developers | https://your-node.example/oauth/github/callback |
| console.cloud.google.com → Credentials | https://your-node.example/oauth/google/callback |
|
| developers.facebook.com | https://your-node.example/oauth/facebook/callback |
|
| Twitter/X | developer.twitter.com | https://your-node.example/oauth/twitter-oauth-2/callback |
| linkedin.com/developers | https://your-node.example/oauth/linkedin-openid/callback |
|
| GitLab | gitlab.com → Applications | https://your-node.example/oauth/gitlab/callback |
Note the redirect paths above — each provider's
servicesKey()maps to these exact callbacks (Twitter usestwitter-oauth-2, LinkedIn useslinkedin-openid).
2. Add the credentials to .env
GITHUB_CLIENT_ID=...
GITHUB_CLIENT_SECRET=...
GITHUB_REDIRECT_URI=/oauth/github/callback
GOOGLE_CLIENT_ID=...
GOOGLE_CLIENT_SECRET=...
GOOGLE_REDIRECT_URI=/oauth/google/callback
FACEBOOK_CLIENT_ID=...
FACEBOOK_CLIENT_SECRET=...
FACEBOOK_REDIRECT_URI=/oauth/facebook/callback
TWITTER_CLIENT_ID=...
TWITTER_CLIENT_SECRET=...
TWITTER_REDIRECT_URI=/oauth/twitter-oauth-2/callback
LINKEDIN_CLIENT_ID=...
LINKEDIN_CLIENT_SECRET=...
LINKEDIN_REDIRECT_URI=/oauth/linkedin-openid/callback
GITLAB_CLIENT_ID=...
GITLAB_CLIENT_SECRET=...
GITLAB_REDIRECT_URI=/oauth/gitlab/callback
3. Clear config
php artisan config:clear
4. Enable the provider in the app
The login page shows the social buttons for enabled providers. If you don't see
one after configuring it, confirm the provider is registered in
config/socialstream.php → providers (Socialstream's default list) and that
socialstream.providers resolves to your chosen providers.
5. Test
- Log out, then log in via the social button for each enabled provider.
- Confirm the redirect round-trips to the callback and creates/logs in the member.
Notes
- First social login may create a new account if none matches the email.
- Linking accounts — if a member already has an email account, they can connect a social provider from their profile/settings (Socialstream's connected-accounts feature).
- Redirect URIs must match exactly including scheme and port, or the provider will reject the callback.
Troubleshooting
| Symptom | Likely fix |
|---|---|
redirect_uri_mismatch |
Callback path in the provider console ≠ servicesKey() here |
invalid_client |
Wrong client ID/secret, or not cleared config after .env edit |
| Button doesn't appear | Provider not in socialstream.providers, or feature disabled |
Related
Still stuck? Contact the node administrator.