Skip to main content

Social Apps

Configure OAuth providers to enable social login for your applications.

Overview​

Social Apps allows you to set up third-party authentication providers like Google, GitHub, Microsoft, and others. Users can sign in to your application using their existing accounts from these providers, simplifying the login experience.

Concepts​

OAuth Provider​

A third-party authentication service that allows users to sign in using existing credentials. Common providers include Google, GitHub, Microsoft, Facebook, and Apple.

Client ID and Secret​

Credentials provided by the OAuth provider when you register your application. These are used to authenticate your app with the provider.

Auto Redirect​

When enabled, users are automatically redirected to the OAuth provider's login page instead of showing the application's login form.

View Social Apps​

  1. Navigate to your Site in the Dashboard.
  2. Click the Settings tab.
  3. Click Social Apps in the Access section.
  4. View the list of configured OAuth providers.

The list displays:

  • Provider: The OAuth provider icon and name
  • Name: Your custom name for the configuration
  • Status: Whether the provider is properly configured
  • Auto: Whether auto-redirect is enabled

Add an OAuth Provider​

  1. Navigate to Site Settings > Social Apps.
  2. Click Add Provider.
  3. Select the OAuth provider from the dropdown.
  4. Fill in the configuration:
    • Name: A custom name for this configuration
    • Client ID: The client ID from the provider
    • Client Secret: The client secret from the provider
    • Scopes: Permission scopes to request (provider-specific)
    • Auto Redirect: Enable to redirect users automatically
  5. Click Create.

Supported Providers​

ProviderDescription
GoogleSign in with Google accounts
GitHubSign in with GitHub accounts
MicrosoftSign in with Microsoft/Azure AD accounts
FacebookSign in with Facebook accounts
AppleSign in with Apple ID
LinkedInSign in with LinkedIn accounts
TwitterSign in with Twitter/X accounts
DiscordSign in with Discord accounts
Custom OIDCAny OpenID Connect compliant provider

Configure a Provider​

Google​

  1. Go to Google Cloud Console.
  2. Create or select a project.
  3. Navigate to APIs & Services > Credentials.
  4. Create an OAuth 2.0 Client ID.
  5. Add your redirect URI: https://your-site.taruvi.cloud/auth/callback/google
  6. Copy the Client ID and Client Secret.

GitHub​

  1. Go to GitHub Developer Settings.
  2. Click New OAuth App.
  3. Set the Authorization callback URL: https://your-site.taruvi.cloud/auth/callback/github
  4. Copy the Client ID and generate a Client Secret.

Microsoft​

  1. Go to Azure Portal.
  2. Navigate to Azure Active Directory > App registrations.
  3. Create a new registration.
  4. Add the redirect URI: https://your-site.taruvi.cloud/auth/callback/microsoft
  5. Copy the Application (client) ID and create a Client Secret.

View Provider Details​

  1. Click on a provider in the Social Apps list.
  2. View the full configuration details:
    • Configuration status
    • Connected user count
    • Scopes and settings
    • Last updated date

Edit a Provider​

  1. Click the Edit (pencil) icon on the provider row.
  2. Update the configuration fields.
  3. Click Save Changes.
note

Changing the Client ID or Secret may require users to re-authenticate.

Delete a Provider​

  1. Click the Delete (trash) icon on the provider row.
  2. Review the warning about connected users.
  3. Confirm deletion.
warning

Deleting a provider will prevent users who only have that authentication method from signing in. Ensure affected users have alternative login methods first.

Configuration​

Provider Fields​

FieldDescriptionRequired
ProviderThe OAuth provider typeYes
NameCustom name for the configurationYes
Client IDOAuth client identifierYes
Client SecretOAuth client secretYes
ScopesPermission scopes to requestNo
Auto RedirectAutomatically redirect to providerNo

Custom OIDC Fields​

For custom OpenID Connect providers:

FieldDescription
Authorization URLOAuth authorization endpoint
Token URLToken exchange endpoint
User Info URLUser profile endpoint
JWKS URLJSON Web Key Set URL

Limits​

ResourceLimit
Social apps per site20
Scopes per provider50

Troubleshooting​

Login fails with redirect error​

Problem: Users see a redirect URI error when trying to log in.

Solution:

  1. Verify the redirect URI in your provider settings matches exactly.
  2. Check for trailing slashes.
  3. Ensure HTTPS is used.

Cannot delete provider with users​

Problem: Deletion is blocked because users are connected.

Solution:

  1. Review how many users use this provider.
  2. Ensure users have alternative login methods.
  3. Force delete if necessary (users will need to create new accounts).

Provider shows "Not Configured"​

Problem: Status shows the provider is not properly configured.

Solution:

  1. Verify Client ID and Secret are correct.
  2. Check that required scopes are added.
  3. Test the configuration by attempting a login.

Last Updated: January 2025