Adding custom (guarded) field to Laravel 5.3 Auth

Question

I am trying to add a custom field 'role' to Laravel 5.3 User Auth. The role will determine whether the user is admin amongst other roles and so because the Auth scaffolding uses mass assignable attributes, there is a vulnerability.

Therefore I have changed my User model to:

protected $guarded = [
  'role'
];

RegisterController I have added my custom fields (a default user will have the role = customer);

   return User::create([
        'name' => $data['name'],
        'email' => $data['email'],
        'password' => bcrypt($data['password']),
        'facebook_id' => $data['facebook_id'],
        'linkedin_id' => $data['linkedin_id'],
        'avatar' => $data['avatar'],
        'token' => $data['token'],
        'role' => 'customer',

I am getting this error message:

SQLSTATE[HY000]: General error: 1364 Field 'role' doesn't have a default >value (SQL: insert into users (name, email, password, >facebook_id, linkedin_id, avatar, token, updated_at, >created_at) values (name, [email protected], hashed password, , , , , >2017-01-20 17:21:16, 2017-01-20 17:21:16))

Can't for the life of me figure it out.

I was thinking that maybe I don't use the mass assignable input, but I have a feeling that may mess up the rest of the Auth scaffold.

Thanks for any help

Moak · Accepted Answer · 2017-01-20 19:21:30Z

1

An easy way to set the default role is to actually define it in the model

class User extends Model
{
    protected $attributes = [
        'role' => 'customer',
    ];

    protected $guarded = [
      'role'
    ];
    //...

Now when you use the create method and don't pass the the 'role' attribute, the insert will use the value 'customer'

edited Jan 20, 2017 at 19:21

answered Jan 20, 2017 at 19:03

Moak

12.9k27 gold badges117 silver badges168 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

the_peacock Over a year ago

OK thanks, I understand how this works, I am still a bit confused as to why my initial method fails though..! Cheers

Moak Over a year ago

the whole point of guarded is you can not pass create(['role'=>'foo'])

Joe · Accepted Answer · 2017-01-21 13:07:36Z

0

In your migration for the users table where you add the role field, you either need to set the field as nullable, or give it a default value, so that when you mass assign without it, the database knows how to deal with that field.

Schema::table('users' function(Blueprint $table){
  $table->string('role')->default('customer');
});

or

Schema::table('users' function(Blueprint $table){
  $table->string('role')->nullable();
});

if your code can deal with a null role value.

answered Jan 21, 2017 at 13:07

Joe

4,7583 gold badges31 silver badges35 bronze badges

Collectives™ on Stack Overflow

Adding custom (guarded) field to Laravel 5.3 Auth

2 Answers 2

2 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related