auth.php 3.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113
  1. <?php
  2. return [
  3. /*
  4. |--------------------------------------------------------------------------
  5. | Authentication Defaults
  6. |--------------------------------------------------------------------------
  7. |
  8. | This option defines the default authentication "guard" and password
  9. | reset "broker" for your application. You may change these values
  10. | as required, but they're a perfect start for most applications.
  11. |
  12. */
  13. 'defaults' => [
  14. 'guard' => 'customer',
  15. 'passwords' => 'customers',
  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. | which utilizes session storage plus the Eloquent user provider.
  25. |
  26. | All authentication guards have a user provider, which defines how the
  27. | users are actually retrieved out of your database or other storage
  28. | system used by the application. Typically, Eloquent is utilized.
  29. |
  30. | Supported: "session"
  31. |
  32. */
  33. 'guards' => [
  34. 'customer' => [
  35. 'driver' => 'session',
  36. 'provider' => 'customers',
  37. ],
  38. 'admin' => [
  39. 'driver' => 'session',
  40. 'provider' => 'admins',
  41. ],
  42. ],
  43. /*
  44. |--------------------------------------------------------------------------
  45. | User Providers
  46. |--------------------------------------------------------------------------
  47. |
  48. | All authentication guards have a user provider, which defines how the
  49. | users are actually retrieved out of your database or other storage
  50. | system used by the application. Typically, Eloquent is utilized.
  51. |
  52. | If you have multiple user tables or models you may configure multiple
  53. | providers to represent the model / table. These providers may then
  54. | be assigned to any extra authentication guards you have defined.
  55. |
  56. | Supported: "database", "eloquent"
  57. |
  58. */
  59. 'providers' => [
  60. 'customers' => [
  61. 'driver' => 'eloquent',
  62. 'model' => Webkul\Customer\Models\Customer::class,
  63. ],
  64. 'admins' => [
  65. 'driver' => 'eloquent',
  66. 'model' => Webkul\User\Models\Admin::class,
  67. ],
  68. ],
  69. /*
  70. |--------------------------------------------------------------------------
  71. | Resetting Passwords
  72. |--------------------------------------------------------------------------
  73. |
  74. | These configuration options specify the behavior of Laravel's password
  75. | reset functionality, including the table utilized for token storage
  76. | and the user provider that is invoked to actually retrieve users.
  77. |
  78. | The expiry time is the number of minutes that each reset token will be
  79. | considered valid. This security feature keeps tokens short-lived so
  80. | they have less time to be guessed. You may change this as needed.
  81. |
  82. | The throttle setting is the number of seconds a user must wait before
  83. | generating more password reset tokens. This prevents the user from
  84. | quickly generating a very large amount of password reset tokens.
  85. |
  86. */
  87. 'passwords' => [
  88. 'customers' => [
  89. 'provider' => 'customers',
  90. 'table' => 'customer_password_resets',
  91. 'expire' => 60,
  92. 'throttle' => 60,
  93. ],
  94. 'admins' => [
  95. 'provider' => 'admins',
  96. 'table' => 'admin_password_resets',
  97. 'expire' => 60,
  98. 'throttle' => 60,
  99. ],
  100. ],
  101. ];