Social Authentication Providers

Login 3.0 supports multiple social identity providers to enable seamless user authentication. This document outlines the available providers and their specific configuration requirements.

Supported Providers

Standard Providers

• Google

• Facebook

• Apple

• GitHub

• Discord

Regional Providers

• Kakao (Korea)

• WeChat (China)

• LINE (Japan, Korea, Thailand)

Messaging Providers

• WhatsApp

• Telegram

Provider-Specific Configuration

Kakao Login

Kakao is a popular social login provider in South Korea.

Configuration Requirements:

• Kakao Developer account

• Kakao App registration

• Redirect URI configuration

Implementation:

// Kakao-specific parameters
const kakaoParams = {
  response_type: 'code',
  client_id: 'YOUR_KAKAO_CLIENT_ID',
  redirect_uri: 'https://your-app.com/callback',
  provider: 'kakao',
  scope: 'profile_nickname,profile_image,account_email'
};

Available Scopes:

• profile_nickname - User's display name

• profile_image - User's profile image

• account_email - User's email address

WhatsApp Login

WhatsApp authentication enables users to log in using their WhatsApp account.

Configuration Requirements:

• WhatsApp Business Account

• Meta Developer account

• Phone number verification

Implementation:

// WhatsApp-specific parameters
const whatsappParams = {
  response_type: 'code',
  client_id: 'YOUR_WHATSAPP_CLIENT_ID',
  redirect_uri: 'https://your-app.com/callback',
  provider: 'whatsapp',
  scope: 'whatsapp_business_management'
};

WeChat Login

WeChat is the primary social platform in China, supporting both WeChat Web and WeChat Mini Program authentication.

Configuration Requirements:

• WeChat Developer account

• WeChat App registration

• ICP license (for China deployment)

Implementation:

// WeChat-specific parameters
const wechatParams = {
  response_type: 'code',
  client_id: 'YOUR_WECHAT_CLIENT_ID',
  redirect_uri: 'https://your-app.com/callback',
  provider: 'wechat',
  scope: 'snsapi_login'
};

Telegram Login

Telegram Login Widget allows users to authenticate using their Telegram account.

Configuration Requirements:

• Telegram Bot creation via @BotFather

• Domain verification

• Bot token configuration

Implementation:

// Telegram-specific parameters
const telegramParams = {
  response_type: 'code',
  client_id: 'YOUR_TELEGRAM_BOT_TOKEN',
  redirect_uri: 'https://your-app.com/callback',
  provider: 'telegram',
  scope: 'telegram_login'
};

Universal Authentication Flow

All social providers follow the same OAuth 2.0 flow:

GET https://auth3.upbond.io/authorize?
  response_type=code&
  client_id=${clientId}&
  redirect_uri=${redirectUri}&
  provider=${providerName}&
  scope=${requiredScopes}&
  state=${csrfToken}

Error Handling

Common error scenarios and their solutions:

Provider-Specific Errors

Kakao Errors:

• KOE101 - Invalid client ID

• KOE102 - Invalid redirect URI

• KOE103 - User denied permission

WhatsApp Errors:

• WAE101 - Business account not verified

• WAE102 - Phone number not registered

• WAE103 - Rate limit exceeded

WeChat Errors:

• WCE101 - Invalid App ID

• WCE102 - Unauthorized domain

• WCE103 - User not in whitelist (sandbox mode)

Telegram Errors:

• TGE101 - Invalid bot token

• TGE102 - Bot not configured for login

• TGE103 - Domain not authorized

Best Practices

1. Provider Selection: Choose providers based on your target audience's geographic location

2. Scope Management: Request only necessary permissions to improve user consent rates

3. Error Handling: Implement proper error handling for each provider's specific error codes

4. Fallback Options: Provide alternative authentication methods when social login fails

5. Privacy Compliance: Ensure compliance with regional privacy laws (GDPR, CCPA, etc.)

Regional Considerations

Korea (Kakao)

• High adoption rate among Korean users

• Requires Korean language support

• Privacy regulations compliance

China (WeChat)

• Mandatory for Chinese market

• Requires ICP license

• Great Firewall considerations

Messaging Apps (WhatsApp, Telegram)

• Global reach but varying adoption

• Consider user privacy preferences

• Rate limiting considerations

Configuration Support

For provider-specific configuration assistance, contact the UPBOND support team with:

• Target market information

• Required user data scopes

• Compliance requirements

• Integration timeline