mirror of
				https://github.com/crater-invoice/crater.git
				synced 2025-10-31 13:41:09 -04:00 
			
		
		
		
	
		
			
				
	
	
		
			120 lines
		
	
	
		
			3.9 KiB
		
	
	
	
		
			PHP
		
	
	
	
	
	
			
		
		
	
	
			120 lines
		
	
	
		
			3.9 KiB
		
	
	
	
		
			PHP
		
	
	
	
	
	
| <?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' => 'api',
 | |
|         '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: "session", "token"
 | |
|     |
 | |
|     */
 | |
| 
 | |
|     'guards' => [
 | |
|         'web' => [
 | |
|             'driver' => 'session',
 | |
|             'provider' => 'users',
 | |
|         ],
 | |
| 
 | |
|         'api' => [
 | |
|             'driver' => 'passport',
 | |
|             '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' => Crater\User::class,
 | |
|         ],
 | |
| 
 | |
|         // '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,
 | |
|         ],
 | |
|     ],
 | |
| 
 | |
|     /*
 | |
|     |--------------------------------------------------------------------------
 | |
|     | OAuth Proxy Authentication
 | |
|     |--------------------------------------------------------------------------
 | |
|     |
 | |
|     | If you are planning to use your application to self-authenticate as a
 | |
|     | proxy, you can define the client and grant type to use here. This is
 | |
|     | sometimes the case when a trusted Single Page Application doesn't
 | |
|     | use a backend to send the authentication request, but instead
 | |
|     | relies on the API to handle proxying the request to itself.
 | |
|     |
 | |
|      */
 | |
|     'proxy' => [
 | |
|         'client_id' => env('PROXY_OAUTH_CLIENT_ID'),
 | |
|         'client_secret' => env('PROXY_OAUTH_CLIENT_SECRET'),
 | |
|         'grant_type' => env('PROXY_OAUTH_GRANT_TYPE'),
 | |
|     ],
 | |
| ];
 |