For our new friends:

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 Azure AD sign-in experience (user authentication) with Nuxt and Logto.

Prerequisites

• A running Logto instance. Check out the introduction page to get started.
• Basic knowledge of Nuxt.
• A usable Azure AD 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:

1. 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.
2. 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 "Nuxt" framework card to start creating your application.
3. 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 Nuxt with Logto

ヒント:

• The following demonstration is built on Nuxt 3.10.2.
• The sample project is available in the GitHub repository.
• Logto Nuxt SDK requires server-side rendering (SSR) to work properly. For single-page applications (SPA), check out our Vue SDK.

Installation

Install Logto SDK via your favorite package manager:

npm

npm i @logto/nuxt

pnpm

pnpm add @logto/nuxt

Yarn

yarn add @logto/nuxt

Integration

Register Logto module

In your Nuxt config file, add the Logto module and configure it:

nuxt.config.ts

export default defineNuxtConfig({
  modules: ['@logto/nuxt'],
  runtimeConfig: {
    logto: {
      endpoint: '<your-logto-endpoint>',
      appId: '<your-logto-app-id>',
      appSecret: '<your-logto-app-secret>',
      cookieEncryptionKey: '<a-random-string>',
    },
  },
  // ...other configurations
});

Since these information are sensitive, it's recommended to use environment variables (.env):

.env

NUXT_LOGTO_ENDPOINT="<your-logto-endpoint>"
NUXT_LOGTO_APP_ID="<your-logto-app-id>"
NUXT_LOGTO_APP_SECRET="<your-logto-app-secret>"
NUXT_LOGTO_COOKIE_ENCRYPTION_KEY="<a-random-string>"

See runtime config for more information.

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:

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.

---

注記:

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.

Handle callback

There's no additional setup needed to handle the callback route. When registering @logto/nuxt module, it will do the following:

• Add three routes for sign-in (/sign-in), sign-out (/sign-out), and callback (/callback).
• Import two composables: useLogtoClient and useLogtoUser.

These routes are configurable via logto.pathnames in the module options, for example:

nuxt.config.ts

export default defineNuxtConfig({
  logto: {
    pathnames: {
      signIn: '/login',
      signOut: '/logout',
      callback: '/auth/callback',
    },
  },
  // ...other configurations
});

Check out the type definition file in the @logto/nuxt package for more information.

注記:

If you configure the callback route to a different path, you need to update the redirect URI in Logto accordingly.

Implement sign-in and sign-out

Since Nuxt pages will be hydrated and become a single-page application (SPA) after the initial load, we need to redirect the user to the sign-in or sign-out route when needed. To help with this, our SDK provides the useLogtoUser() composable, which can be used in both server and client side.

index.vue

<script setup lang="ts">
  import { useLogtoUser } from '#imports'; // Add this line if auto-import is disabled
  const user = useLogtoUser();
</script>
<template>
  <!-- Simplified button for sign-in and sign-out -->
  <nuxt-link :to="`/sign-${ user ? 'out' : 'in' }`"> Sign {{ user ? 'out' : 'in' }} </nuxt-link>
</template>

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 token storage and sign out.

Add Azure AD connector

To enable quick sign-in and improve user conversion, connect with Nuxt 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:

1. Navigate to Console > Connectors > Social Connectors.
2. Click "Add social connector" and select "Azure AD".
3. 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 Azure AD

Set up Microsoft Azure AD in the Azure Portal

• Visit the Azure Portal and sign in with your Azure account. You need to have an active subscription to access Microsoft Azure AD.
• Click the Azure Active Directory from the services they offer, and click the App Registrations from the left menu.
• Click New Registration at the top, enter a description, select your access type and add your Redirect URI, which will redirect the user to the application after logging in. In our case, this will be ${your_logto_endpoint}/callback/${connector_id}. e.g. https://foo.logto.app/callback/${connector_id}. The connector_id can be also found on the top bar of the Logto Admin Console connector details page. You can copy the Callback URI in the configuration section.
• Select Web as Platform.

Fill in the configuration in Logto

Name	Type
clientId	string
clientSecret	string
tenantId	string
cloudInstance	string

Client ID

You may find the Application (client) ID in the Overview section of your newly created application in the Azure Portal.

Client Secret

• In your newly created application, click the Certificates & Secrets to get a client secret, and click the New client secret from the top.
• Enter a description and an expiration.
• This will only show your client secret once. Fill the value to the Logto connector configuration and save it to a secure location.

Cloud Instance

Usually, it is https://login.microsoftonline.com/. See Azure AD authentication endpoints for more information.

Tenant ID

Logto will use this field to construct the authorization endpoints. This value is dependent on the access type you selected when creating the application in the Azure Portal.

• If you select Accounts in this organizational directory only for access type then you need to enter your {TenantID}. You can find the tenant ID in the Overview section of your Azure Active Directory.
• If you select Accounts in any organizational directory for access type then you need to enter organizations.
• If you select Accounts in any organizational directory or personal Microsoft accounts for access type then you need to enter common.
• If you select Personal Microsoft accounts only for access type then you need to enter consumers.

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

Enable Azure AD connector in Sign-in Experience

Once you create a social connector successfully, you can enable it as a "Continue with Azure AD" button in Sign-in Experience.

1. Navigate to Console > Sign-in experience > Sign-up and sign-in.
2. (Optional) Choose "Not applicable" for sign-up identifier if you need social login only.
3. Add configured Azure AD connector to the "Social sign-in" section.

Testing and Validation

Return to your Nuxt app. You should now be able to sign in with Azure AD. 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.