diff options
| author | Camil Staps | 2016-09-04 23:30:15 +0200 | 
|---|---|---|
| committer | Camil Staps | 2016-09-04 23:30:15 +0200 | 
| commit | c61b156f1bd93ec4aadd8adc78523b42b0232918 (patch) | |
| tree | cd9bcb6f889dcf554818246957bed54eb14c9fbe /config/auth.php | |
| parent | Use blade templates (diff) | |
User creation and authentication
Diffstat (limited to 'config/auth.php')
| -rw-r--r-- | config/auth.php | 88 | 
1 files changed, 88 insertions, 0 deletions
| diff --git a/config/auth.php b/config/auth.php new file mode 100644 index 0000000..2331863 --- /dev/null +++ b/config/auth.php @@ -0,0 +1,88 @@ +<?php + +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. +	| +	*/ + +	'defaults' => [ +		'guard' => env('AUTH_GUARD', 'basic-http'), +	], + +	/* +	|-------------------------------------------------------------------------- +	| 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" +	| +	*/ + +	'guards' => [ +		'basic-http' => ['driver' => 'basic', '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" +	| +	*/ + +	'providers' => [ +		'users' => [ +			'driver' => 'eloquent', +			'model' => HebrewParseTrainer\User::class, +		], +	], + +	/* +	|-------------------------------------------------------------------------- +	| 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. +	| +	*/ + +	'passwords' => [ +		// +	], + +]; | 
