auth.php 3.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112
  1. <?php
  2. return [
  3. /*
  4. |--------------------------------------------------------------------------
  5. | Authentication Defaults
  6. |--------------------------------------------------------------------------
  7. |
  8. | This option controls the default authentication "guard" and password
  9. | reset options for your application. You may change these defaults
  10. | as required, but they're a perfect start for most applications.
  11. |
  12. */
  13. 'defaults' => [
  14. 'guard' => 'web',
  15. 'passwords' => 'users',
  16. ],
  17. /*
  18. |--------------------------------------------------------------------------
  19. | Authentication Guards
  20. |--------------------------------------------------------------------------
  21. |
  22. | Next, you may define every authentication guard for your application.
  23. | Of course, a great default configuration has been defined for you
  24. | here which uses session storage and the Eloquent user provider.
  25. |
  26. | All authentication drivers have a user provider. This defines how the
  27. | users are actually retrieved out of your database or other storage
  28. | mechanisms used by this application to persist your user's data.
  29. |
  30. | Supported: "session", "token"
  31. |
  32. */
  33. 'guards' => [
  34. 'web' => [
  35. 'driver' => 'session',
  36. 'provider' => 'users',
  37. ],
  38. 'api' => [
  39. 'driver' => 'token',
  40. 'provider' => 'users',
  41. ],
  42. 'wechat' => [
  43. 'driver' => 'session',
  44. 'provider' => 'fans',
  45. ],
  46. ],
  47. /*
  48. |--------------------------------------------------------------------------
  49. | User Providers
  50. |--------------------------------------------------------------------------
  51. |
  52. | All authentication drivers have a user provider. This defines how the
  53. | users are actually retrieved out of your database or other storage
  54. | mechanisms used by this application to persist your user's data.
  55. |
  56. | If you have multiple user tables or models you may configure multiple
  57. | sources which represent each model / table. These sources may then
  58. | be assigned to any extra authentication guards you have defined.
  59. |
  60. | Supported: "database", "eloquent"
  61. |
  62. */
  63. 'providers' => [
  64. 'users' => [
  65. 'driver' => 'eloquent',
  66. 'model' => App\User::class,
  67. ],
  68. 'fans' => [
  69. 'driver' => 'eloquent',
  70. 'model' => \Encore\WeChat\Models\Fan::class,
  71. ],
  72. // 'users' => [
  73. // 'driver' => 'database',
  74. // 'table' => 'users',
  75. // ],
  76. ],
  77. /*
  78. |--------------------------------------------------------------------------
  79. | Resetting Passwords
  80. |--------------------------------------------------------------------------
  81. |
  82. | You may specify multiple password reset configurations if you have more
  83. | than one user table or model in the application and you want to have
  84. | separate password reset settings based on the specific user types.
  85. |
  86. | The expire time is the number of minutes that the reset token should be
  87. | considered valid. This security feature keeps tokens short-lived so
  88. | they have less time to be guessed. You may change this as needed.
  89. |
  90. */
  91. 'passwords' => [
  92. 'users' => [
  93. 'provider' => 'users',
  94. 'table' => 'password_resets',
  95. 'expire' => 60,
  96. ],
  97. ],
  98. ];