Chapters

19 Chapters | 1:23:55 |

01

Installing the Security Bundle

6:09
02

Creating the User Class

7:27
03

Creating a Login Form

9:19
04

Understanding Password Hashing

9:51
05

app.user and Login/Logout Links

4:28
06

Protecting Logout with CSRF

5:11
07

Enabling "Remember Me" Feature

5:33
08

Authentication Attributes

5:07
09

User Roles

5:47
10

Role Hierarchy & Access Control

4:26
11

User Doctrine Relationship

4:18
12

Fetching the User in Services/Controllers

5:03
13

Creating a Custom Voter

6:31
14

Denying Access with a Voter

4:45
15

Impersonating Users with switch_user

(coming soon)
16

Exiting Impersonation & IS_IMPERSONATOR

(coming soon)
17

Limiting Login Attempts

(coming soon)
18

Security Events: Tracking the Last Login

(coming soon)
19

Registration Form

(coming soon)

This course is still being released! Check back later for more chapters.

> Symfony > Symfony Security: The Basics

Buy Access to Course

02.

Creating the User Class

|

|

Autoplay

Previous Challenge

Next Challenge

Login or Register to check out the script

14 Comments

Sort By

Login or Register to join the conversation

JeffJones 55 minutes ago edited

Not sure what I did wrong (which is typical). I ran

symfony console foundry:load-fixtures

It worked correctly in that it did run src/Story/AppStory and did load the Users. But it dropped the "doctrine_migrations_versions" table.

Before loading the fixtures:

symfony console doctrine:migrations:list
+--------------------------------------------------------------------------------------------+--------------+
| Migration Versions                                                                         |              |
+------------------------------------------+----------+---------------------+----------------+--------------+
| Migration                                | Status   | Migrated At         | Execution Time | Description  |
+------------------------------------------+----------+---------------------+----------------+--------------+
| DoctrineMigrations\Version20260812195546 | migrated | 2026-08-19 18:29:18 | 0.026s         | Add User     |
| DoctrineMigrations\Version20260819183049 | migrated | 2026-08-19 18:31:05 | 0.021s         | Add Category |
+------------------------------------------+----------+---------------------+----------------+--------------+

And now after loading the fixtures:

symfony console doctrine:migrations:list
+----------------------------------------------------------------------------------------+--------------+
| Migration Versions                                                                     |              |
+------------------------------------------+--------------+-------------+----------------+--------------+
| Migration                                | Status       | Migrated At | Execution Time | Description  |
+------------------------------------------+--------------+-------------+----------------+--------------+
| DoctrineMigrations\Version20260812195546 | not migrated |             |                | Add User     |
| DoctrineMigrations\Version20260819183049 | not migrated |             |                | Add Category |
+------------------------------------------+--------------+-------------+----------------+--------------+

That doesn't seem right.

What am I doing wrong?

Some notes on my app.
[ ] Entities are not stored under src/Entity but rather src/Data/Entity - that might be the problem. However, load-fixtures does create all the entities tables.
[ ] doctrine.yaml has orm: mappings:

dir: '%kernel.project_dir%/src/Data/Entity'
prefix: 'App\Data\Entity'

[ ] make:migration has not problem finding the Entities
[ ] doctrine:migrations:migrate works fine.

Also doctrine:fixtures:load does not drop the "doctrine_migrations_versions" table.

symfony console doctrine:fixtures:load

However, it does not use AppStory, so no Users were loaded.

|

giorgiocba 2 months ago

I've followed all the steps in this chapter, but there's a problem: the only user created isn't being loaded into the User table. When I run symfony console dbal:run-sql 'select * from user', I get: [OK] The query yielded an empty result set.
If I use the DB Browser for SQLite tool and inspect the User table, it is indeed empty.

|

MolloKhan SFCASTS giorgiocba 2 months ago edited

|

Brontie MolloKhan 2 months ago edited

The chapter’s fixture user is created by Foundry, so an empty user table usually means the fixtures story never ran, not that Doctrine is broken. Run the story loader explicitly so AppStory inserts picard@enterprise.space into the database:

symfony console foundry:load-fixtures

If the table is still empty after that, make sure you already ran the migration that creates the user table, because Foundry can’t insert into a table that doesn’t exist yet. A common gotcha here is checking the SQLite file in one place while Symfony is using a different database path, so verify you’re looking at the same var/data.db your app is actually configured to use.

Sources:

Creating the User Class

| |

MolloKhan SFCASTS giorgiocba 2 months ago edited

Hey @giorgiocba

This may sound silly, but did you load the fixtures? symfony console foundry:load-fixtures
If you did, could you do it again and see if there were any errors or warnings?
Another thing to check is whether you're using Docker for the database and whether you have it installed locally. It may be the case that the CLI is using the Docker instance, but the web isn't.

Cheers!

|

giorgiocba giorgiocba 2 months ago

What could have happened?

|

While this tutorial's code uses Symfony 8, everything discussed works in Symfony 7!

Symfony 8 PHP 8.4

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=8.4",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "babdev/pagerfanta-bundle": "^4.6", // v4.6.0
        "doctrine/dbal": "^4.4", // 4.4.3
        "doctrine/doctrine-bundle": "^3.2", // 3.2.2
        "doctrine/doctrine-migrations-bundle": "^3.7", // 3.7.0
        "doctrine/orm": "^3.6", // 3.6.6
        "knplabs/knp-time-bundle": "^2.5", // 2.5.0
        "pagerfanta/doctrine-orm-adapter": "^4.8", // v4.8.0
        "php-cs-fixer/shim": "^3.94", // v3.95.2
        "phpdocumentor/reflection-docblock": "^5.6", // 5.6.7
        "phpstan/phpdoc-parser": "^2.3", // 2.3.2
        "stof/doctrine-extensions-bundle": "^1.15", // v1.15.3
        "symfony/asset": "8.0.*", // v8.0.8
        "symfony/asset-mapper": "8.0.*", // v8.0.11
        "symfony/console": "8.0.*", // v8.0.11
        "symfony/dotenv": "8.0.*", // v8.0.11
        "symfony/flex": "^2.10", // v2.10.0
        "symfony/form": "8.0.*", // v8.0.9
        "symfony/framework-bundle": "8.0.*", // v8.0.11
        "symfony/http-client": "8.0.*", // v8.0.9
        "symfony/monolog-bundle": "^4.0", // v4.0.2
        "symfony/property-access": "8.0.*", // v8.0.8
        "symfony/property-info": "8.0.*", // v8.0.8
        "symfony/rate-limiter": "8.0.*", // v8.0.14
        "symfony/runtime": "8.0.*", // v8.0.12
        "symfony/security-bundle": "8.0.*", // v8.0.12
        "symfony/security-csrf": "8.0.*", // v8.0.8
        "symfony/serializer": "8.0.*", // v8.0.10
        "symfony/stimulus-bundle": "^2.34", // v2.35.0
        "symfony/twig-bundle": "8.0.*", // v8.0.8
        "symfony/ux-turbo": "^2.34", // v2.35.0
        "symfony/validator": "8.0.*", // v8.0.10
        "symfony/yaml": "8.0.*", // v8.0.12
        "symfonycasts/tailwind-bundle": "^0.12.0", // v0.12.0
        "twig/extra-bundle": "^3.24", // v3.24.0
        "twig/twig": "^3.24" // v3.26.0
    },
    "require-dev": {
        "symfony/debug-bundle": "8.0.*", // v8.0.8
        "symfony/maker-bundle": "^1.67", // v1.67.0
        "symfony/stopwatch": "8.0.*", // v8.0.8
        "symfony/web-profiler-bundle": "8.0.*", // v8.0.12
        "zenstruck/foundry": "^2.9" // v2.10.1
    }
}

Previous Challenge

Next Challenge