| 
									
										
										
										
											2015-02-06 04:39:52 +01:00
										 |  |  | <?php | 
					
						
							| 
									
										
										
										
											2016-10-05 06:52:15 +02:00
										 |  |  | /** | 
					
						
							|  |  |  |  * auth.php | 
					
						
							|  |  |  |  * Copyright (C) 2016 thegrumpydictator@gmail.com | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * This software may be modified and distributed under the terms of the | 
					
						
							|  |  |  |  * Creative Commons Attribution-ShareAlike 4.0 International License. | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * See the LICENSE file for details. | 
					
						
							|  |  |  |  */ | 
					
						
							| 
									
										
										
										
											2016-05-20 08:57:45 +02:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2015-02-06 04:39:52 +01:00
										 |  |  | return [ | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2016-09-16 06:19:40 +02:00
										 |  |  |     /* | 
					
						
							|  |  |  |     |-------------------------------------------------------------------------- | 
					
						
							|  |  |  |     | 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' => 'web', | 
					
						
							| 
									
										
										
										
											2016-01-08 15:59:21 +01:00
										 |  |  |         'passwords' => 'users', | 
					
						
							|  |  |  |     ], | 
					
						
							| 
									
										
										
										
											2016-09-16 06:19:40 +02:00
										 |  |  | 
 | 
					
						
							|  |  |  |     /* | 
					
						
							|  |  |  |     |-------------------------------------------------------------------------- | 
					
						
							|  |  |  |     | 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' => [ | 
					
						
							| 
									
										
										
										
											2016-01-08 15:59:21 +01:00
										 |  |  |         'web' => [ | 
					
						
							| 
									
										
										
										
											2016-09-16 06:19:40 +02:00
										 |  |  |             'driver' => 'session', | 
					
						
							| 
									
										
										
										
											2016-01-08 15:59:21 +01:00
										 |  |  |             'provider' => 'users', | 
					
						
							|  |  |  |         ], | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  |         'api' => [ | 
					
						
							| 
									
										
										
										
											2016-09-16 06:19:40 +02:00
										 |  |  |             'driver' => 'token', | 
					
						
							| 
									
										
										
										
											2016-01-08 15:59:21 +01:00
										 |  |  |             'provider' => 'users', | 
					
						
							|  |  |  |         ], | 
					
						
							|  |  |  |     ], | 
					
						
							| 
									
										
										
										
											2015-02-06 04:39:52 +01:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2016-09-16 06:19:40 +02:00
										 |  |  |     /* | 
					
						
							|  |  |  |     |-------------------------------------------------------------------------- | 
					
						
							|  |  |  |     | 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" | 
					
						
							|  |  |  |     | | 
					
						
							|  |  |  |     */ | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2016-01-08 15:59:21 +01:00
										 |  |  |     'providers' => [ | 
					
						
							|  |  |  |         'users' => [ | 
					
						
							|  |  |  |             'driver' => 'eloquent', | 
					
						
							| 
									
										
										
										
											2016-09-16 06:19:40 +02:00
										 |  |  |             'model' => FireflyIII\User::class, | 
					
						
							| 
									
										
										
										
											2016-01-08 15:59:21 +01:00
										 |  |  |         ], | 
					
						
							|  |  |  |     ], | 
					
						
							| 
									
										
										
										
											2015-02-06 04:39:52 +01:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2016-09-16 06:19:40 +02:00
										 |  |  |     /* | 
					
						
							|  |  |  |     |-------------------------------------------------------------------------- | 
					
						
							|  |  |  |     | 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. | 
					
						
							|  |  |  |     | | 
					
						
							|  |  |  |     */ | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2016-01-08 15:59:21 +01:00
										 |  |  |     'passwords' => [ | 
					
						
							|  |  |  |         'users' => [ | 
					
						
							|  |  |  |             'provider' => 'users', | 
					
						
							| 
									
										
										
										
											2016-09-16 06:19:40 +02:00
										 |  |  |             'table' => 'password_resets', | 
					
						
							|  |  |  |             'expire' => 60, | 
					
						
							| 
									
										
										
										
											2016-01-08 15:59:21 +01:00
										 |  |  |         ], | 
					
						
							| 
									
										
										
										
											2015-06-27 08:06:24 +02:00
										 |  |  |     ], | 
					
						
							| 
									
										
										
										
											2015-02-06 04:39:52 +01:00
										 |  |  | 
 | 
					
						
							|  |  |  | ]; |