Logto is an Auth0 alternative designed for modern apps and SaaS products. It offers both Cloud and Open-source services to help you quickly launch your identity and management (IAM) system. Enjoy authentication, authorization, and multi-tenant management all in one.
We recommend starting with a free development tenant on Logto Cloud. This allows you to explore all the features easily.
In this article, we will go through the steps to quickly build the Naver sign-in experience (user authentication) with Express and Logto.
Prerequisites
- A running Logto instance. Check out the introduction page to get started.
- Basic knowledge of Express.
- A usable Naver account.
Create an application in Logtoโ
Logto is based on OpenID Connect (OIDC) authentication and OAuth 2.0 authorization. It supports federated identity management across multiple applications, commonly called Single Sign-On (SSO).
To create your Traditional web application, simply follow these steps:
- Open the Logto Console. In the "Get started" section, click the "View all" link to open the application frameworks list. Alternatively, you can navigate to Logto Console > Applications, and click the "Create application" button.
- In the opening modal, click the "Traditional web" section or filter all the available "Traditional web" frameworks using the quick filter checkboxes on the left. Click the "Express" framework card to start creating your application.
- 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 Express SDKโ
- The sample project is available on our SDK repository.
Installationโ
Install Logto SDK via your favorite package manager:
- npm
- pnpm
- yarn
npm i @logto/express cookie-parser express-session
pnpm add @logto/express cookie-parser express-session
yarn add @logto/express cookie-parser express-session
Integrationโ
Prepare configs and required middlewaresโ
Prepare configuration for the Logto client:
import { LogtoExpressConfig } from '@logto/express';
const config: LogtoExpressConfig = {
appId: '<your-application-id>',
appSecret: '<your-application-secret>',
endpoint: '<your-logto-endpoint>', // E.g. http://localhost:3001
baseUrl: '<your-express-app-base-url>', // E.g. http://localhost:3000
};
The SDK requires express-session to be configured in prior.
import cookieParser from 'cookie-parser';
import session from 'express-session';
app.use(cookieParser());
app.use(
session({
secret: 'random_session_key', // Replace with your own secret
cookie: { maxAge: 14 * 24 * 60 * 60 * 1000 }, // In miliseconds
})
);
Configure redirect URIsโ
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.
In the following code snippets, we assume your app is running on http://localhost:3000/
.
Configure redirect URIsโ
Switch to the application details page of Logto Console. Add a redirect URI http://localhost:3000/callback
.
Just like signing in, users should be redirected to Logto for signing out of the shared session. Once finished, it would be great to redirect the user back to your website. For example, add http://localhost:3000/
as the post sign-out redirect URI section.
Then click "Save" to save the changes.
Register routesโ
The SDK provides a helper function handleAuthRoutes
to register 3 routes:
/logto/sign-in
: Sign in with Logto./logto/sign-in-callback
: Handle sign-in callback./logto/sign-out
: Sign out with Logto.
Add the following code to your app:
import { handleAuthRoutes } from '@logto/express';
app.use(handleAuthRoutes(config));
Implement sign-in and sign-outโ
With the routes registered, now let's implement the sign-in and sign-out buttons in the home page. We need to redirect the user to the sign-in or sign-out route when needed. To help with this, use withLogto
to inject authentication status to req.user
.
import { withLogto } from '@logto/express';
app.get('/', withLogto(config), (req, res) => {
res.setHeader('content-type', 'text/html');
if (req.user.isAuthenticated) {
res.end(`<div>Hello ${req.user.claims?.sub}, <a href="/logto/sign-out">Sign Out</a></div>`);
} else {
res.end('<div><a href="/logto/sign-in">Sign In</a></div>');
}
});
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 token storage and sign out.
Add Naver connectorโ
To enable quick sign-in and improve user conversion, connect with Express as an identity provider. The Logto social connector helps you establish this connection in minutes by allowing several parameter inputs.
To add a social connector, simply follow these steps:
- Navigate to Console > Connectors > Social Connectors.
- Click "Add social connector" and select "Naver".
- Follow the README guide and complete required fields and customize settings.
If you are following the in-place Connector 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})
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โ
Once you create a social connector successfully, you can enable it as a "Continue with Naver" button in Sign-in Experience.
- Navigate to Console > Sign-in experience > Sign-up and sign-in.
- (Optional) Choose "Not applicable" for sign-up identifier if you need social login only.
- Add configured Naver connector to the "Social sign-in" section.
Testing and Validationโ
Return to your Express app. You should now be able to sign in with Naver. Enjoy!
Further readingsโ
End-user flows: Logto provides a out-of-the-box authentication flows including MFA and enterprise SSO, along with powerful APIs for flexible implementation of account settings, security verification, and multi-tenant experience.
Authorization: Authorization defines the actions a user can do or resources they can access after being authenticated. Explore how to protect your API for native and single-page applications and implement Role-based Access Control (RBAC).
Organizations: Particularly effective in multi-tenant SaaS and B2B apps, the organization feature enable tenant creation, member management, organization-level RBAC, and just-in-time-provisioning.
Customer IAM series Our serial blog posts about Customer (or Consumer) Identity and Access Management, from 101 to advanced topics and beyond.