質問編集履歴

3

初心者マーク

2020/03/12 22:40

投稿

tenlife
tenlife

スコア70

test CHANGED
File without changes
test CHANGED
@@ -446,22 +446,152 @@
446
446
 
447
447
  'driver' => 'session',
448
448
 
449
+ 'provider' => 'admins',
450
+
451
+ ],
452
+
453
+
454
+
455
+ 'api' => [
456
+
457
+ 'driver' => 'token',
458
+
449
459
  'provider' => 'users',
450
460
 
461
+ 'hash' => false,
462
+
451
463
  ],
452
464
 
453
-
465
+ ],
466
+
467
+
468
+
454
-
469
+ /*
470
+
471
+ |--------------------------------------------------------------------------
472
+
473
+ | User Providers
474
+
475
+ |--------------------------------------------------------------------------
476
+
477
+ |
478
+
479
+ | All authentication drivers have a user provider. This defines how the
480
+
481
+ | users are actually retrieved out of your database or other storage
482
+
483
+ | mechanisms used by this application to persist your user's data.
484
+
485
+ |
486
+
487
+ | If you have multiple user tables or models you may configure multiple
488
+
489
+ | sources which represent each model / table. These sources may then
490
+
491
+ | be assigned to any extra authentication guards you have defined.
492
+
493
+ |
494
+
495
+ | Supported: "database", "eloquent"
496
+
497
+ |
498
+
499
+ */
500
+
501
+
502
+
503
+ 'providers' => [
504
+
455
- 'api' => [
505
+ 'users' => [
456
-
506
+
457
- 'driver' => 'token',
507
+ 'driver' => 'eloquent',
508
+
509
+ 'model' => App\Models\User::class,
510
+
511
+ ],
512
+
513
+
514
+
515
+ 'admins' => [
516
+
517
+ 'driver' => 'eloquent',
518
+
519
+ 'model' => App\Models\Admin::class,
520
+
521
+ ],
522
+
523
+
524
+
525
+ // 'users' => [
526
+
527
+ // 'driver' => 'database',
528
+
529
+ // 'table' => 'users',
530
+
531
+ // ],
532
+
533
+ ],
534
+
535
+
536
+
537
+ /*
538
+
539
+ |--------------------------------------------------------------------------
540
+
541
+ | Resetting Passwords
542
+
543
+ |--------------------------------------------------------------------------
544
+
545
+ |
546
+
547
+ | You may specify multiple password reset configurations if you have more
548
+
549
+ | than one user table or model in the application and you want to have
550
+
551
+ | separate password reset settings based on the specific user types.
552
+
553
+ |
554
+
555
+ | The expire time is the number of minutes that the reset token should be
556
+
557
+ | considered valid. This security feature keeps tokens short-lived so
558
+
559
+ | they have less time to be guessed. You may change this as needed.
560
+
561
+ |
562
+
563
+ */
564
+
565
+
566
+
567
+ 'passwords' => [
568
+
569
+ 'users' => [
458
570
 
459
571
  'provider' => 'users',
460
572
 
573
+ 'table' => 'password_resets',
574
+
461
- 'hash' => false,
575
+ 'expire' => 60,
576
+
577
+ 'throttle' => 60,
462
578
 
463
579
  ],
464
580
 
581
+
582
+
583
+ 'admins' => [
584
+
585
+ 'provider' => 'admins',
586
+
587
+ 'table' => 'password_resets',
588
+
589
+ 'expire' => 60,
590
+
591
+ 'throttle' => 60,
592
+
593
+ ],
594
+
465
595
  ],
466
596
 
467
597
 
@@ -470,29 +600,17 @@
470
600
 
471
601
  |--------------------------------------------------------------------------
472
602
 
473
- | User Providers
603
+ | Password Confirmation Timeout
474
-
604
+
475
- |--------------------------------------------------------------------------
605
+ |--------------------------------------------------------------------------
476
-
606
+
477
- |
607
+ |
478
-
479
- | All authentication drivers have a user provider. This defines how the
608
+
480
-
481
- | users are actually retrieved out of your database or other storage
482
-
483
- | mechanisms used by this application to persist your user's data.
484
-
485
- |
486
-
487
- | If you have multiple user tables or models you may configure multiple
609
+ | Here you may define the amount of seconds before a password confirmation
488
-
610
+
489
- | sources which represent each model / table. These sources may then
611
+ | times out and the user is prompted to re-enter their password via the
490
-
612
+
491
- | be assigned to any extra authentication guards you have defined.
613
+ | confirmation screen. By default, the timeout lasts for three hours.
492
-
493
- |
494
-
495
- | Supported: "database", "eloquent"
496
614
 
497
615
  |
498
616
 
@@ -500,124 +618,6 @@
500
618
 
501
619
 
502
620
 
503
- 'providers' => [
504
-
505
- 'users' => [
506
-
507
- 'driver' => 'eloquent',
508
-
509
- 'model' => App\Models\User::class,
510
-
511
- ],
512
-
513
-
514
-
515
- 'admins' => [
516
-
517
- 'driver' => 'eloquent',
518
-
519
- 'model' => App\Models\Admin::class,
520
-
521
- ],
522
-
523
-
524
-
525
- // 'users' => [
526
-
527
- // 'driver' => 'database',
528
-
529
- // 'table' => 'users',
530
-
531
- // ],
532
-
533
- ],
534
-
535
-
536
-
537
- /*
538
-
539
- |--------------------------------------------------------------------------
540
-
541
- | Resetting Passwords
542
-
543
- |--------------------------------------------------------------------------
544
-
545
- |
546
-
547
- | You may specify multiple password reset configurations if you have more
548
-
549
- | than one user table or model in the application and you want to have
550
-
551
- | separate password reset settings based on the specific user types.
552
-
553
- |
554
-
555
- | The expire time is the number of minutes that the reset token should be
556
-
557
- | considered valid. This security feature keeps tokens short-lived so
558
-
559
- | they have less time to be guessed. You may change this as needed.
560
-
561
- |
562
-
563
- */
564
-
565
-
566
-
567
- 'passwords' => [
568
-
569
- 'users' => [
570
-
571
- 'provider' => 'users',
572
-
573
- 'table' => 'password_resets',
574
-
575
- 'expire' => 60,
576
-
577
- 'throttle' => 60,
578
-
579
- ],
580
-
581
-
582
-
583
- 'admins' => [
584
-
585
- 'provider' => 'admins',
586
-
587
- 'table' => 'password_resets',
588
-
589
- 'expire' => 60,
590
-
591
- 'throttle' => 60,
592
-
593
- ],
594
-
595
- ],
596
-
597
-
598
-
599
- /*
600
-
601
- |--------------------------------------------------------------------------
602
-
603
- | Password Confirmation Timeout
604
-
605
- |--------------------------------------------------------------------------
606
-
607
- |
608
-
609
- | Here you may define the amount of seconds before a password confirmation
610
-
611
- | times out and the user is prompted to re-enter their password via the
612
-
613
- | confirmation screen. By default, the timeout lasts for three hours.
614
-
615
- |
616
-
617
- */
618
-
619
-
620
-
621
621
  'password_timeout' => 10800,
622
622
 
623
623
 

2

初心者マーク

2020/03/12 22:39

投稿

tenlife
tenlife

スコア70

test CHANGED
File without changes
test CHANGED
@@ -636,6 +636,8 @@
636
636
 
637
637
  ・キャッシュ削除。https://qiita.com/ucan-lab/items/c1e561d20cc591966c25
638
638
 
639
+ ・ユーザーの作り直し
640
+
639
641
 
640
642
 
641
643
  自分の力では原因を掴めずにいます。

1

初心者マーク

2020/03/12 22:35

投稿

tenlife
tenlife

スコア70

test CHANGED
File without changes
test CHANGED
@@ -10,7 +10,9 @@
10
10
 
11
11
  userの方はログインも新規登録もうまくいくのですが、
12
12
 
13
+ adminは新規登録するとログイン画面に飛ばされます(データベースには登録されている)。
14
+
13
- adminは新規登録するとログイン画面に飛ばされます(データベースには登録されている)。ログインしようとするとThese credentials do not match our recordsが出てきます。
15
+ ログインしようとするとThese credentials do not match our recordsが出てきます。
14
16
 
15
17
 
16
18