composer require konekt/user
touch config/concord.php

Edit config/concord.php and add this content to it:


return [
    'modules' => [

Laravel 5.4: Register The Service Provider Edit config/app.php and add this line to the providers array (below 'Package Service Providers', always above 'Application Service Providers'):


Test if all worked well by invoking the command:

php artisan concord:modules

Now you should see this:

| #  | Name               | Kind   | Version | Id          | Namespace       |
| 1. | Konekt User Module | Module | 1.1.0  | konekt.user | Konekt\User     |

TIP: Try php artisan concord:modules -a to see ALL modules


Configure .env, along with a database.

Afterwards run the migrations:

php artisan migrate

The user module contains 2 migrations out of the box

Laravel 5.8 and Bigint Compatibility


As of Laravel 5.8, migration stubs use the bigIncrements method on ID columns by default. Previously, ID columns were created using the increments method.

Foreign key columns must be of the same type. Therefore, a column created using the increments method can not reference a column created using the bigIncrements method.

This small change is a big source of problems for packages that define references to the default Laravel user table.

This package contains the Profile model having the profile table beneath. The profile belongs to a user via the user_id key. In order to keep the above mentioned compatibility, the user_id field must be the same type (int or bigint) as the user table's id field.

Unfortunately detecting if Laravel version is 5.8+ is not enough to find out whether is bigInt or int, since the host application could use bigInt even before Laravel 5.8 and can still use plain int even after 5.8.

Best solution would be to detect the actual field type and act accordingly. The problem with that solution is that it prevents from altering tables with enum fields, breaking the migrations in this package, especially with MySQL:

Unknown database type enum requested, Doctrine\DBAL\Platforms\MySQL57Platform may not support it.

In case you created your project with Laravel 5.8, then the user table is likely already a bigInt.


You can explicitly define whether to use bigInt for referring to the field by setting the value of USER_ID_IS_BIGINT to true or false in your .env file.

If there's no explicit value defined for USER_ID_IS_BIGINT then it'll be true in Laravel 5.8+ and false for any earlier version.

This can solve migration problems like:

Migrating: 2016_12_18_121118_create_profiles_table

   Illuminate\Database\QueryException: SQLSTATE[HY000]: General error: 1005 Can't create table
   `vanilo`.`#sql-9a5_a6` (errno: 150 "Foreign key constraint is incorrectly formed")
    alter table `profiles`
    add constraint `profiles_user_id_foreign`
    foreign key (`user_id`) references `users` (`id`)

Laravel Auth Support

First, run php artisan make:auth in your application.

If the "final" user class is not going to be App\User then don't forget to modify model class this to your app's config/auth.php file:

    'providers' => [
        'users' => [
            'driver' => 'eloquent',
            // 'model' => App\User::class <- change this to:
            'model' => Konekt\User\Models\User::class,

OR: Another approach is to keep App\User but modify the class to extend this user model:

namespace App;

// No need to use Laravel default traits and properties as
// they're already present in the base class

class User extends \Konekt\User\Models\User

And add this to you AppServiceProviders's boot method:

   $this->app->concord->registerModel(\Konekt\User\Contracts\User::class, \App\User::class);

Next: Active/Inactive Status »