Skip to content

Latest commit



462 lines (339 loc) · 14.5 KB


File metadata and controls

462 lines (339 loc) · 14.5 KB

Getting Started With FOSUserBundle

The Symfony Security component provides a flexible security framework that allows you to load users from configuration, a database, or anywhere else you can imagine. The FOSUserBundle builds on top of this to make it quick and easy to store users in a database, as well as functionality for registration, reset password and a profile page.

So, if you need to persist and fetch the users in your system to and from a database, then you're in the right place.

For a video tutorial, check out FOSUserBundle FTW by KnpUniversity.


This version of the bundle requires Symfony 2.8+. If you are using an older Symfony version, please use the 1.3.x releases of the bundle.


If you wish to use default texts provided in this bundle, you have to make sure you have translator enabled in your config.

# app/config/config.yml

    translator: ~

For more information about translations, check Symfony documentation.


Installation is a quick (I promise!) 7 step process:

  1. Download FOSUserBundle using composer
  2. Enable the Bundle
  3. Create your User class
  4. Configure your application's security.yml
  5. Configure the FOSUserBundle
  6. Import FOSUserBundle routing
  7. Update your database schema

Step 1: Download FOSUserBundle using composer

Require the bundle with composer:

$ composer require friendsofsymfony/user-bundle "^3.0"

Composer will install the bundle to your project's vendor/friendsofsymfony/user-bundle directory. If you encounter installation errors pointing at a lack of configuration parameters, such as The child node "db_driver" at path "fos_user" must be configured, you should complete the configuration in Step 5 first and then re-run this step.

Step 2: Enable the bundle

Enable the bundle in the kernel:

// app/AppKernel.php

public function registerBundles()
    $bundles = array(
        // ...
        new FOS\UserBundle\FOSUserBundle(),
        // ...

Step 3: Create your User class

The goal of this bundle is to persist some User class to a database (MySql, MongoDB, CouchDB, etc). Your first job, then, is to create the User class for your application. This class can look and act however you want: add any properties or methods you find useful. This is your User class.

The bundle provides base classes which are already mapped for most fields to make it easier to create your entity. Here is how you use it:

  1. Extend the base User class (from the Model folder if you are using any of the doctrine variants)
  2. Map the id field. It must be protected as it is inherited from the parent class.


When you extend from the mapped superclass provided by the bundle, don't redefine the mapping for the other fields as it is provided by the bundle.

In the following sections, you'll see examples of how your User class should look, depending on how you're storing your users (Doctrine ORM, MongoDB ODM, or CouchDB ODM).


The doc uses a bundle named AppBundle according to the Symfony best practices. However, you can of course place your user class in the bundle you want.


If you override the __construct() method in your User class, be sure to call parent::__construct(), as the base User class depends on this to initialize some fields.

a) Doctrine ORM User class

If you're persisting your users via the Doctrine ORM, then your User class should live in the Entity namespace of your bundle and look like this to start:

// src/AppBundle/Entity/User.php

namespace AppBundle\Entity;

use FOS\UserBundle\Model\User as BaseUser;
use Doctrine\ORM\Mapping as ORM;

 * @ORM\Entity
 * @ORM\Table(name="fos_user")
class User extends BaseUser
     * @ORM\Id
     * @ORM\Column(type="integer")
     * @ORM\GeneratedValue(strategy="AUTO")
    protected $id;

    public function __construct()
        // your own logic
# src/AppBundle/Resources/config/doctrine/User.orm.yml
    type:  entity
    table: fos_user
            type: integer
                strategy: AUTO
<?xml version="1.0" encoding="utf-8"?>
<!-- src/AppBundle/Resources/config/doctrine/User.orm.xml -->
<doctrine-mapping xmlns=""

    <entity name="AppBundle\Entity\User" table="fos_user">
        <id name="id" type="integer" column="id">
            <generator strategy="AUTO"/>


user is a reserved keyword in the SQL standard. If you need to use reserved words, surround them with backticks, e.g. @ORM\Table(name="`user`")

b) MongoDB User class

If you're persisting your users via the Doctrine MongoDB ODM, then your User class should live in the Document namespace of your bundle and look like this to start:

// src/AppBundle/Document/User.php

namespace AppBundle\Document;

use FOS\UserBundle\Model\User as BaseUser;
use Doctrine\ODM\MongoDB\Mapping\Annotations as MongoDB;

 * @MongoDB\Document
class User extends BaseUser
     * @MongoDB\Id(strategy="auto")
    protected $id;

    public function __construct()
        // your own logic

c) CouchDB User class

If you're persisting your users via the Doctrine CouchDB ODM, then your User class should live in the CouchDocument namespace of your bundle and look like this to start:

// src/AppBundle/CouchDocument/User.php

namespace AppBundle\CouchDocument;

use FOS\UserBundle\Model\User as BaseUser;
use Doctrine\ODM\CouchDB\Mapping\Annotations as CouchDB;

 * @CouchDB\Document
class User extends BaseUser
     * @CouchDB\Id
    protected $id;

    public function __construct()
        // your own logic

Step 4: Configure your application's security.yml

In order for Symfony's security component to use the FOSUserBundle, you must tell it to do so in the security.yml file. The security.yml file is where the basic security configuration for your application is contained.

Below is a minimal example of the configuration necessary to use the FOSUserBundle in your application:

# app/config/security.yml
        FOS\UserBundle\Model\UserInterface: auto

        ROLE_ADMIN:       ROLE_USER

            id: fos_user.user_provider.username

            pattern: ^/
            user_checker: fos_user.user_checker
                provider: fos_userbundle
                csrf_token_generator: security.csrf.token_manager

            logout:       true
            anonymous:    true

        - { path: ^/login$, role: IS_AUTHENTICATED_ANONYMOUSLY }
        - { path: ^/register, role: IS_AUTHENTICATED_ANONYMOUSLY }
        - { path: ^/resetting, role: IS_AUTHENTICATED_ANONYMOUSLY }
        - { path: ^/admin/, role: ROLE_ADMIN }

Under the providers section, you are making the bundle's packaged user provider service available via the alias fos_userbundle. The id of the bundle's user provider service is fos_user.user_provider.username.

Next, take a look at and examine the firewalls section. Here we have declared a firewall named main. By specifying form_login, you have told the Symfony Framework that any time a request is made to this firewall that leads to the user needing to authenticate himself, the user will be redirected to a form where he will be able to enter his credentials. It should come as no surprise then that you have specified the user provider service we declared earlier as the provider for the firewall to use as part of the authentication process.


Although we have used the form login mechanism in this example, the FOSUserBundle user provider service is compatible with many other authentication methods as well. Please read the Symfony Security component documentation for more information on the other types of authentication methods.

The access_control section is where you specify the credentials necessary for users trying to access specific parts of your application. The bundle requires that the login form and all the routes used to create a user and reset the password be available to unauthenticated users but use the same firewall as the pages you want to secure with the bundle. This is why you have specified that any request matching the /login pattern or starting with /register or /resetting have been made available to anonymous users. You have also specified that any request beginning with /admin will require a user to have the ROLE_ADMIN role.

For more information on configuring the security.yml file please read the Symfony security component documentation.


Pay close attention to the name, main, that we have given to the firewall which the FOSUserBundle is configured in. You will use this in the next step when you configure the FOSUserBundle.

Step 5: Configure the FOSUserBundle

Now that you have properly configured your application's security.yml to work with the FOSUserBundle, the next step is to configure the bundle to work with the specific needs of your application.

Add the following configuration to your config.yml file according to which type of datastore you are using.

# app/config/config.yml
    db_driver: orm # other valid values are 'mongodb' and 'couchdb'
    firewall_name: main
    user_class: AppBundle\Entity\User
        address: "%mailer_user%"
        sender_name: "%mailer_user%"
<!-- app/config/config.xml -->

<!-- other valid 'db-driver' values are 'mongodb' and 'couchdb' -->

Only four configuration's nodes are required to use the bundle:

  • The type of datastore you are using (orm, mongodb or couchdb).
  • The firewall name which you configured in Step 4.
  • The fully qualified class name (FQCN) of the User class which you created in Step 3.
  • The default email address to use when the bundle send a registration confirmation to the user.


FOSUserBundle uses a compiler pass to register mappings for the base User model classes with the object manager that you configured it to use. (Unless specified explicitly, this is the default manager of your doctrine configuration.)

Step 6: Import FOSUserBundle routing files

Now that you have activated and configured the bundle, all that is left to do is import the FOSUserBundle routing files.

By importing the routing files you will have ready made pages for things such as logging in, creating users, etc.

# app/config/routing.yml
    resource: "@FOSUserBundle/Resources/config/routing/all.xml"
<!-- app/config/routing.xml -->
<import resource="@FOSUserBundle/Resources/config/routing/all.xml"/>


In order to use the built-in email functionality (confirmation of the account, resetting of the password), you must activate and configure the SwiftmailerBundle.

Step 7: Update your database schema

Now that the bundle is configured, the last thing you need to do is update your database schema because you have added a new entity, the User class which you created in Step 4.

For ORM run the following command.

$ php bin/console doctrine:schema:update --force

For MongoDB users you can run the following command to create the indexes.

$ php bin/console doctrine:mongodb:schema:create --index


If you use the Symfony 2.x structure in your project, use app/console instead of bin/console in the commands.

You now can log in at!

Next Steps

Now that you have completed the basic installation and configuration of the FOSUserBundle, you are ready to learn about more advanced features and usages of the bundle.

The following documents are available:

overriding_templates controller_events overriding_forms user_manager command_line_tools logging_by_username_or_email form_type emails doctrine overriding_validation canonicalizer custom_storage_layer routing configuration_reference adding_invitation_registration