Skip to content

Commit 8f2b552

Browse files
committed
[Cookbook] Tweaking registration_form (e.g. bcrypt)
1 parent e14e194 commit 8f2b552

File tree

1 file changed

+62
-13
lines changed

1 file changed

+62
-13
lines changed

cookbook/doctrine/registration_form.rst

Lines changed: 62 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,19 @@
11
.. index::
22
single: Doctrine; Simple Registration Form
33
single: Form; Simple Registration Form
4+
single: Security; Simple Registration Form
45

5-
How to Implement a simple Registration Form
6+
How to Implement a Simple Registration Form
67
===========================================
78

89
Creating a registration form is pretty easy - it *really* means just creating
9-
a form that will update some ``User`` model object (a Doctrine entity in this example)
10-
and then save it.
10+
a form that will update some ``User`` model object (a Doctrine entity in this
11+
example) and then save it.
1112

1213
.. tip::
1314

14-
The popular `FOSUserBundle`_ provides a registration form, reset password form
15-
and other user management functionality.
15+
The popular `FOSUserBundle`_ provides a registration form, reset password
16+
form and other user management functionality.
1617

1718
If you don't already have a ``User`` entity and a working login system,
1819
first start with :doc:`/cookbook/security/entity_provider`.
@@ -61,27 +62,27 @@ With some validation added, your class may look something like this::
6162
private $id;
6263

6364
/**
64-
* @ORM\Column(type="string", length=255)
65+
* @ORM\Column(type="string", length=255, unique=true)
6566
* @Assert\NotBlank()
6667
* @Assert\Email()
6768
*/
6869
private $email;
6970

7071
/**
71-
* @ORM\Column(type="string", length=255)
72+
* @ORM\Column(type="string", length=255, unique=true)
7273
* @Assert\NotBlank()
7374
*/
7475
private $username;
7576

7677
/**
7778
* @Assert\NotBlank()
78-
* @Assert\Length(max = 4096)
79+
* @Assert\Length(max=4096)
7980
*/
8081
private $plainPassword;
8182

8283
/**
8384
* The below length depends on the "algorithm" you use for encoding
84-
* the password, but this works well with bcrypt
85+
* the password, but this works well with bcrypt.
8586
*
8687
* @ORM\Column(type="string", length=64)
8788
*/
@@ -124,6 +125,11 @@ With some validation added, your class may look something like this::
124125
$this->password = $password;
125126
}
126127

128+
public function getSalt()
129+
{
130+
return null;
131+
}
132+
127133
// other methods, including security methods like getRoles()
128134
}
129135

@@ -146,8 +152,10 @@ example, see the :ref:`Entity Provider <security-crete-user-entity>` article.
146152
only place where you don't need to worry about this is your login form,
147153
since Symfony's Security component handles this for you.
148154

149-
Create a Form for the Model
150-
---------------------------
155+
.. _create-a-form-for-the-model:
156+
157+
Create a Form for the Entity
158+
----------------------------
151159

152160
Next, create the form for the ``User`` entity::
153161

@@ -196,8 +204,9 @@ There are just three fields: ``email``, ``username`` and ``plainPassword``
196204
Handling the Form Submission
197205
----------------------------
198206

199-
Next, you need a controller to handle the form. Start by creating a simple
200-
controller for displaying the registration form::
207+
Next, you need a controller to handle the form rendering and submission. If the
208+
form is submitted, the controller performs the validation and saves the data
209+
into the database::
201210

202211
// src/AppBundle/Controller/RegistrationController.php
203212
namespace AppBundle\Controller;
@@ -223,6 +232,7 @@ controller for displaying the registration form::
223232
// 2) handle the submit (will only happen on POST)
224233
$form->handleRequest($request);
225234
if ($form->isSubmitted() && $form->isValid()) {
235+
226236
// 3) Encode the password (you could also do this via Doctrine listener)
227237
$encoder = $this->get('security.encoder_factory')
228238
->getEncoder($user);
@@ -249,6 +259,45 @@ controller for displaying the registration form::
249259
}
250260
}
251261

262+
To define the algorithm used to encode the password in step 3 configure the
263+
encoder in the security configuration:
264+
265+
.. configuration-block::
266+
267+
.. code-block:: yaml
268+
269+
# app/config/security.yml
270+
security:
271+
encoders:
272+
AppBundle\Entity\User: bcrypt
273+
274+
.. code-block:: xml
275+
276+
<!-- app/config/security.xml -->
277+
<?xml version="1.0" charset="UTF-8" ?>
278+
<srv:container xmlns="http://symfony.com/schema/dic/security"
279+
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
280+
xmlns:srv="http://symfony.com/schema/dic/services"
281+
xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
282+
283+
<config>
284+
<encoder class="AppBundle\Entity\User">bcrypt</encoder>
285+
</config>
286+
</srv:container>
287+
288+
.. code-block:: php
289+
290+
// app/config/security.php
291+
$container->loadFromExtension('security', array(
292+
'encoders' => array(
293+
'AppBundle\Entity\User' => 'bcrypt',
294+
),
295+
));
296+
297+
In this case the recommended ``bcrypt`` algorithm is used. To learn more
298+
about how to encode the users password have a look into the
299+
:ref:`security chapter <book-security-encoding-user-password>`.
300+
252301
.. note::
253302

254303
If you decide to NOT use annotation routing (shown above), then you'll

0 commit comments

Comments
 (0)