Every app needs authentication and authorization. Logto is an Auth0 alternative designed for modern apps and SaaS products.
In this article, we will go through the steps to quickly build the Naver sign-in experience (user authentication) with Flutter and Logto.
Prerequisites
- A running Logto instance. Check out the introduction page to get started.
- Basic knowledge of Flutter.
- A usable Naver account.
Create an application in Logto
In you browser, open a new tab and enter the link of Logto Admin Console.
Once the page is loaded, in the "Get Started" section click the View all
link to open the application framework list page.
Choose your application type
In the opening modal, scroll to the "Native app" section or filter all the available " Native app" frameworks using the quick filter checkboxes on the left.
Click the "Flutter" framework card to start creating your application.
Enter application name
Enter the application name, e.g., "Bookstore," and click "Create application."
🎉 Ta-da! You just created your first application in Logto. You'll see a congrats page which includes a detailed integration guide. Follow the guide to see what the experience will be in your application.
Integrate Logto SDK
- The SDK package is available on pub.dev and Logto GitHub repository.
- The sample project is built using Flutter material. You can find it on pub.dev and our GitHub repository.
- The SDK is compatible with Android, and iOS platforms only.
- The SDK v1.x is compatible with Dart 2.x. For SDK v2.x, you need to update your Dart version to 3.x or higher.
Installation
- pub.dev
- GitHub
You can install the logto_dart_sdk package
directly using the pub package manager.
Run the following command under your project root:
flutter pub get logto_dart_sdk
If you prefer to fork your own version of the SDK, you can clone the repository directly from GitHub.
git clone https://github.com/logto-io/dart
Modules
The logto_dart_sdk
includes two main modules:
-
logto_core.dart This core module provides the basic functions and interfaces for the Logto SDK.
-
logto_client.dart This client module offers a high-level Logto client class for interacting with the Logto server.
Dependency and configurations
Dependency and configurations
This SDK has the following dependencies, some require additional configurations:
flutter_secure_storage
We use flutter_secure_storage to implement the cross-platform persistent secure token storage.
- Keychain is used for iOS
- AES encryption is used for Android.
Config Android version
Set the android:minSdkVersion to 18 in your project's android/app/build.gradle file.
android {
...
defaultConfig {
...
minSdkVersion 18
...
}
}
Disable autobackup
By default Android may backup data on Google Drive automatically. It can cause exception java.security.InvalidKeyException:Failed to unwrap key
.
To avoid this, you can disable auto backup for your app or exclude sharedprefs
from the FlutterSecureStorage
.
-
To disable auto backup, go to your app manifest file and set the
android:allowBackup
andandroid:fullBackupContent
attributes tofalse
.AndroidManifest.xml<manifest ... >
...
<application
android:allowBackup="false"
android:fullBackupContent="false"
...
>
...
</application>
</manifest> -
Exclude
sharedprefs
fromFlutterSecureStorage
.If you need to keep the
android:fullBackupContent
for your app rather than disabling it, you can exclude thesharedprefs
directory from the backup. See more details in the Android documentation.In your AndroidManifest.xml file, add the android:fullBackupContent attribute to the
<application>
element, as shown in the following example. This attribute points to an XML file that contains backup rules.AndroidManifest.xml<application ...
android:fullBackupContent="@xml/backup_rules">
</application>Create an XML file called
@xml/backup_rules
in theres/xml/
directory. In this file, add rules with the<include>
and<exclude>
elements. The following sample backs up all shared preferences except device.xml:@xml/backup_rules<?xml version="1.0" encoding="utf-8"?>
<full-backup-content>
<exclude domain="sharedpref" path="FlutterSecureStorage"/>
</full-backup-content>
Please check flutter_secure_storage for more details.
flutter_web_auth
flutter_web_auth is used behind Logto's flutter SDK. We rely on its webview-based interaction interface to authenticate users.
This plugin uses ASWebAuthenticationSession
on iOS 12+ and macOS 10.15+, SFAuthenticationSession
on iOS 11, Chrome Custom Tabs
on Android and opens a new window on Web.
Register the callback url on Android
In order to capture the callback url from Logto's sign-in web page, you will need to register your sign-in redirectUri to your AndroidManifest.xml
file.
<activity android:name="com.linusu.flutter_web_auth.CallbackActivity" android:exported="true">
<intent-filter android:label="flutter_web_auth">
<action android:name="android.intent.action.VIEW"/>
<category android:name="android.intent.category.DEFAULT"/>
<category android:name="android.intent.category.BROWSABLE"/>
<data android:scheme="io.logto"/>
</intent-filter>
</activity>
http.dart
Since the SDK need to make network requests, you will need to pass in a HTTP client to the SDK. You can use the default http.Client
from http.dart or create your own http.Client
with custom configurations.
import 'package:http/http.dart' as http;
Integration
Init LogtoClient
Import the logto_dart_sdk
package and initialize the LogtoClient
instance at the root of your application.
import 'package:logto_dart_sdk/logto_dart_sdk.dart';
import 'package:http/http.dart' as http;
void main() async {
WidgetsFlutterBinding.ensureInitialized();
runApp(const MyApp());
}
class MyApp extends StatelessWidget {
const MyApp({Key? key}) : super(key: key);
Widget build(BuildContext context) {
return const MaterialApp(
title: 'Flutter Demo',
home: MyHomePage(title: 'Logto Demo Home Page'),
);
}
}
class MyHomePage extends StatefulWidget {
const MyHomePage({Key? key, required this.title}) : super(key: key);
final String title;
State<MyHomePage> createState() => _MyHomePageState();
}
class _MyHomePageState extends State<MyHomePage> {
late LogtoClient logtoClient;
void render() {
// state change
}
// LogtoConfig
final logtoConfig = const LogtoConfig(
endpoint: "<your-logto-endpoint>",
appId: "<your-app-id>"
);
void _init() {
logtoClient = LogtoClient(
config: logtoConfig,
httpClient: http.Client(), // Optional http client
);
render();
}
void initState() {
super.initState();
_init();
}
// ...
}
Implement sign-in
Before we dive into the details, here's a quick overview of the end-user experience. The sign-in process can be simplified as follows:
- Your app invokes the sign-in method.
- The user is redirected to the Logto sign-in page. For native apps, the system browser is opened.
- The user signs in and is redirected back to your app (configured as the redirect URI).
Regarding redirect-based sign-in
- This authentication process follows the OpenID Connect (OIDC) protocol, and Logto enforces strict security measures to protect user sign-in.
- If you have multiple apps, you can use the same identity provider (Logto). Once the user signs in to one app, Logto will automatically complete the sign-in process when the user accesses another app.
To learn more about the rationale and benefits of redirect-based sign-in, see Logto sign-in experience explained.
Before starting, you need to add a redirect URI in the Admin Console for your application.
Let's switch to the Application details page of Logto Console. Add a Redirect URI io.logto://callback
and click "Save changes".
- For iOS, the redirect URI scheme does not really matter since the
ASWebAuthenticationSession
class will listen to the redirect URI regardless of if it's registered. - For Android, the redirect URI scheme must be registered in the
AndroidManifest.xml
file.
After the redirect URI is configured, we add a sign-in button to your page, which will call logtoClient.signIn
API to invoke the Logto sign-in flow:
class _MyHomePageState extends State<MyHomePage> {
// ...
final redirectUri = 'io.logto://callback';
Widget build(BuildContext context) {
// ...
Widget signInButton = TextButton(
onPressed: () async {
await logtoClient.signIn(redirectUri);
render();
},
child: const Text('Sign In'),
);
return Scaffold(
appBar: AppBar(
title: Text(widget.title),
),
body: Center(
child: Column(
mainAxisAlignment: MainAxisAlignment.center,
children: <Widget>[
SelectableText('My Demo App'),
signInButton,
],
),
),
);
}
}
Implement sign-out
Now let's add a sign-out button on the main page so users can sign out from your application.
class _MyHomePageState extends State<MyHomePage> {
// ...
Widget build(BuildContext context) {
// ...
Widget signOutButton = TextButton(
onPressed: () async {
await logtoClient.signOut();
render();
},
child: const Text('Sign Out'),
);
return Scaffold(
appBar: AppBar(
title: Text(widget.title),
),
body: Center(
child: Column(
mainAxisAlignment: MainAxisAlignment.center,
children: <Widget>[
SelectableText('My Demo App'),
signInButton,
signOutButton,
],
),
),
);
}
}
Handle authentication status
Logto SDK provides an asynchronous method to check the authentication status. The method is logtoClient.isAuthenticated
. The method returns a boolean value, true
if the user is authenticated, otherwise false
.
In the example we conditionally render the sign-in and sign-out buttons based on the authentication status. Now let's update the render
method in our Widget to handle the state change:
class _MyHomePageState extends State<MyHomePage> {
// ...
bool? isAuthenticated = false;
void render() {
setState(() async {
isAuthenticated = await logtoClient.isAuthenticated;
});
}
Widget build(BuildContext context) {
// ...
return Scaffold(
appBar: AppBar(
title: Text(widget.title),
),
body: Center(
child: Column(
mainAxisAlignment: MainAxisAlignment.center,
children: <Widget>[
SelectableText('My Demo App'),
isAuthenticated == true ? signOutButton : signInButton,
],
),
),
);
}
}
Checkpoint: Test your application
Now, you can test your application:
- Run your application, you will see the sign-in button.
- Click the sign-in button, the SDK will init the sign-in process and redirect you to the Logto sign-in page.
- After you signed in, you will be redirected back to your application and see the sign-out button.
- Click the sign-out button to clear local storage and sign out.
Add Naver connector
To add a social connector, go to the "Connector" tab in the Admin Console, then click on "Social connectors". From there, click "Add social connector".
In the openning modal, select "Naver" and click "Next".
On the next page, you will see a two-column layout with the README content on the left and configuration on the right.
Feel free to follow the README file in place or read the following section to complete the configuration process. If you follow the in-place guide, you can skip the next section.
Set up Naver login
Developer Site Only Korean Support Now
Currently Naver Developers
site only supports Korean. Please consider use a translator.
For the Production
- For the production, you have to get review from Naver team.
Otherwise, only registered users can sign in.
- You can add a tester from
맴버관리(Member Manage)
menu.
- You can add a tester from
- To get a review, please check
애플리케이션 개발 상태(Application Devlopment Status)
fromAPI 설정(API Setting)
from your application project setting.
Set up a project in the Naver Developers
- Visit the Naver Developers and sign in with your Naver account.
- Click the Application -> 어플리케이션 등록 from the menu to create new project.
- Follow the instruction below to create application.
Application Name (어플리케이션 이름)
- Type your application name on
어플리케이션 이름
(This name is shown while a user sign in.)
API Usage (사용 API)
- Choose
네이버 로그인(Naver Login)
for사용 API(API Usage)
- Check
이메일 주소(Email Address), 별명(Nickname), 프로필 사진(Profile Image)
as필수(Neccessary)
from권한(Role)
(You can check추가(Add)
as optional these options, but you cannot get the information from the user.)
Sign in Open API Service Environment (로그인 오픈 API 서비스 환경)
- For
로그인 오픈 API 서비스 환경(Sign in Open API Service Environment)
, add two environmentPC웹(PC Web)
and모바일웹(Mobile Web)
.
PC Web (PC 웹)
- For
서비스 URL(Service URL)
, typehttp(s)://YOUR_URL
(ex. https://logto.io) - For
네이버 로그인(Naver Login) Callback URL
, typehttp(s)://YOUR_URL/callback/connector_id
(e.g. https://logto.io/callback/connector_id)
Mobile Web (Mobile 웹)
- For
서비스 URL(Service URL)
, typehttp(s)://YOUR_URL
(ex. https://logto.io) - For
네이버 로그인(Naver Login) Callback URL
, typehttp(s)://YOUR_URL/callback/connector_id
(e.g. https://logto.io/callback/connector_id)
⚠️ Caution
The
connector_id
can be found on the top bar of the Logto Admin Console connector details page.
Configure Logto
Config types
Name | Type |
---|---|
clientId | string |
clientSecret | string |
clientId
clientId
is Client ID
of your project.
(You can find it from 애플리케이션 정보(Application Info)
of your project from Naver developers.)
clientSeceret
clientSecret
is Client Secret
of your project.
(You can find it from 애플리케이션 정보(Application Info)
of your project from Naver developers.)
Save your configuration
Double check you have filled out necessary values in the Logto connector configuration area. Click "Save and Done" (or "Save changes") and the Naver connector should be available now.
Enable Naver connector in Sign-in Experience
Switch to the "Sign-in experience" tab, then click the "Sign-up and sign-in" tab.
If it's the first time you enter the tab, you will see a quick introduction about Sign-in Experience and its basic configuration.
Select "None" for the "Sign-up identifier" to provide minimum sign-up effort for Naver sign-in, which may increase your conversion rate.
In the "Social sign-in" section, add "Add Social Connector" and choose "Naver". Then you should be able to see a button with text "Continue with Naver" in the preview section.
Finally, click "Save changes" on the bottom right corner.
Testing and Validation
Return to your Flutter app. You should now be able to sign in with Naver. Enjoy!
Further readings
Protect your API For native and single page apps, you'll need to call one or more API endpoints to retrieve and update data.
Learn more about identifying who's who and keeping your API secure.
User management We know you care about user management and activities, as we also do.
Learn more about how to know your users and see the figures like DAU and MAU graphically.
Localization From one regional business to a global corporate, the willingness to offer the best user experience won't change.
You can change current language phrases or add a new language without friction.
Customer IAM series Our serial blog posts about Customer (or Consumer) Identity and Access Management, from 101 to advanced topics and beyond.