Skip to main content
· 2 min read
Logto team
The better identity infrastructure for developers
For our new friends

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 Kakao sign-in experience (user authentication) with Expo (React Native) and  Logto.

Prerequisites

Create an application in Logto

In you browser, open a new tab and enter the link of Logto Admin Console.

Get Started

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

Framework List

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 "Expo" framework card to start creating your application.

Enter application name

Create Application modal

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

tip
  • The following demonstration is built on Expo ~50.0.6.
  • The sample project is available on our SDK repository.

Installation

Install Logto SDK and peer dependencies via your favorite package manager:

npm i @logto/rn
npm i expo-crypto expo-secure-store expo-web-browser @react-native-async-storage/async-storage

The @logto/rn package is the SDK for Logto. The remaining packages are its peer dependencies. They couldn't be listed as direct dependencies because the Expo CLI requires that all dependencies for native modules be installed directly within the root project's package.json.

note

If you're installing this in a bare React Native app, you should also follow these additional installation instructions.

Init Logto provider

Import and use LogtoProvider to provide a Logto context:

App.tsx
import { LogtoProvider, LogtoConfig } from '@logto/rn';

const config: LogtoConfig = {
endpoint: '<your-logto-endpoint>',
appId: '<your-application-id>',
};

const App = () => (
<LogtoProvider config={config}>
<YourAppContent />
</LogtoProvider>
);

Implement sign-in and sign-out

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:

  1. Your app invokes the sign-in method.
  2. The user is redirected to the Logto sign-in page. For native apps, the system browser is opened.
  3. The user signs in and is redirected back to your app (configured as the redirect URI).
Regarding redirect-based sign-in
  1. This authentication process follows the OpenID Connect (OIDC) protocol, and Logto enforces strict security measures to protect user sign-in.
  2. 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.


Switch to the application details page of Logto Console. Add a native redirect URI (for example, io.logto://callback), then click "Save".

  • 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 filled in Expo's app.json file, for example:

    app.json
    {
    "expo": {
    "scheme": "io.logto"
    }
    }

Now back to your app, you can use useLogto hook to sign in and sign out:

App.tsx
import { useLogto } from '@logto/rn';
import { Button } from 'react-native';

const Content = () => {
const { signIn, signOut, isAuthenticated } = useLogto();

return (
<div>
{isAuthenticated ? (
<Button title="Sign out" onPress={async () => signOut()} />
) : (
// Replace the redirect URI with your own
<Button title="Sign in" onPress={async () => signIn('io.logto://callback')} />
)}
</div>
);
};

Checkpoint: Test your application

Now, you can test your application:

  1. Run your application, you will see the sign-in button.
  2. Click the sign-in button, the SDK will init the sign-in process and redirect you to the Logto sign-in page.
  3. After you signed in, you will be redirected back to your application and see the sign-out button.
  4. Click the sign-out button to clear local storage and sign out.
Test your integration

Open your Expo (React Native) app to test if the integration works. When you click the "Sign In" button, the page should be redirected to a Logto sign-in page, and you should be able to create a new account by entering username and password and complete the sign-in process.

Add Kakao 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".

Connector tab

In the openning modal, select "Kakao" 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 Kakao login

Set up a project in the Kakao Devlopers Console

  • Visit the Kakao Developers Console and sign in with your Kakao account.
  • Click the Add an application to create new project or choose exist project.

Configure Kakao Login

Activate Kakao Login

  • Click the Product Settings -> Kakao Login from the menu.
  • Turn on Kakao Login Activation
  • Add below URL into Redirect URI
    • http(s)://YOUR_URL/callback/${connector_id} (The connector_id can be found on the top bar of the Logto Admin Console connector details page.)
    • (Please replace YOUR_URL with your Logto URL, and choose http or https on your situation.)

Privacy Setting

  • Click the Product Settings -> Kakao Login -> Consent Item from the menu.
  • Change state of Nickname, Profile image, and Email to Required consent (You might not able to change Email to Required consent because of your project setting.)

Security Setting (Optional)

  • Click the Product Settings -> Kakao Login -> Security from the menu.
  • Click the Client secret code to generate secret code.
  • Change Activation state to Enable. (If you enable it, secret code is necessary.)

Configure Logto

Config types

NameType
clientIdstring
clientSecretstring?

clientId

clientId is REST API key of your project. (You can find it from summary of your project from Kakao developers console.)

clientSeceret

clientSecret is Secret Code of your project. (Please check Security Setting (Optional))

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 Kakao connector should be available now.

Enable Kakao connector in Sign-in Experience

Switch to the "Sign-in experience" tab, then click the "Sign-up and sign-in" tab.

note

If it's the first time you enter the tab, you will see a quick introduction about Sign-in Experience and its basic configuration.

Sign-in Experience tab

Select "None" for the "Sign-up identifier" to provide minimum sign-up effort for Kakao sign-in, which may increase your conversion rate.

In the "Social sign-in" section, add "Add Social Connector" and choose "Kakao". Then you should be able to see a button with text "Continue with Kakao" in the preview section.

Save changes

Finally, click "Save changes" on the bottom right corner.

Testing and Validation

Return to your Expo (React Native) app. You should now be able to sign in with Kakao. 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.