Thursday May 20, 2021 By David Quintanilla
How To Implement Authentication In Next.js With Auto0 — Smashing Magazine

About The Writer

Methods Engineer from Buenos Aires, Argentina, with 15+ years of expertise in software program growth. Full Stack Developer. Auth0 Ambassador. GitKraken …
More about

In the meanwhile of including authentication and authorization to our net purposes, there are some issues that we must always consider, e.g. whether or not we have to create our personal safety platform or whether or not we will depend on an current third-party service. Let’s see how we will implement authentication and authorization in Subsequent.js apps, with Auth0.

“Authentication” is the motion of validating {that a} person is who she or he claims to be. We normally do that by implementing a credentials system, like person/password, safety questions, and even facial recognition.

“Authorization” determines what a person can (or can’t) do. If we have to deal with authentication and authorization in our net software, we’ll want a safety platform or module. We will develop our personal platform, implement it, and preserve it. Or we will take the benefit of current authentication and authorization platforms out there which are provided as companies.

When evaluating whether or not it’s higher for us to create our personal platform, or to make use of a third-party service, there are some issues that we must always contemplate:

  • Designing and creating authentication companies is just not our core talent. There are individuals working specifically targeted on safety matters that may create higher and safer platforms than us;
  • We will save time counting on an current authentication platform and spend it including worth to the services that we care about;
  • We don’t retailer delicate data in our databases. We separate it from all the information concerned in our apps;
  • The instruments third-party companies provide have improved usability and efficiency, which makes it simpler for us to administrate the customers of our software.

Contemplating these components, we will say that counting on third-party authentication platforms could be simpler, cheaper, and much more safe than creating our personal safety module.

On this article, we’ll see how you can implement authentication and authorization in our Subsequent.js purposes utilizing one of many current merchandise out there: Auth0.

What Is Auth0?

It permits you to add safety to apps developed utilizing any programming language or expertise.

“Auth0 is a versatile, drop-in answer so as to add authentication and authorization companies to your purposes.”

Dan Arias, auth0.com

Auth0 has a number of fascinating options, similar to:

  • Single Signal-On: When you log into an software that makes use of Auth0, you received’t need to enter your credentials once more when coming into one other one which additionally makes use of it. You can be mechanically logged in to all of them;
  • Social login: Authenticate utilizing your most well-liked social community profile;
  • Multi-Issue Authentication;
  • A number of normal protocols are allowed, similar to OpenID Join, JSON Internet Token, or OAuth 2.0;
  • Reporting and analytics instruments.

There’s a free plan that you should use to begin securing your net purposes, overlaying as much as 7000 month-to-month energetic customers. You’ll begin paying when the quantity of customers will increase.

One other cool factor about Auth0 is that we now have a Next.js SDK accessible to make use of in our app. With this library, created particularly for Subsequent.js, we will simply hook up with the Auth0 API.

Auth0 SDK For Subsequent.js

As we talked about earlier than, Auth0 created (and maintains) a Subsequent.js targeted SDK, amongst different SDKs accessible to hook up with the API utilizing varied programming languages. We simply have to obtain the NPM package, configure some particulars about our Auth0 account and connection, and we’re good to go.

This SDK provides us instruments to implement authentication and authorization with each client-side and server-side strategies, utilizing API Routes on the backend and React Context with React Hooks on the frontend.

Let’s see how a few of them work in an instance Subsequent.js software.

Instance Subsequent.js App Utilizing Auth0

Let’s return to our earlier video platform instance, and create a small app to indicate how you can use Auth0 Subsequent.js SDK. We’ll arrange Auth0’s Universal Login. We may have some YouTube video URLs. They are going to be hidden beneath an authentication platform. Solely registered customers will be capable to see the checklist of movies by means of our net software.

Observe: This text focuses on the configuration and use of Auth0 in your Subsequent.js software. We received’t get into particulars like CSS styling or database utilization. If you wish to see the entire code of the instance app, you may go to this GitHub repository.

Create Auth0 Account And Configure App Particulars

To begin with, we have to create an Auth0 account utilizing the Sign Up page.

creation of an Auth0 account using the Sign Up page
(Large preview)

After that, let’s go to the Auth0 Dashboard. Go to Purposes and create a brand new app of sort [“Regular Web Applications”].

creation of a new app of type 'Regular Web Applications'.
(Large preview)

Now let’s go to the Settings tab of the appliance and, beneath the Software URIs part, configure the next particulars and save the adjustments:

  • Allowed Callback URLs: add http://localhost:3000/api/auth/callback
  • Allowed Logout URLs: add http://localhost:3000/
Settings tab of the application.
(Large preview)

By doing this, we’re configuring the URL the place we wish to redirect the customers after they login our web site (Callback), and the URL the place we redirect the customers after they log off (Logout). We must always add the manufacturing URLs once we deploy the ultimate model of our app to the internet hosting server.

Auth0 Dashboard has many configurations and customizations we will apply to our initiatives. We will change the kind of authentication we use, the login/sign-up web page, the information we request for the customers, allow/disable new registrations, configure customers’ databases, and so forth.

Create Subsequent.js App

To create a model new Subsequent.js app, we’ll use create-next-app, which units up the whole lot mechanically for you. To create the undertaking, run:

npx create-next-app [name-of-the-app]


yarn create next-app [name-of-the-app]

To start out the develop server regionally and see the positioning simply created in your browser, go to the brand new folder that you simply created:

cd [name-of-the-app]

And run:

npm run dev


yarn dev

Set up And Configure The Auth0 Subsequent.js SDK

Let’s set up the Auth0 Subsequent.js SDK in our app:

npm set up @auth0/nextjs-auth0


yarn add @auth0/nextjs-auth0

Now, in our env.native file (or the setting variables menu of our internet hosting platform), let’s add these variables:

AUTH0_SECRET="[A 32 characters secret used to encrypt the cookies]"
AUTH0_ISSUER_BASE_URL="https://[Your tenant domain. Can be found in the Auth0 dashboard under settings]"
AUTH0_CLIENT_ID="[Can be found in the Auth0 dashboard under settings]"
AUTH0_CLIENT_SECRET="[Can be found in the Auth0 dashboard under settings]"
configuration options for the Auth0 Next.js SDK.
(Large preview)

If you’d like extra configuration choices, you may take a look at the docs.

Create the Dynamic API Route

Subsequent.js affords a technique to create serverless APIs: API Routes. With this function, we will create code that can be executed in each person request to our routes. We will outline mounted routes, like /api/index.js. However we will even have dynamic API routes, with params that we will use in our API routes code, like /api/weblog/[postId].js.

Let’s create the file /pages/api/auth/[...auth0].js, which can be a dynamic API route. Inside the file, let’s import the handleAuth methodology from the Auth0 SDK, and export the end result:

import { handleAuth } from '@auth0/nextjs-auth0';

export default handleAuth();

It will create and deal with the next routes:

  • /api/auth/login
    To carry out login or enroll with Auth0.
  • /api/auth/logout
    To log the person out.
  • /api/auth/callback
    To redirect the person after a profitable login.
  • /api/auth/me
    To get the person profile data.

And that may be the server-side a part of our app. If we wish to log in to our software or join a brand new account, we must always go to http://localhost:3000/api/auth/login. We must always add a hyperlink to that route in our app. Similar for logging out from our web site: Add a hyperlink to http://localhost:3000/api/auth/logout.

Add The UserProvider Element

To deal with person authentication state on the frontend of our net software we will use UserProvider React element, accessible on Auth0 Subsequent.js SDK. the element makes use of React Context internally.

If you wish to entry the person authentication state on a Element, it is best to wrap it with a UserProvider element.

  <Element {...props} />

If we wish to entry the entire pages in our software, we must always add the element to the pages/_app.js file. pages/_app.js overrides the React App element. It’s a function that Subsequent.js exposes to customise our software. You possibly can learn extra about it here.

import React from 'react';
import { UserProvider } from '@auth0/nextjs-auth0';

export default operate App({ Element, pageProps }) {
  return (
      <Element {...pageProps} />

We now have a React hook useUser that accesses to the authentication state uncovered by UserProvider. We will use it, for example, to create a type of welcome web page. Let’s change the code of the pages/index.js file:

import { useUser } from "@auth0/nextjs-auth0";

export default () => {
 const { person, error, isLoading } = useUser();

 if (isLoading) return <div>Loading...</div>;

 if (error) return <div>{error.message}</div>;

 if (person) {
   return (
       <a href="https://smashingmagazine.com/api/auth/logout">Logout</a>
 return <a href="http://smashingmagazine.com/api/auth/login">Login</a>;

The person object accommodates data associated to the person’s id. If the individual visiting the web page is just not logged in (we don’t have a person object accessible), we’ll show a hyperlink to the login web page. If the person is already authenticated, we’ll show person.identify and person.e-mail properties on the web page, and a Logout hyperlink.

Let’s create a movies.js file, with an inventory of three YouTube video URLs that can solely be seen for registered individuals. To solely enable logged customers to see this web page, we’ll use withPageAuthRequired methodology from the SDK.

import { withPageAuthRequired } from "@auth0/nextjs-auth0";

export default () => {
 return (
     <a href="https://www.youtube.com/watch?v=5qap5aO4i9A">LoFi Music</a>
     <a href="https://www.youtube.com/watch?v=fEvM-OUbaKs">Jazz Music</a>
     <a href="https://www.youtube.com/watch?v=XULUBg_ZcAU">Piano Music</a>

export const getServerSideProps = withPageAuthRequired();

Take into accounts that our net software permits any individual to enroll in an account, utilizing the Auth0 platform. The person can even re-use an current Auth0 account, as we’re implementing Common Login.

We will create our personal registration web page to request extra particulars concerning the person or add fee data to invoice them month-to-month for our service. We will additionally use the strategies uncovered within the SDK to deal with authorization in an automated method.


On this article, we noticed how you can safe our Subsequent.js purposes utilizing Auth0, an authentication and authorization platform. We consider the advantages of utilizing a third-party service for the authentication of our net purposes in comparison with creating our personal safety platform. We created an instance Subsequent.js app and we secured it utilizing Auth0 free plan and Auth0 Subsequent.js SDK.

If you wish to deploy an Auth0 instance software to Vercel, you are able to do it here.

Additional Studying And Sources

Smashing Editorial
(vf, yk, il)

Source link