LINE OAuth Provider

Descope allows you to create custom Social Login (OAuth) providers within the Authentication Methods page. This allows you to add any Social OAuth authentication within your application. This guide specifically covers the step by step configuration of a custom Line OAuth provider.

Creating the LINE Application

Before creating the custom OAuth provider within the Descope console, you must create and configure an application within your LINE developer account. You can follow the Line Login Integration Guide for details on creating your application.

When you create your app within Line, you must configure the redirect URI. Set the redirect URI to be https://<your-base-url>/v1/oauth/callback. You can find your project's base url in our Multi-Region Support Guide.

Creating Descope Custom Provider

You can configure a custom provider in the Descope Console. Under Authentication Methods -> Social Login, select + Add custom provider in the top right corner. You can then set the name (in this case, "Line"), logo, and description for your custom provider.

Create custom provider

Configure Account Settings

Within the account settings section of your provider, you will configure the following items:

  • Client ID: This is the Channel ID of the application created within Line
  • Client Secret: This is the Channel Secret of the application created within Line
  • Scopes: These are the configured scopes granted to Descope for the user within Line. Scopes provides Line users using third-party apps the confidence that only the information they choose to share will be shared. Line’s Docs specify the available scopes that can be requested
  • Authorized Grant Type:
    • Authorization Code: Recommended. Uses standard query/form response modes.
    • Implicit: Only if required; typically not recommended for new integrations.

Custom Line OAuth provider account settings configured within Descope

Configure Connection Settings

Within the connection settings section of your provider, you will configure the following items:

  • Authorization Endpoint: The endpoint to request authorization from the user. For LINE, this endpoint is https://access.line.me/oauth2/v2.1/authorize.
  • Token Endpoint: The endpoint to exchange the authorization code for an access token. For LINE this endpoint is https://api.line.me/oauth2/v2.1/token.
  • User Info Endpoint: The endpoint to get user details for attribute mapping. For LINE, this endpoint is https://api.line.me/v2/profile.

Custom Line OAuth provider user attribute mapping configured within Descope

Configure User Attribute Mapping

Given the openid and profile scopes, Descope can capture any items from the user info endpoint response.

However, capturing additional profile information (name, gender, birthday, phone number, address) that users have registered with LINE Profile+, would require you to undergo an application process with Line, see LINE Profile+ for more details.

Custom Line OAuth provider user attribute mapping configured within Descope

For more OAuth provider settings information, check out the OAuth Settings Guide.

To add Line Social Login to your flow, check out our Social Login In Flows Guide.

Was this helpful?

On this page