This page is a step-by-step guide for the process of opening and setting up an external application in LINE as part of the Gigya Setup process.

This page is a step-by-step guide for the process of opening and setting up an external application in LINE as part of the Gigya Setup process.


Phase 1 - Creating Your Application In LINE

You must be a LINE Partner in order to create an application. You can apply to become a Partner here.

Optional: If you are planning on configuring a domain alias (CNAME), please insert your alias subdomain (CNAME value) instead of '' and your domain instead of Gigya's domain. i.e., https://[YOUR-ALIAS-SUB-DOMAIN] in the Authorized Redirect URLs field of the Authentication page.

  1. Log into LINE by going to and click the Channels button in the top right-hand corner of the page.

  2. You will be directed to the login page.

  3. Once logged in, click the Channels button from Step 1 again.
    Here you will be able to access any existing apps and create new ones.
  4. Click Add a new Channel from the top left-hand menu.

  5. Complete the following fields:
  6. After clicking Save you will be returned to the app page and see the following notice.

  7. At the bottom of the page there is now a Submit button that you need to press to complete the process.

  8. Once you click the Submit button you will be presented with a popup:

  9. Fill in the comment section and press Submit.
  10. If you did not incur any errors your app will now be created, however, you will need to return to the Channels page to view the app out of 'Review' status. 


Phase 2 - Additional LINE Configuration

When selecting your new app from the top left-hand menu of the Channels page on the LINE website you will now be able to edit additional configurations.

Basic Information

Navigating to the Basic information tab you will be able to retrieve your Channel ID and Channel Secret, which will be needed in Phase 3 - Configuring LINE's Application in Gigya's Console.

Technical Configuration

In the Technical configuration tab you will see the specifications of your app.

The Technical configuration tab is where you will define your Authorized Redirect URL's using the Edit button and entering them one per line.

If you are using a CName, be sure to include the correct URI in this field. The below screenshot is just an example.

Redirect URI format:


On the Roles tab you will be able to view the roles for users with access to your app, as well as add additional users.

Any user you wish to add must have a LINE User ID.


View Statistics

On the View statistics tab you can view the specific stats for your app within a given time frame.


Developement Of Your App

While your app is in Development status, you add users via the Roles tab described above, in order for them to have access to the app.

Once you move the Status of your app to PUBLISHED (described below) it will become Live and visible/usable to all.

Moving Your App To Production

  1. When the development mode of your application is complete, login to your LINE account and return to the Channels section as described above.
  2. Navigate to the particular app you want to move to production from the left-hand menu (if you have more than one).
  3. Press the EDIT button.

  4. Here you can adjust the Status of your app.

  5. Once changed, press the SAVE button. Your app is now live. 

Phase 3 - Configuring Line's Application Keys in Gigya's Console

  1. Open the Providers Configuration page of Gigya's Console.
  2. Select Line from the list of providers.

  3. Paste the Channel ID and Channel Secret from the beginning of Phase 2 in to the corresponding fields. 
  4. Select Secure redirects only to allow only HTTPS redirects from Line. 
  5. Click OK and then click Save Settings on the lower right-hand corner.


That's it, Line configuration is complete! Please note that it can take up to 10 minutes for any changes to synchronize with LINE.

Additional Information

When using LINE as a login provider via socialize.login or accounts.showScreenSet on a mobile device, only authflow 'redirect' is supported, e.g.,

var params = {
    callback: onLogin,