Change from lumen 5.2 to laravel 5.3 (Resolves #1)

1 files changed, 89 insertions, 75 deletions

diff --git a/config/auth.php b/config/auth.php
index 2331863..5e571a9 100644
--- a/config/auth.php
+++ b/config/auth.php
@@ -2,87 +2,101 @@
 
 return [
 
-	/*
-	|--------------------------------------------------------------------------
-	| Authentication Defaults
-	|--------------------------------------------------------------------------
-	|
-	| This option controls the default authentication "guard" and password
-	| reset options for your application. You may change these defaults
-	| as required, but they're a perfect start for most applications.
-	|
-	*/
+    /*
+    |--------------------------------------------------------------------------
+    | Authentication Defaults
+    |--------------------------------------------------------------------------
+    |
+    | This option controls the default authentication "guard" and password
+    | reset options for your application. You may change these defaults
+    | as required, but they're a perfect start for most applications.
+    |
+    */
 
-	'defaults' => [
-		'guard' => env('AUTH_GUARD', 'basic-http'),
-	],
+    'defaults' => [
+        'guard' => 'web',
+        'passwords' => 'users',
+    ],
 
-	/*
-	|--------------------------------------------------------------------------
-	| Authentication Guards
-	|--------------------------------------------------------------------------
-	|
-	| Next, you may define every authentication guard for your application.
-	| Of course, a great default configuration has been defined for you
-	| here which uses session storage and the Eloquent user provider.
-	|
-	| All authentication drivers have a user provider. This defines how the
-	| users are actually retrieved out of your database or other storage
-	| mechanisms used by this application to persist your user's data.
-	|
-	| Supported: "token"
-	|
-	*/
+    /*
+    |--------------------------------------------------------------------------
+    | Authentication Guards
+    |--------------------------------------------------------------------------
+    |
+    | Next, you may define every authentication guard for your application.
+    | Of course, a great default configuration has been defined for you
+    | here which uses session storage and the Eloquent user provider.
+    |
+    | All authentication drivers have a user provider. This defines how the
+    | users are actually retrieved out of your database or other storage
+    | mechanisms used by this application to persist your user's data.
+    |
+    | Supported: "session", "token"
+    |
+    */
 
-	'guards' => [
-		'basic-http' => ['driver' => 'basic', 'provider' => 'users'],
-	],
+    'guards' => [
+        'web' => [
+            'driver' => 'session',
+            'provider' => 'users',
+        ],
 
-	/*
-	|--------------------------------------------------------------------------
-	| User Providers
-	|--------------------------------------------------------------------------
-	|
-	| All authentication drivers have a user provider. This defines how the
-	| users are actually retrieved out of your database or other storage
-	| mechanisms used by this application to persist your user's data.
-	|
-	| If you have multiple user tables or models you may configure multiple
-	| sources which represent each model / table. These sources may then
-	| be assigned to any extra authentication guards you have defined.
-	|
-	| Supported: "database", "eloquent"
-	|
-	*/
+        'api' => [
+            'driver' => 'token',
+            'provider' => 'users',
+        ],
+    ],
 
-	'providers' => [
-		'users' => [
-			'driver' => 'eloquent',
-			'model' => HebrewParseTrainer\User::class,
-		],
-	],
+    /*
+    |--------------------------------------------------------------------------
+    | User Providers
+    |--------------------------------------------------------------------------
+    |
+    | All authentication drivers have a user provider. This defines how the
+    | users are actually retrieved out of your database or other storage
+    | mechanisms used by this application to persist your user's data.
+    |
+    | If you have multiple user tables or models you may configure multiple
+    | sources which represent each model / table. These sources may then
+    | be assigned to any extra authentication guards you have defined.
+    |
+    | Supported: "database", "eloquent"
+    |
+    */
 
-	/*
-	|--------------------------------------------------------------------------
-	| Resetting Passwords
-	|--------------------------------------------------------------------------
-	|
-	| Here you may set the options for resetting passwords including the view
-	| that is your password reset e-mail. You may also set the name of the
-	| table that maintains all of the reset tokens for your application.
-	|
-	| You may specify multiple password reset configurations if you have more
-	| than one user table or model in the application and you want to have
-	| separate password reset settings based on the specific user types.
-	|
-	| The expire time is the number of minutes that the reset token should be
-	| considered valid. This security feature keeps tokens short-lived so
-	| they have less time to be guessed. You may change this as needed.
-	|
-	*/
+    'providers' => [
+        'users' => [
+            'driver' => 'eloquent',
+            'model' => HebrewParseTrainer\User::class,
+        ],
 
-	'passwords' => [
-		//
-	],
+        // 'users' => [
+        //     'driver' => 'database',
+        //     'table' => 'users',
+        // ],
+    ],
+
+    /*
+    |--------------------------------------------------------------------------
+    | Resetting Passwords
+    |--------------------------------------------------------------------------
+    |
+    | You may specify multiple password reset configurations if you have more
+    | than one user table or model in the application and you want to have
+    | separate password reset settings based on the specific user types.
+    |
+    | The expire time is the number of minutes that the reset token should be
+    | considered valid. This security feature keeps tokens short-lived so
+    | they have less time to be guessed. You may change this as needed.
+    |
+    */
+
+    'passwords' => [
+        'users' => [
+            'provider' => 'users',
+            'table' => 'password_resets',
+            'expire' => 60,
+        ],
+    ],
 
 ];