Implement Authentication Flow API using Express
This post provides a simple guide for implementing a custom email + password login and signup pages using Authentication Flow API and Express.
Last updated
This post provides a simple guide for implementing a custom email + password login and signup pages using Authentication Flow API and Express.
Last updated
With the Authentication Flow API, you can replace the default Auth UI provided by Authgear with your own custom UI built from the ground up.
In this post, we'll walk you through an example of building your own custom login and signup pages using Express and the Authentication Flow API.
Before we continue, it's important for you to familiarize yourself with the following concepts about the Authentication Flow API:
URL Query: This is an additional set of URL query parameters that Authgear adds to your Custom UI URI during the initialization of the authentication flow. The initial request to the Authentication Flow API must include this URL query in order to return get value for finish_redirect_uri at the end of the flow.
Endpoint: Your Authgear project's domain is visible on your application configuration page in Authgear Portal, under the Endpoint section. Your full endpoint is your Authgear domain followed by a valid path for an operation (such as starting a new authentication flow, or sending input to an existing flow. For example, https://my-project.authgear.cloud/api/v1/authentication_flows to start an authentication flow and https://my-project.authgear.cloud/api/v1/authentication_flows/states/input to send input to an existing flow.
State Token: The Authentication Flow API supports authentication with multi-step UI just like the default authentication flow in Auth UI. State tokens can be used to make this type of type of authentication flow work. You can pass information about a previous step to the next step by using the state token. For example, using the state token in the result of step A as input in step B to continue using the state of the previous step.
Inputs: You can pass values to Authentication Flow API using the input or batch_input parameters in your HTTP request body. Use the batch_input to send multiple values as in an array and input when you are passing only 1 value.
Finish Redirect URI: This is a URL that you can use to redirect back to your app at the end of the authentication flow.
Note: In order to follow this tutorial and implement the example app, you need to enable a login method that supports "Email and Password" under Authentication > Login Methods in Authgear Portal. Also, disable 2FA Requirements from Authentication > 2FA in Authgear Portal.
In order to follow along with the example in this post, you should have the following:
Node.js installed on your local machine.
A code editor such as VS Code, Sublime, Atom, etc.
An Authgear account. You can create one for free .
Be familiar with CLI tools like npm.
Enable Custom UI for your Authgear Project. to enable custom UI.
Next, set up your Authgear project to use custom authentication UI by following the steps below.
An important part of getting your application ready to use custom authentication UI is to configure your Authgear project in Portal. In this section, we'll cover the configuration required for the example app.
Login to the Authgear Portal and navigate to the Application section. Select an existing application and modify it or click on the Add Application button to create a new application.
Configure your application using the following details:
Application name: My app <or any name of your choice>
Application type: OIDC Client Application
Once you're done, click on the Save button to continue.
Note: You can select any Application Type on the Portal depending on the nature of your client application that will be interacting with Authgear and your Custom UI.
To follow this example, select OIDC Client Application as your Application type.
An Authorized Redirect URI is a page on your application that you want Authgear to redirect users to at the end of an authentication flow.
To add an Authorized Redirect URI, scroll to the URIs section on your Authgear application configuration page. Click on the Add URI button then enter a valid URI for your application.
For our example, the redirect URI will be:
Once you're done, click on the Save button to keep your changes.
To use your custom authentication UI with Authgear, you need to specify the URI for your custom UI in the Authgear portal using the custom UI URI field. This will cause your application to show the custom UI instead of the default Auth UI during login/sign. The custom UI URI is basically a link to your custom login page.
Since we'll be testing the example app on a browser that runs on the same computer as the Express server, you can use the following value for the Custom UI URI:
To set the custom UI URI, scroll to the Custom UI section on your application configuration page and paste the URL (e.g the unique public URL from CloudFlare Tunnel) in the Custom UI URI text box.
Note: For our example app, you must include the /login path in the URL so that the user is redirected straight to our login route.
That concludes all the configuration requirements in the Authgear portal for this example.
For our example app in this tutorial, users will be using their email and password to log in. Hence, you are required to enable this option in the Authgear Portal.
To do that, enable the "Email + Password" option under Authentication > Login Methods.
Also, disable 2FA (if enabled) so that the authentication flow does not include an extra step which our demo app will not cover. You can disable 2FA Requirements in Authentication > 2FA in the Authgear Portal.
In this part of the guide, we'll implement custom login and signup pages using Express and the Authentication Flow API.
The application you'll build in this part is the same application your Custom UI URI should point to.
Create a basic Express application for your Authgear project.
To do that, first run the following commands on your computer to create a new project folder and install all the necessary dependencies:
Create project folder/directory:
Change your working directory to the new folder by running the following command:
Install Express:
For our example application, we'll be using the Axios node package to make HTTP requests. Run the following command to install Axios in your project:
Install dotenv. We'll use this package to enable the use of .env file to store project configuration:
After installing the above dependencies, create a new app.js file in the project directory you created earlier. Add the following code to the file:
Create a .env file then add the following code to it:
Add the correct values from your Authgear application configuration page in the .env file.
At the end of this step, you should have an Express application that can connect to Authgear. However, we are yet to implement the custom login/signup page. In the next steps, we'll implement both pages.
Add the following code to your app.js file just below the app.get('/startLogin',...) route:
The above code sets up a basic email + password login page using Express.
The rawURLQuery() function extracts the URL query we mentioned earlier from the URL of the login page. The code includes the query as the value for an <input type="hidden"> so that we can include the value in the request we'll make to the Authentication Flow API later.
The following screenshot shows the output of the login page in a browser:
Now your application needs to make an HTTP request to the Authentication Flow API with the user inputs to authenticate them.
First, we'll create a userLogin() function that sends the HTTP request. To do that, add the following code to your app.js just above the declaration of the rawURLQuery() function:
Here are a few key things to note about the above code:
The code initiates an Authentication Flow API request of type login and finishes the entire login flow in a single step (one HTTP request).
As we mentioned earlier, the URL query from Authgear is added to the API endpoint for the initial request.
The user inputs (email and password) are sent in the request body using the batch_input parameter.
The structure of the HTTP response will look like this:
Now add the following code after the app.get('/login',...) route to create a new route that handles the action of submitting the login form:
Once the login flow is complete and a finish_redirect_uri is returned, we redirect the user to this URL for Authgear to finish the authentication process and redirect the user back to your application.
To test your progress so far, start your Express app by running the following command:
Now open your app in a web browser by visiting localhost:3000. Once the page loads, click on the Login link. You should be redirected to the custom login page instead of the default Auth UI by Authgear.
Enter a valid email and password and click the Submit button. You should be redirected back to your application on successful login.
This step includes an example of using the Authentication Flow API for user signup. Unlike in the previous login flow example, this time we'll use the API to perform a signup flow using 2 steps(also 2 HTTP requests).
The first step is to initialize the signup flow. To do that, create an initSignUp() function just after the userLogin() function in app.js using the following code:
Here is a breakdown of what the above code does:
First, in the code, the value for the URL query is added to the Authentication Flow API endpoint so as to meet the requirement for getting the finish_redirect_uri at the end of the flow.
The type of authentication flow is also specified as signup in the input variable that's passed in the HTTP request body.
The function returns the value of state_token from the HTTP request response. This value is required in the next step (request) to continue the signup flow.
To create the actual page with a signup, add the following code just after the app.post('/login',...) route in app.js:
The above code contains the HTML code for rendering a simple email and password signup page. It also calls the initSignUp() to start the authorization flow and add the state token in an <input type="hidden">.
To complete the signup flow, first create a submitSignUpData() function by adding the following code just after the initSignUp() function in app.js:
The above code implements the second step of the signup flow. It takes the state token from the first step and sends it in the second HTTP request so that the flow can continue.
Next, add the following code just after the app.get('/signup',...) route:
The above code calls the submitSignUpData() function which initiates the second step of the signup flow and submits the user inputs. At the end, the user is redirected to the finish_redirect_uri again to complete the authentication process.
Just like we've implemented custom UI for email and password authentication in this example, you can design custom UIs for other authentication flows that Authgear supports. For example, OTP and TOTP.
To learn more about all the endpoints the Authentication Flow API supports, and their inputs and outputs, you should check out the API reference page for Authentication Flow API.
Alternatively, you can get a public URL for our local Express app with CloudFlare Tunnel. See more instructions on how to set up CloudFlare tunnel on your local machine .
You can find the complete code for the example application in this post in our .