Implementing User Registration

Welcome to the first lesson in our course "Securing Your Symfony MVC App" . In this lesson, we'll focus on implementing user registration, a crucial part of any web application. User registration helps in: Creating unique user accounts for personalized experiences. Enhancing security by controlling access to different parts of the application. Tracking user interactions and preferences. By the end of this lesson, you will be able to set up a user registration feature in your Symfony application. This foundational knowledge will be valuable as we explore more advanced authentication strategies in future lessons.

Setting Up the User Entity

Let's start by creating the User entity, which will represent the users of our application. PHP<?php namespace App\Entity; use Doctrine\ORM\Mapping as ORM; #[ORM\Entity(repositoryClass: "App\Repository\UserRepository")] #[ORM\Table(name: "users")] #[ORM\UniqueConstraint(name: "username_unique", columns: ["username"])] class User { #[ORM\Id] #[ORM\GeneratedValue] #[ORM\Column(type: "integer")] private $id; #[ORM\Column(type: "string", length: 255, unique: true)] private $username; #[ORM\Column(type: "string", length: 255)] private $password; // Getter and Setter methods... }<?php namespace App\Entity; use Doctrine\ORM\Mapping as ORM; #[ORM\Entity(repositoryClass: "App\Repository\UserRepository")] #[ORM\Table(name: "users")] #[ORM\UniqueConstraint(name: "username_unique", columns: ["username"])] class User { #[ORM\Id] #[ORM\GeneratedValue] #[ORM\Column(type: "integer")] private $id; #[ORM\Column(type: "string", length: 255, unique: true)] private $username; #[ORM\Column(type: "string", length: 255)] private $password; // Getter and Setter methods... } In this code, we define a User entity class using Doctrine ORM annotations to specify how it maps to the underlying database. The #[ORM\Entity] annotation indicates that this is a Doctrine entity, and the #[ORM\Table] annotation specifies the table name and constraints. The entity has three main properties: id, username, and password. The id is the primary key and is auto-generated. The username is a unique string field, and the password is also stored as a string. The class should also include getter and setter methods to interact with these properties.

Creating the User Repository

Next, we need a repository to interact with the user data in the database. PHP<?php namespace App\Repository; use App\Entity\User; use Doctrine\Bundle\DoctrineBundle\Repository\ServiceEntityRepository; use Doctrine\Persistence\ManagerRegistry; class UserRepository extends ServiceEntityRepository { public function __construct(ManagerRegistry $registry) { parent::__construct($registry, User::class); } public function findByUsername(string $username): ?User { return $this->findOneBy(['username' => $username]); } } The UserRepository extends Doctrine's ServiceEntityRepository, which provides convenient methods for database operations. It includes a custom method findByUsername to retrieve a user by their username, allowing us to encapsulate query logic within the repository.

Building the User Service

The service layer provides a clean way to handle the application logic related to users. This allows for a clean separation between the controller logic and database operations. PHP<?php namespace App\Service; use App\Entity\User; use App\Repository\UserRepository; use Doctrine\ORM\EntityManagerInterface; class UserService { private $entityManager; private $userRepository; public function __construct(EntityManagerInterface $entityManager, UserRepository $userRepository) { $this->entityManager = $entityManager; $this->userRepository = $userRepository; } // Method to create a new user public function create(string $username, string $password): User { $user = new User(); $user->setUsername($username); $user->setPassword($password); // No password hashing yet. $this->entityManager->persist($user); $this->entityManager->flush(); return $user; } // Method to find a user by their username public function findByUsername(string $username): ?User { return $this->userRepository->findByUsername($username); } } Here, the UserService class uses dependency injection to receive the EntityManagerInterface and UserRepository instances. It has two main methods: create, which creates a new user and saves it to the database, and findByUsername, which finds a user by their username. This service layer separates the business logic from the controller, making the code more modular and maintainable.

Setting Up the User Controller

The controller will handle HTTP requests and responses related to user registration. PHP<?php namespace App\Controller; use Symfony\Bundle\FrameworkBundle\Controller\AbstractController; use Symfony\Component\HttpFoundation\Response; use Symfony\Component\HttpFoundation\Request; use Symfony\Component\Routing\Annotation\Route; use App\Service\UserService; class UserController extends AbstractController { private $userService; public function __construct(UserService $userService) { $this->userService = $userService; } #[Route("/register", name: "user_register", methods: ["POST"])] public function register(Request $request): Response { // Retrieve username and password from the request $username = $request->request->get('_username'); $password = $request->request->get('_password'); // Check if username and password are provided if (!$username || !$password) { $this->addFlash('error', 'Username and password are required.'); return $this->redirectToRoute('user_auth'); } // Check if the username already exists if ($this->userService->findByUsername($username)) { $this->addFlash('error', 'Username already exists. Please choose a different one.'); return $this->redirectToRoute('user_auth'); } // Create the user $this->userService->create($username, $password); // Add a success message and redirect to the auth page $this->addFlash('success', 'Registration successful! Please log in.'); // Refresh the page return $this->redirectToRoute('user_auth'); } #[Route("/", name: "user_auth")] public function auth(): Response { return $this->render('user/auth.html.twig'); } } In this code, we define a route for user registration that handles POST requests. The register method validates the request data, checks if the username is unique, creates the user, and provides feedback through flash messages. Additionally, the auth method renders the authentication template.

Creating the Registration Page

Finally, we will create a simple registration page using Twig. HTML<!-- templates/user/auth.html.twig --> <!DOCTYPE html> <html> <head> <title>User Authentication</title> </head> <body> <h1>User Authentication</h1> <!-- Success Messages --> {% for message in app.flashes('success') %} <div class="flash-success"> {{ message }} </div> {% endfor %} <!-- Error Messages --> {% for message in app.flashes('error') %} <div class="flash-error"> {{ message }} </div> {% endfor %} <!-- Registration Form --> <form action="{{ path('user_register') }}" method="post"> <label for="username">Username:</label> <input type="text" id="username" name="_username" required><br><br> <label for="password">Password:</label> <input type="password" id="password" name="_password" required><br><br> <button type="submit">Register</button> </form> </body> </html><!-- templates/user/auth.html.twig --> <!DOCTYPE html> <html> <head> <title>User Authentication</title> </head> <body> <h1>User Authentication</h1> <!-- Success Messages --> {% for message in app.flashes('success') %} <div class="flash-success"> {{ message }} </div> {% endfor %} <!-- Error Messages --> {% for message in app.flashes('error') %} <div class="flash-error"> {{ message }} </div> {% endfor %} <!-- Registration Form --> <form action="{{ path('user_register') }}" method="post"> <label for="username">Username:</label> <input type="text" id="username" name="_username" required><br><br> <label for="password">Password:</label> <input type="password" id="password" name="_password" required><br><br> <button type="submit">Register</button> </form> </body> </html>

Registration Page: Success Messages

Using a Twig loop, we iterate over success messages that are stored in the session flash bag and display them inside a div with the class flash-success . These messages inform the user about successful operations, such as successful registration. HTML {% for message in app.flashes('success') %} <div class="flash-success"> {{ message }} </div> {% endfor %} {% for message in app.flashes('success') %} <div class="flash-success"> {{ message }} </div> {% endfor %}

Registration Page: Error Messages

Similarly, we iterate over error messages and display them inside a div with the class flash-error . These messages inform the user of any errors, such as missing fields or a duplicate username. HTML {% for message in app.flashes('error') %} <div class="flash-error"> {{ message }} </div> {% endfor %} {% for message in app.flashes('error') %} <div class="flash-error"> {{ message }} </div> {% endfor %}

Registration Page: Form

The form includes fields for username and password, both marked as required to ensure users provide this information. It directs the data to the correct endpoint using the action attribute set to the user_register route. Additionally, the method is set to post, which ensures the data is securely transmitted upon form submission. HTML<form action="{{ path('user_register') }}" method="post"> <label for="username">Username:</label> <input type="text" id="username" name="_username" required><br><br> <label for="password">Password:</label> <input type="password" id="password" name="_password" required><br><br> <button type="submit">Register</button> </form><form action="{{ path('user_register') }}" method="post"> <label for="username">Username:</label> <input type="text" id="username" name="_username" required><br><br> <label for="password">Password:</label> <input type="password" id="password" name="_password" required><br><br> <button type="submit">Register</button> </form>

Component Interaction Flow

Here's a simplified flow of how user registration works and how the various components interact: Form Submission : User fills out and submits the registration form, triggering an HTTP POST request to the /register endpoint. Controller Handling : The UserController's register method processes the request, retrieving the username and password from the form data. Service Logic : UserController calls UserService::create to handle the creation of the new user. UserService::create initializes a new User entity, sets the username and password, and uses the entityManager to persist and flush the user to the database. EntityManager and Repository : entityManager manages and tracks entities, saving the new user to the database upon calling flush() . UserRepository, extending ServiceEntityRepository, depends on entityManager to execute database queries. Once entityManager->flush() is called, UserRepository can access the newly created user. This flow ensures that when a user entity is created and persisted by the entityManager, the UserRepository can immediately query for this user, thanks to their integrated system via Doctrine ORM.

Conclusion and Summary

In this lesson, we have covered: Entity Creation: We created the User entity with Doctrine ORM. Repository Setup: We set up the UserRepository for database interactions. Service Implementation: We built the UserService for handling business logic. Controller Development: We created the UserController to handle registration. Form Design: We designed a registration form using Twig. Now that you have a foundational understanding of how to implement user registration in Symfony, it's time to put this knowledge into practice. Use the provided examples and explanations to complete the exercises and reinforce your learning.

Next Lesson: Hashing Passwords During Registration

Join the 1M+ learners on CodeSignal

Be a part of our community of 1M+ users who develop and demonstrate their skills on CodeSignal