Install Laravel Socialite via Composer. 2. Create OAuth credentials in Google Cloud Console and set redirect URI. 3. Add GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, and GOOGLE_REDIRECT_URI to .env and configure in config/services.php. 4. Define routes for Google login and callback. 5. Create GoogleAuthController with redirectToGoogle and handleGoogleCallback methods to authenticate and log in user. 6. Add google_id, google_token, and google_refresh_token fields to users table via migration and include in User model's $fillable array. 7. Add a login button in Blade template linking to the Google login route, and optionally specify scopes for additional data access, ensuring email validation for security, completing the full Google login integration in Laravel using Socialite.
Using Laravel Socialite to implement Google login is straightforward. Here's a step-by-step guide to help you set it up properly in your Laravel application.

1. Install Laravel Socialite
First, install Laravel Socialite via Composer:
composer require laravel/socialite
Note: Laravel Socialite is a first-party package, so it’s well-maintained and integrates smoothly.
2. Configure Google OAuth Credentials
Go to the Google Cloud Console:
- Create a new project or select an existing one.
- Navigate to APIs & Services > Credentials.
- Click Create Credentials > OAuth client ID.
- Choose Web application.
- Add authorized redirect URIs. For local development, use:
http://your-app.test/login/google/callback
or if using Laravel Sail or Valet:
http://localhost:8000/login/google/callback
- Save and copy the Client ID and Client Secret.
3. Add Google Credentials to .env
In your .env
file, add the following:
GOOGLE_CLIENT_ID=your-google-client-id GOOGLE_CLIENT_SECRET=your-google-client-secret GOOGLE_REDIRECT_URI=http://localhost:8000/login/google/callback
Then, register these in config/services.php
:
// config/services.php 'google' => [ 'client_id' => env('GOOGLE_CLIENT_ID'), 'client_secret' => env('GOOGLE_CLIENT_SECRET'), 'redirect' => env('GOOGLE_REDIRECT_URI'), ],
4. Set Up Routes
Add routes for redirecting to Google and handling the callback:
// routes/web.php use Illuminate\Support\Facades\Route; use App\Http\Controllers\Auth\GoogleAuthController; Route::get('/login/google', [GoogleAuthController::class, 'redirectToGoogle']) ->name('login.google'); Route::get('/login/google/callback', [GoogleAuthController::class, 'handleGoogleCallback']);
5. Create the Controller
Generate the controller:
php artisan make:controller Auth/GoogleAuthController
Implement the methods:
// App/Http/Controllers/Auth/GoogleAuthController.php <?php namespace App\Http\Controllers\Auth; use App\Http\Controllers\Controller; use Illuminate\Http\Request; use Laravel\Socialite\Facades\Socialite; use App\Models\User; use Illuminate\Support\Facades\Auth; class GoogleAuthController extends Controller { public function redirectToGoogle() { return Socialite::driver('google')->redirect(); } public function handleGoogleCallback() { try { $googleUser = Socialite::driver('google')->user(); } catch (\Exception $e) { return redirect('/login')->withErrors('Google login failed.'); } // Find or create user $user = User::updateOrCreate([ 'google_id' => $googleUser->id, ], [ 'name' => $googleUser->name, 'email' => $googleUser->email, 'google_token' => $googleUser->token, 'google_refresh_token' => $googleUser->refreshToken, ]); Auth::login($user); return redirect('/dashboard'); } }
? Tip: Store
google_id
in your users table to uniquely identify Google users. You may also want to addgoogle_token
if you plan to use Google APIs later.
6. Update Your User Model and Migration
Make sure your users
table has the necessary fields:
php artisan make:migration add_google_fields_to_users_table --table=users
// migration file public function up() { Schema::table('users', function ($table) { $table->string('google_id')->nullable()->unique(); $table->string('google_token')->nullable(); $table->string('google_refresh_token')->nullable(); }); }
Run the migration:
php artisan migrate
Also, add the fields to your User model's $fillable
array:
// app/Models/User.php protected $fillable = [ 'name', 'email', 'google_id', 'google_token', 'google_refresh_token', ];
7. Add Google Login Button in Your View
Example in a Blade file:
<!-- resources/views/auth/login.blade.php --> <a href="{{ route('login.google') }}" class="btn btn-danger"> Login with Google </a>
Optional: Scopes and Additional Data
If you need more permissions (e.g., user's profile, email), you can add scopes:
return Socialite::driver('google') ->scopes(['openid', 'profile', 'email']) ->redirect();
By default, Socialite requests basic profile and email, so this is often not needed.
That’s it! You now have Google login working in your Laravel app using Socialite.
?? Security Note: Always validate the email and consider email verification if you're allowing account creation based on Google login.
Basically just follow the flow: redirect → callback → get user → log in or register → redirect to dashboard.
The above is the detailed content of How to use Laravel Socialite for Google login?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

There are three ways to add custom validation rules in Laravel: using closures, Rule classes, and form requests. 1. Use closures to be suitable for lightweight verification, such as preventing the user name "admin"; 2. Create Rule classes (such as ValidUsernameRule) to make complex logic clearer and maintainable; 3. Integrate multiple rules in form requests and centrally manage verification logic. At the same time, you can set prompts through custom messages methods or incoming error message arrays to improve flexibility and maintainability.

ToworkeffectivelywithpivottablesinLaravel,firstaccesspivotdatausingwithPivot()orwithTimestamps(),thenupdateentrieswithupdateExistingPivot(),managerelationshipsviadetach()andsync(),andusecustompivotmodelswhenneeded.1.UsewithPivot()toincludespecificcol

Laravelprovidesacleanandflexiblewaytosendnotificationsviamultiplechannelslikeemail,SMS,in-appalerts,andpushnotifications.Youdefinenotificationchannelsinthevia()methodofanotificationclass,andimplementspecificmethodsliketoMail(),toDatabase(),ortoVonage

Dependency injection automatically handles class dependencies through service containers in Laravel without manual new objects. Its core is constructor injection and method injection, such as automatically passing in the Request instance in the controller. Laravel parses dependencies through type prompts and recursively creates the required objects. The binding interface and implementation can be used by the service provider to use the bind method, or singleton to bind a singleton. When using it, you need to ensure type prompts, avoid constructor complications, use context bindings with caution, and understand automatic parsing rules. Mastering these can improve code flexibility and maintenance.

Laravel performance optimization can improve application efficiency through four core directions. 1. Use the cache mechanism to reduce duplicate queries, store infrequently changing data through Cache::remember() and other methods to reduce database access frequency; 2. Optimize database from the model to query statements, avoid N 1 queries, specifying field queries, adding indexes, paging processing and reading and writing separation, and reduce bottlenecks; 3. Use time-consuming operations such as email sending and file exporting to queue asynchronous processing, use Supervisor to manage workers and set up retry mechanisms; 4. Use middleware and service providers reasonably to avoid complex logic and unnecessary initialization code, and delay loading of services to improve startup efficiency.

Methods to manage database state in Laravel tests include using RefreshDatabase, selective seeding of data, careful use of transactions, and manual cleaning if necessary. 1. Use RefreshDatabasetrait to automatically migrate the database structure to ensure that each test is based on a clean database; 2. Use specific seeds to fill the necessary data and generate dynamic data in combination with the model factory; 3. Use DatabaseTransactionstrait to roll back the test changes, but pay attention to its limitations; 4. Manually truncate the table or reseed the database when it cannot be automatically cleaned. These methods are flexibly selected according to the type of test and environment to ensure the reliability and efficiency of the test.

LaravelSanctum is suitable for simple, lightweight API certifications such as SPA or mobile applications, while Passport is suitable for scenarios where full OAuth2 functionality is required. 1. Sanctum provides token-based authentication, suitable for first-party clients; 2. Passport supports complex processes such as authorization codes and client credentials, suitable for third-party developers to access; 3. Sanctum installation and configuration are simpler and maintenance costs are low; 4. Passport functions are comprehensive but configuration is complex, suitable for platforms that require fine permission control. When selecting, you should determine whether the OAuth2 feature is required based on the project requirements.

Laravel simplifies database transaction processing with built-in support. 1. Use the DB::transaction() method to automatically commit or rollback operations to ensure data integrity; 2. Support nested transactions and implement them through savepoints, but it is usually recommended to use a single transaction wrapper to avoid complexity; 3. Provide manual control methods such as beginTransaction(), commit() and rollBack(), suitable for scenarios that require more flexible processing; 4. Best practices include keeping transactions short, only using them when necessary, testing failures, and recording rollback information. Rationally choosing transaction management methods can help improve application reliability and performance.
