How to set up ET Social Login with Twitter?

  1. To create an application you have to be logged in under your own account or create a new one on twitter.com.

  2. You can create a new application on the developers website. A step-by-step manual with screenshots is available below.

    1. Create a new application on the developers site.

      Image 1. New application
      Image 1. New application
    2. Fill the form.

      Image 2. New application form
      Image 2. New application form
      You can find the Callback URL in the extension settings in the admin panel of your website.
      Name — This name will be displayed to the customer when he uses Google authorization on your website.
    3. Read and agree to the twitter developer agreement. Click "Create your Twitter application".

      Image 3. Developer agreement
      Image 3. Developer agreement
    4. Set up the application permissions. We recommend using minimal permissions — only to read user information.

      Image 4. Setting up the permissions
      Image 4. Setting up the permissions
    5. Go to "Keys and Access Tokens" tab. Here you can find the necessary parameters to set up the extension. You can confirm permission here too.

      Image 5. Consumer key and Consumer Secret
      Image 5. Consumer key and Consumer Secret
  3. Copy the Consumer Key (API Key) and Consumer Secret (API Secret) from the application settings into the ET Social Login settings in the admin panel.

    Image 6. Extension settings
    Image 6. Extension settings
  4. We recommend you to fill the Special Notes field with the information about the social network account. E.g. email or name of the person who was creating the application. We had a lot of cases when shop owners wanted to make some changes and found out that they don't remember which account owns the application, so they were forced to create a new one.

    Image 7. Application information
    Image 7. Application information
  5. Everything is ready. You can check how it works on your website now.

Last modify date: Thursday, October 20, 2016