PHP package built for Laravel 5.* to easily handle a user email verification and validate the email

@fake-fur

this happened running migrations on empty database

[Illuminate\Database\QueryException]
SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'verified' (SQL: alter table users add verified tinyint(1)
not n
ull default '0', add verification_token varchar(255) null)
[PDOException] SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'verified'

This means you already have the column in your table. Why do you try to run the migration again? Apparently your table is already set up. Did you alter your user table migration to include this verified field?

If so you should remove it from the user table migration.

I think resending a verification email is a very typical thing, I see it on nearly every platform. I think it would be good to add a default route that does the resend and redirects back to the page the user comes from.

<?php

namespace App\Models;

use App\Models\Messages\Dialog;
use App\Traits\HasRoles;
use Carbon\Carbon;
use \Illuminate\Contracts\Auth\CanResetPassword as CanResetPasswordContract;
use Illuminate\Auth\Passwords\CanResetPassword;
use Illuminate\Database\Eloquent\SoftDeletes;
use Illuminate\Foundation\Auth\User as Authenticatable;
use Illuminate\Notifications\Notifiable;
use Illuminate\Support\Facades\Cache;
use Jrean\UserVerification\Traits\UserVerification;
use Watson\Rememberable\Rememberable;

class User extends Authenticatable implements CanResetPasswordContract
{
    use Notifiable, SoftDeletes, HasRoles, Rememberable,  UserVerification, CanResetPassword;

<?php

namespace App\Http\Controllers\Auth;

use App\Http\Controllers\Controller;
use App\Models\User;
use Carbon\Carbon;
use Illuminate\Foundation\Auth\RegistersUsers;
use Illuminate\Http\Request;
use Illuminate\Support\Facades\Validator;
use Jrean\UserVerification\Facades\UserVerification;
use Jrean\UserVerification\Traits\VerifiesUsers;

class RegisterController extends Controller
{
    /*
    |--------------------------------------------------------------------------
    | Register Controller
    |--------------------------------------------------------------------------
    |
    | This controller handles the registration of new users as well as their
    | validation and creation. By default this controller uses a trait to
    | provide this functionality without requiring any additional code.
    |
    */

    use RegistersUsers, VerifiesUsers;

    /**
     * Where to redirect users after registration.
     *
     * @var string
     */
    protected $redirectTo = '/login';
    protected $redirectAfterVerification = '/login';

    /**
     * Create a new controller instance.
     *
     * @return void
     */
    public function __construct()
    {
        parent::__construct();
        $this->middleware('guest', ['except' => ['getVerification', 'getVerificationError']]);
    }

    /**
     * Get a validator for an incoming registration request.
     *
     * @param  array $data
     * @return \Illuminate\Contracts\Validation\Validator
     */
    protected function validator(array $data)
    {
        return Validator::make($data, [
            'accept-rules' => 'accepted',
            'name' => 'required|string|alpha_num|max:32|unique:users',
            'email' => 'required|email|max:128|unique:users',
            'password' => 'required|min:6|max:32|confirmed',
            'g-recaptcha-response' => 'recaptcha',
        ]);
    }

    /**
     * Create a new user instance after a valid registration.
     *
     * @param  array $data
     * @return User
     */
    protected function create(array $data)
    {
        return User::create([
            'name' => $data['name'],
            'email' => $data['email'],
            'password' => bcrypt($data['password']),
            'money_hold_until' => Carbon::now()->addDays(1)
        ]);
    }

    /**
     * Handle a registration request for the application.
     *
     * @param  \Illuminate\Http\Request $request
     * @return \Illuminate\Http\Response
     */
    public function register(Request $request)
    {
        $this->validator($request->all())->validate();

        $user = $this->create($request->all());

        UserVerification::generate($user);
        UserVerification::send($user, env('SITE_NAME') . ' - Подтверждение электронной почты');

        return redirect($this->redirectPath())->with('message', 'Подтвердите аккаунт по электронной почте');
    }
}

if i remove use Jrean\UserVerification\Traits\UserVerification; from user model it work, but not sure that is the best way. what is the solution of this problem? can someone help?

Hello,

I'm getting error: Attempt to assign property of non-object which is here: Line no 255 $user->table = $table; File: UserVerification.php

I have dump $user to check and found it has all the users table field but it does't have "table" key, so that is why it throws this error.

Furthermore, I'm getting "Trying to get property of non-object" on line no 270 if ($user->verified == true) in that same file.

Again I checked $user, now this time issue is that it is an array not an object, so its throwing the error.

So are these bugs already in the package? Or if not that what possible causes it could be with my project? As far as I know I have done all the configuration correctly as mentioned in the documentation.

Thanks, Parth vora

I'm on 2.2 due to the version of laravel I'm using. This may not be a problem in other branches, but I'm raising it while I remember, and will add further details when I can.

I updated a site that was using 2.x and it seems that the email on the verification URL is a new requirement, which my verification email template did not include. Tracing through the code (since users were all getting "verification has failed" errors), a user was selected from the database. However, it was not the correct user - it was just the first user that came out of the users table. This was of course failing the verification since that was not the user being verified, but the fact that it got that user means the reason for failure can be misleading.

Instead, if no email is given in the verification URL, the verification process should realise that earlier, not go and fetch a user with the missing email address, and go down the "user not found" path.

I don't believe this is a security issue, but just the fact that it is possible for the verification process to be even looking at the wrong user could lead to unexpected consequences.

Any success or how-to's leveraging this great package with Laravel 5.4 and Spark? Spark's registration process adds quite a bit of twists to the standard Laravel install, but I'd love to not have to write user email verification from scratch and use this package if possible.

Hello,

I followed the documentation step by step but I'm getting this error and can't find any solution to fix it: ReflectionException in Container.php line 749: Class user.verification does not exist

Do you know how can I fix this?

Hey @jrean,

this PR for #51 is not completely done yet, but maybe you can already test it in any case.

Concerns / todos:

• b/c break for people who rely on the routes from the package to the RegisterController
• Controller needs to be publishable & overwritable to customize things like redirectIfVerified (publish not implemented, overwrite not tested yet)
  • this should be moved to a config file though

Discussion

• Are you fine with doing a redirect back(); which might include an error flash message? Should we namespace the flash message? Like user-verification-error.
• I implemented it using a post with a user_id which makes sense for me, as it is a kind of post action and this allows us to use the resend route also for e.g. for an admin resending a link to a user by triggering a post request with another users user_id

I have a weird issue I'm struggling to debug why the verification_token isn't being saved to the database. It is getting created and emailed correctly. Also if I manually add it everything works fine.

Here is my user model, pretty basic:

<?php

namespace App;

use Illuminate\Notifications\Notifiable;
use Illuminate\Foundation\Auth\User as Authenticatable;

use App\Models;

class User extends Authenticatable
{
    use Notifiable;

    protected $table = 'users';
    public $incrementing = false;
    public $timestamps = true;

    /**
     * The attributes that are mass assignable.
     *
     * @var array
     */
    protected $fillable = [
        'name', 'email', 'password', 'uuid', 'verification_token',
        'remember_token', 'created_at', 'updated_at', 'legacy_verified',
        'verified',
    ];

    /**
     * The attributes that should be hidden for arrays.
     *
     * @var array
     */
    protected $hidden = [
        'password', 'remember_token',
    ];
}

and my registration controller;

<?php
namespace App\Http\Controllers\Auth;

use App\User;
use Validator;
use App\Http\Controllers\Controller;
use Illuminate\Foundation\Auth\RegistersUsers;
use Illuminate\Http\Request;

use Jrean\UserVerification\Traits\VerifiesUsers;
use Jrean\UserVerification\Facades\UserVerification as UserVerification;
use Jrean\UserVerification\Events\VerificationEmailSent;

class RegisterController extends Controller
{
    use RegistersUsers, VerifiesUsers;

    protected $data = []; // the information we send to the view

    /**
     * Where to redirect users after login / registration.
     *
     * @var string
     */
    protected $redirectTo = 'user/registered';

    protected $redirectIfVerified = '/user/signin';

    protected $redirectAfterVerification = '/user/signin';

    //protected $verificationErrorView = '';
    //protected $verificationEmailView = '';

    /**
     * Create a new controller instance.
     *
     * @return void
     */
    public function __construct()
    {
         $this->middleware('guest', [
            'except' => ['getVerification', 'getVerificationError']
         ]);
    }

    /**
     * Get a validator for an incoming registration request.
     *
     * @param array $data
     *
     * @return \Illuminate\Contracts\Validation\Validator
     */
    protected function validator(array $data)
    {
        return Validator::make($data, [
            'email'    => 'required|email|max:255|unique:users',
            'password' => 'required|min:8|confirmed',
        ]);
    }

    /**
     * Create a new user instance after a valid registration.
     *
     * @param array $data
     *
     * @return User
     */
    protected function create(array $data)
    {
        $user = new \App\User();

        return $user->create([
            'email'    => $data['email'],
            'password' => bcrypt($data['password']),
            'uuid'     => \Uuid::generate(4),
        ]);
    }

    /**
     * Handle a registration request for the application.
     *
     * @param  \Illuminate\Http\Request  $request
     * @return \Illuminate\Http\Response
     */
    public function register(Request $request)
    {
        $this->validator($request->all())->validate();

        $user = $this->create($request->all());
        $this->guard()->login($user);

        UserVerification::generate($user);
        //UserVerification::send($user, 'Verify Your Account');

        $token = $user->verification_token . '?email=' . urlencode($user->email);

        // @FIXME: Clean this up
        \Mail::send('mail.empty', [], function (\Illuminate\Mail\Message $message) use ($user, $token) {
            $message
            ->to($user->email, $user->email)
            ->embedData([
                'subject' => 'Verify',
                'template_id' => '6620a3f6-66df-4a42-9d4b-5bae3d974648',
                'categories' => ['unverified'],
                'personalizations' => [
                    [
                        'substitutions' => [
                            '%name%' => '',
                            '%verification_code%' => url('user/verify') . '/' . $token,
                            '%user_reference_id%' => strtoupper($user->uuid),
                        ],
                    ],
                ],
                // Unsubscribed users will want this
                'mail_settings' => [
                    'bypass_list_management' => [
                        'enable' => true,
                    ],
                ],
                // To reduce the potential of being marked as spam we need
                // to disable tracking.
                'tracking_settings' => [
                    'click_tracking' => [
                        'enable' => false,
                    ],
                    'subscription_tracking' => [
                        'enable' => false,
                    ],
                    'ganalytics' => [
                        'enable' => false,
                    ],
                ],
            ], 'sendgrid/x-smtpapi');
        });

        if($request->ajax()) {
            return response()->json([
                'result'  => 'success',
                'message' => trans('user.registered_dropdown'),
                'html'    => null,
            ], 200);
        }
        else {
            return redirect($this->redirectPath());
        }
    }
}

No exceptions and everything else works.

Error; Trait method redirectIfVerified has not been applied, because there are collisions with other trait methods on App\Http\Controllers\Auth\AuthController

I have this code:

<?php

namespace App\Http\Controllers\Auth;

use App\User;
use Validator;
use App\Http\Controllers\Controller;
use Illuminate\Foundation\Auth\ThrottlesLogins;
use Illuminate\Foundation\Auth\AuthenticatesAndRegistersUsers;

use Jrean\UserVerification\Traits\VerifiesUsers;
use Jrean\UserVerification\Traits\RedirectsUsers;

use UserVerification;
use Auth;
use Carbon\Carbon;

class AuthController extends Controller
{
    /*
    |--------------------------------------------------------------------------
    | Registration & Login Controller
    |--------------------------------------------------------------------------
    |
    | This controller handles the registration of new users, as well as the
    | authentication of existing users. By default, this controller uses
    | a simple trait to add these behaviors. Why don't you explore it?
    |
    */

    use AuthenticatesAndRegistersUsers, ThrottlesLogins, VerifiesUsers, RedirectsUsers;


    /**
     * Where to redirect users after login / registration.
     *
     * @var string
     */
    protected $redirectTo = '/';
    protected $redirectIfVerified = '/';

If I add UserVerification trait to the User model I start getting:

Symfony\Component\Debug\Exception\FatalErrorException: Cannot use Jrean\UserVerification\Facades\UserVerification as UserVerification because the name is already in use in /my_project/vendor/jrean/laravel-user-verification/src/Traits/VerifiesUsers.php:11

Without the Jrean\UserVerification\Traits\UserVerification trait in the User model it works when I access any route.

Is anybody else getting this?

https://github.com/jrean/laravel-user-verification/blob/69527fdd760cdd29853846e03504b567aac58c8a/src/UserVerification.php#L271

https://github.com/jrean/laravel-user-verification/blob/69527fdd760cdd29853846e03504b567aac58c8a/src/UserVerification.php#L342

The above two places make it almost impossible to use a different connection than the default(actually it is possible to get around it by changing DB facade temporarily, but it's not the right way), so i would suggest changing the second constructor parameter to $connection,

1. then at places where it needs schema, just do $connection->getSchemaBuilder(),
2. and replace DB with $connections in the above places.
3. And of course, you need to modify the service provider slightly as well. I would create a PR if you want it.

Hi, I have 3 personas who are authenticable. I discovered that UserVerification class on line 52 kept getting model from the auth.providers.users.model. I need it it to validate against the customer provider not users. How do I go about this?

Hi, Beautiful piece of work. I wish to request that the "verified" and "verification_token" column names be customizable based on info supplied on the published config file because currently working on a solution that required the phone number to be verified. I would have preferred an "email_verified" column name to differentiate them both