Recording

Introduction

In this article, we'll explore the concept of AuthenticationStrategy and how to use it in an application. We'll present an example of a simple application where users can sign up, log in, reset their passwords, and access a restricted area of the application. Throughout the article, we'll explain how to configure each step and how to use the authentication Policy to protect the application's routes. Let's get started!

User Table

Before we start configuring the application, let's create a user table. This table will be used to store information about the users registered in the app. To do this, we'll create a simple table with the fields "name," "email" with unique, and "password." The unique parameter will be used to prevent duplicate emails and data conflicts. It's important to keep stored data secure, which is why we'll use the Password field type for the password.

User Registration

Now that we have our user table, let's configure the user registration screen. On this screen, the user will be able to fill in the fields needed to create an account in the app. We'll use a form with fields for name, email, and password. It's important to keep the password field of type password to ensure the security of the data entered by the user. After configuring the form, we'll add the insert, edit, save, and cancel buttons, which are already pre-configured. This way, the user will be able to perform all these operations easily and intuitively.

Login Screen

Now that we've configured the user registration screen, let's work on the login screen. On this screen, the user will be able to enter their email and password to access the app's restricted area. We'll use a form similar to the registration one, with email and password fields. It's important to keep the password field of type "password" to prevent the password from being displayed while the user types it. We'll also add a block to display an error message if the credentials are incorrect.

Protecting the Routes

Now that we've configured the registration and login screens, let's protect the app's routes so that only authenticated users can access them. To do this, we'll use the authentication policy, which will check whether the user is logged in before allowing access to protected routes. We'll add the authentication policy to all routes in the app, except the home route. This way, only authenticated users will be able to access the app's restricted pages.

Password Reset

Now that we've protected the app's routes, let's implement the password reset feature. This feature will let users reset their passwords if they forget them. To do this, we'll add a "forgot password" button on the login screen. When the user clicks this button, they'll be redirected to a page where they can enter their email to receive a password reset link by email. We'll configure this page to display a personalized message with the user's name and a link to reset the password.

Conclusion

In this article, we introduced the concept of AuthenticationStrategy and how to use it in an application. We demonstrated step by step how to configure the registration, login, and password reset screens, as well as how to protect the app's routes using the authentication policy. We hope this example can serve as a foundation for implementing authentication in your own applications. If you'd like to explore this topic further, check out our User Life Cycle Action template in the Builder. If you have any questions, feel free to reach out. Thanks for reading!