From 670b3ba868f7935c755603bb6e72e07d30e0f18f Mon Sep 17 00:00:00 2001 From: Daniel Supernault Date: Tue, 2 May 2023 20:53:10 -0600 Subject: [PATCH] Update passport config --- config/passport.php | 41 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+) diff --git a/config/passport.php b/config/passport.php index a4565f372..bd7e2ee9b 100644 --- a/config/passport.php +++ b/config/passport.php @@ -1,6 +1,18 @@ 'web', /* |-------------------------------------------------------------------------- @@ -17,4 +29,33 @@ return [ 'public_key' => env('PASSPORT_PUBLIC_KEY'), + /* + |-------------------------------------------------------------------------- + | Client UUIDs + |-------------------------------------------------------------------------- + | + | By default, Passport uses auto-incrementing primary keys when assigning + | IDs to clients. However, if Passport is installed using the provided + | --uuids switch, this will be set to "true" and UUIDs will be used. + | + */ + + 'client_uuids' => false, + + /* + |-------------------------------------------------------------------------- + | Personal Access Client + |-------------------------------------------------------------------------- + | + | If you enable client hashing, you should set the personal access client + | ID and unhashed secret within your environment file. The values will + | get used while issuing fresh personal access tokens to your users. + | + */ + + 'personal_access_client' => [ + 'id' => env('PASSPORT_PERSONAL_ACCESS_CLIENT_ID'), + 'secret' => env('PASSPORT_PERSONAL_ACCESS_CLIENT_SECRET'), + ], + ];