News: Articles for #LINE Login

  • 2019/12/06

    New LINE Login notification message

    When a user logs in to a site that uses LINE Login v2.1, the content of the notification from the Official LINE account will be different.

    Before, the notification differed depending on the login method that was used. Starting December 9th, 2019, the notification content will be consistent regardless of how the user logs in.

    LINE Login notification message

    Successful login

    We've detected a login to X on Y (Z).
    IP address: {ip_address}
    Location: {Location}
    If this wasn't you, you can log out here: {device_link}
    We also recommend changing your password via the following link: {help_link}

    Failed login

    We've detected an unsuccessful login attempt to X on Y (Z).
    IP address: {ip_address}
    Location: {Location}
    If this wasn't you, you can check which devices are logged into your account here: {device_link}
    We also recommend changing your password via the following link: {help_link}

    Note that (Z) represents a URL and may sometimes be omitted.

    Target users

    For all LINE users that log in to a site using LINE Login v2.1.

  • 2019/10/25

    New ID token verification endpoint released

    When your back-end server receives an ID token originating from LINE Login v2.1 or the LINE SDK, you should verify that the ID token is authentic.

    Previously, you had to use a JWT library or write your own decoding and verification code.

    After this release, you merely have to send an HTTP request to the verification endpoint to determine if an ID token is authentic.

    For instructions on verifying ID tokens, read Transfer ID token to back-end server.

  • 2019/09/26

    Notice about system maintenance

    We're performing system maintenance at the below time. We apologize for any inconvenience.

    Scheduled maintenance time

    September 26, 2019 16:20-16:50 JST (+9 GMT)

    The maintenance will only last a few seconds and will take place somewhere in this time window.

    Impact

    Messaging API, LINE Login, and LIFF operations may result in errors. Specifically, the following events can occur:

    • Messaging API (https://api.line.me/v2/bot/*) returns an error with status code 500.
    • An error with status code 500 is returned when a user logs in with LINE Login or starts a LIFF app.
  • 2019/09/13

    LINE SDK v4.x end-of-life on December 12th, 2019

    December 12th, 2019 marks the end-of-life date for LINE SDK v4.0 for Android and LINE SDK v4.1 for iOS (from hereon collectively called LINE SDK v4.x). On that date, we'll remove from this site the following things:

    Why we're doing this

    To ensure a consistent, secure, up-to-date experience for LINE users, our partners' apps and services should use the latest version of our technology. We already marked LINE SDK v4.x as deprecated some time ago, but continued to offer documentation and download links as a courtesy to partners who couldn't upgrade on short notice. Now we're taking the next logical step: declaring LINE SDK v4.x end-of-life and removing all references from our site.

    Upgrading to a new SDK version

    What you need to do to upgrade depends on what version you're currently using.

    From To Notes
    LINE SDK v4.x for iOS Objective-C LINE SDK v5.2 for iOS Swift The old and new versions use different programming languages, which makes migrating a big task. We hope the migration instructions in Upgrading the SDK will make it easier.
    LINE SDK v4.x for Android LINE SDK v5.1 for Android There are minor differences between the old and new version, particularly with relation to how login works. The page Integrating LINE Login with your Android app explains how to integrate the latest version.
    LINE SDK v3.x for iOS Objective-C LINE SDK v5.2 for iOS Swift There are major differences between the old and new version, meaning you'll have to redo your integration from scratch. See Integrating LINE Login with your iOS app for instructions.
    LINE SDK v3.x for Android LINE SDK v5.1 for Android There are major differences between the old and new version, meaning you'll have to redo your integration from scratch. See Integrating LINE Login with your Android app for instructions.
  • 2019/07/18

    Notice about service outage for LINE Login (resolved)

    We want to inform you about a service outage regarding LINE Login. The issue has now been resolved. We apologize for any inconvenience this may have caused.

    Date and time of outage

    Date: July 18, 2019 Time: 9:38–10:40 JST (GMT+9)

    Cause

    Issue with our servers.

    Details

    LINE Login returned http error codes with the pattern 5xx (500, 501, etc.) for some requests. As a result, LINE Login was unavailable in the following applications:

    • Web application
    • Desktop app

    LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

  • 2019/06/27

    LINE SDK for Flutter released

    We've released a new LINE SDK for Flutter. This SDK is a Flutter plugin that lets you access the functions of LINE SDK for iOS and LINE SDK for Android in your Flutter app with Dart. For details, see these pages:

    The LINE SDK for Flutter documentation is only available in English, for now.

  • 2019/06/26

    LINE Login: new parameters and properties added

    We've added new parameters and properties to LINE Login v2.1:

    • The parameter ui_locales lets you specify the display language and script for LINE Login.
    • The property amr specifies the authentication methods used in authentication. This corresponds to the OpenID Connect 1.0 amr Claim.

      The amr property is automatically added to all LINE login v2.1 enabled channels, so no additional development work is required.

    See also Integrating LINE login with your web app. If you haven't integrated LINE Login yet, we hope you'll consider doing so now.

    note Note

    New or changed LINE Login functions may cause changes in the structure of the payload JSON object. These changes may include added properties, variations in property order, and added/removed white space and line breaks. Make sure your implementation can handle both current and future payload data objects.

    Any functionality we offer may be changed without notice. However, we'll try notify you in advance if we believe that the change will significantly affect developers.

  • 2019/06/17

    Notice about service outage for LINE Login (resolved)

    We'd like to inform you about a service outage regarding LINE Login. The issue has now been resolved. We apologize for any inconvenience that this may have caused.

    Date and time of outage

    Date: June 17, 2019 Time: 11:41–13:01 JST (GMT+9)

    Cause

    Issue with our servers.

    Details

    LINE Login returned error code "400 Bad Request" when some users attempted to log in.

    LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

  • 2019/03/01

    Notice about system maintenance

    We will perform maintenance for LINE Login and the Social API. We apologize for any inconvenience caused by this.

    Scheduled maintenance time

    March 05, 2019 05:30-06:30 JST (+9 GMT)

    Impact

    API operations using the access token for LINE Login 2.0 and the Social API 2.0 can be interrupted for 30 seconds to 1 minute.

    This maintenance will not affect API operations using the access token for LINE Login 2.1 and the Social API 2.1.

  • 2019/03/01

    Notice about service outage for LINE Login and the Social API (resolved)

    We'd like to inform you about a service outage regarding LINE Login and the Social API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

    Date and time of outage

    Date: February 26, 2019

    Time: 6:46–7:16 JST (GMT+9)

    Cause of the outage

    Issue with our servers.

    Details

    HTTP status code 500 was sometimes returned when requests were sent to the LINE Login and Social APIs.

    We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.