This tutorial has a new version, check it out!
> Symfony 3 > Symfony 3 Security: Beautiful Authentication, Powerful Authorization
Login to bookmark this video
Buy Access to Course
02.

The UserInterface Methods (Keep some Blank!)

Share this awesome video!

|

Our job: fill in the 5 methods from UserInterface. But check this out - I'm going rogue - I'm only going to implement 2 of them: getUsername() and getRoles().

getUsername()

First getUsername()... is super-unimportant. Just return any unique user string you want - a username, an email, a uuid, a funny, but unique joke - whatever. This is only used to show you who is logged in when you're debugging.

In our app, our users won't have a username - but they will have an email. Add a private $email property then just use that in getUsername(): return $this->email:

48 lines | src/AppBundle/Entity/User.php
// ... lines 1 - 7
class User implements UserInterface
{
private $email;
// needed by the security system
public function getUsername()
{
return $this->email;
}
// ... lines 17 - 46
}

And add a setter for that method:

48 lines | src/AppBundle/Entity/User.php
// ... lines 1 - 7
class User implements UserInterface
{
// ... lines 10 - 42
public function setEmail($email)
{
$this->email = $email;
}
}

We'll eventually need that to create users.

getRoles()

Cool: half-way done! Now: getRoles(). We'll talk roles later with authorization, but these are basically permissions we want to give the user. For now, give every user the same, one role: ROLE_USER:

42 lines | src/AppBundle/Entity/User.php
// ... lines 1 - 7
class User implements UserInterface
{
// ... lines 10 - 16
public function getRoles()
{
return ['ROLE_USER'];
}
// ... lines 21 - 40
}

What about getPassword(), getSalt() and eraseCredentials()?

So what about getPassword(), getSalt() and eraseCredentials()? Keep them blank:

42 lines | src/AppBundle/Entity/User.php
// ... lines 1 - 7
class User implements UserInterface
{
// ... lines 10 - 21
public function getPassword()
{
// leaving blank - I don't need/have a password!
}
public function getSalt()
{
// leaving blank - I don't need/have a password!
}
public function eraseCredentials()
{
// leaving blank - I don't need/have a password!
}
// ... lines 36 - 40
}

Whaat? It turns out, you only need these if your app is personally responsible for storing and checking user passwords. In our app - to start - we're not going to have passwords: we're just going to let anyone login with a single, central, hardcoded password. But there are also real-world situations where your app isn't responsible for managing and checking passwords.

If you have one of these, feel ok leaving these blank.

Setting up the User Entity

So in our application, we want to store users in the database. So let's set this class up with Doctrine. Copy the use statement from SubFamily and paste it here:

63 lines | src/AppBundle/Entity/User.php
// ... lines 1 - 6
use Doctrine\ORM\Mapping as ORM;
// ... lines 8 - 63

Next, I'll put my cursor inside the class, press Command+N - or use the "Code"->"Generate" menu - and select "ORM class":

63 lines | src/AppBundle/Entity/User.php
// ... lines 1 - 8
/**
* @ORM\Entity
* @ORM\Table(name="user")
*/
class User implements UserInterface
// ... lines 14 - 63

Next, add a private $id property and press Command+N one more time. This time, choose "ORM annotation" and highlight both fields:

63 lines | src/AppBundle/Entity/User.php
// ... lines 1 - 12
class User implements UserInterface
{
/**
* @ORM\Id
* @ORM\GeneratedValue(strategy="AUTO")
* @ORM\Column(type="integer")
*/
private $id;
/**
* @ORM\Column(type="string", unique=true)
*/
private $email;
// ... lines 26 - 61
}

Oh, and while we're here, let's add unique=true for the email field:

63 lines | src/AppBundle/Entity/User.php
// ... lines 1 - 12
class User implements UserInterface
{
// ... lines 15 - 21
/**
* @ORM\Column(type="string", unique=true)
*/
private $email;
// ... lines 26 - 61
}

Perfect: we have a fully functional User class. Sure, it only has an id and email, but that's enough!

Since we just added a new entity, let's generate a migration:

./bin/console doctrine:migrations:diff

I'll copy the class and open it up quickly, just to make sure it looks right:

35 lines | app/DoctrineMigrations/Version20160524105319.php
// ... lines 1 - 10
class Version20160524105319 extends AbstractMigration
{
// ... lines 13 - 15
public function up(Schema $schema)
{
// this up() migration is auto-generated, please modify it to your needs
$this->abortIf($this->connection->getDatabasePlatform()->getName() != 'mysql', 'Migration can only be executed safely on \'mysql\'.');
$this->addSql('CREATE TABLE user (id INT AUTO_INCREMENT NOT NULL, email VARCHAR(255) NOT NULL, UNIQUE INDEX UNIQ_8D93D649E7927C74 (email), PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci ENGINE = InnoDB');
}
// ... lines 23 - 26
public function down(Schema $schema)
{
// this down() migration is auto-generated, please modify it to your needs
$this->abortIf($this->connection->getDatabasePlatform()->getName() != 'mysql', 'Migration can only be executed safely on \'mysql\'.');
$this->addSql('DROP TABLE user');
}
}

Looks great!

Adding User Fixtures

Finally, let's add some users to the database. Open our trusty fixtures.yml. I'll copy the SubFamily section, change the class to User and give these keys user_1..10:

26 lines | src/AppBundle/DataFixtures/ORM/fixtures.yml
// ... lines 1 - 22
AppBundle\Entity\User:
user_{1..10}:
// ... lines 25 - 26

Then, the only field is email. Set it to weaverryan+<current()>@gmail.com:

26 lines | src/AppBundle/DataFixtures/ORM/fixtures.yml
// ... lines 1 - 22
AppBundle\Entity\User:
user_{1..10}:
email: weaverryan+<current()>@gmail.com

The current() function will return 1 through 10 as Alice loops through our set. That'll give us weaverryan+1@gmail.com up to weaverryan+10@gmail.com. And if you didn't know, Gmail ignores everything after a + sign, so these will all be delivered to weaverryan@gmail.com. There's your Internet hack for the day.

Ok, let's roll! Don't forget to run the migration first:

./bin/console doctrine:migrations:migrate

And then load the fixtures:

./bin/console doctrine:fixtures:load

Hey hey: you've got users in the database. Let's let 'em login.