OAuth2 GitHub Login on Laravel: Setup Socialite

OAuth2 GitHub Login on Laravel: Implementation in 1 Day

Imagine: you launch a SaaS for developers, and every user manually fills out a registration form. Conversion drops by 30% — nobody wants to enter a password if they can log in with one click. On one project for a CIS developer community, we implemented GitHub OAuth — registration conversion jumped from 12% to 45% in a week. Logging in via GitHub is 12 times faster than the form: 5 seconds versus 60. Our experience (10+ years, 50+ projects) shows that GitHub OAuth is the most reliable OAuth2 flow: it doesn't require email verification (GitHub already does that), provides a stable identifier and avatar. We guarantee speed — from app registration to production in 1-2 days.

GitHub OAuth is safer than classic registration: you don't store passwords, and GitHub handles authentication. Additionally, it increases trust — 95% of users prefer social login.

OAuth2 GitHub Flow

The process consists of four steps:

1. The user clicks the "Login with GitHub" button.
2. GitHub displays a permissions page.
3. After consent, GitHub returns a temporary code to your callback URL.
4. The server exchanges the code for an access token and requests the profile.

This takes a couple of seconds. The token lives until revoked, but for login we don't store it — we use it only to obtain data during registration.

Registering an OAuth App

1. github.com → Settings → Developer settings → OAuth Apps → New OAuth App.
2. Fill in Application name, Homepage URL, and Authorization callback URL.
3. Save Client ID and generate Client Secret.

Authorization callback URL must point to your endpoint, e.g., https://example.com/auth/github/callback. More details — GitHub OAuth documentation.

Note: GitHub App (not OAuth App) is used to access repositories — for user authorization, an OAuth App is enough.

Laravel Socialite

// config/services.php 'github' => [ 'client_id' => env('GITHUB_CLIENT_ID'), 'client_secret' => env('GITHUB_CLIENT_SECRET'), 'redirect' => env('GITHUB_REDIRECT_URI'), ], 

class GitHubAuthController extends Controller { public function redirect(): RedirectResponse { return Socialite::driver('github') ->scopes(['user:email']) ->redirect(); } public function callback(): RedirectResponse { try { $githubUser = Socialite::driver('github')->user(); } catch (\Exception $e) { return redirect('/login')->withErrors(['github' => 'Ошибка авторизации']); } $user = User::updateOrCreate( ['github_id' => $githubUser->getId()], [ 'name' => $githubUser->getName() ?? $githubUser->getNickname(), 'email' => $githubUser->getEmail(), 'email_verified_at' => now(), 'avatar' => $githubUser->getAvatar(), 'github_username' => $githubUser->getNickname(), ] ); Auth::login($user, remember: true); return redirect()->intended('/dashboard'); } } 

Socialite abstracts the OAuth routine: you don't need to manually form requests, handle redirects, and parse responses. This reduces code volume by 70% compared to a custom implementation. We've learned from experience: errors in manual OAuth are a common source of bugs in production.

Advantages of Socialite

Socialite supports dozens of providers out of the box. You simply switch the driver — and GitHub OAuth turns into GitLab or Google. A unified interface reduces the chance of errors. Plus automatic updates when the provider's API changes.

How to Handle a User's Private Email on GitHub?

If a user has hidden their email in GitHub settings, getEmail() will return null. A request with the user:email scope allows you to get the email via an additional API call:

$emails = Http::withToken($githubUser->token) ->get('https://api.github.com/user/emails') ->json(); $primaryEmail = collect($emails) ->firstWhere(fn($e) => $e['primary'] && $e['verified']); 

This method returns a verified email. If none is found — the user will not be able to log in until they set a public email on GitHub.

How to Restrict Login to Organization Members?

If you need to allow login only to members of a specific GitHub organization:

$membership = Http::withToken($githubUser->token) ->get("https://api.github.com/orgs/{$orgName}/members/{$githubUser->getNickname()}"); if ($membership->status() !== 204) { Auth::logout(); return redirect('/login')->withErrors(['github' => 'Вход разрешён только для членов организации']); } 

What to Do About GitHub API Errors?

The GitHub API may be unavailable or return an error. We embed logging and fallback mechanisms: if the request fails, the user sees a clear message, and we get a notification. Additionally, we configure retries with exponential backoff.

What's Included in the Integration

• Creation and configuration of an OAuth App
• Integration of Laravel Socialite with specified scopes
• Implementation of controllers and error handling
• Testing of all scenarios (private email, access denial, re-login)
• Deployment documentation and 2 weeks of support after handover

Work Process for the Integration

1. Analysis — determine requirements: need for organization screening, which profile data to save.
2. Design — create OAuth App, configure environment.
3. Implementation — connect Socialite, write controllers and error handling.
4. Testing — check scenarios: private email, access denial, re-login.
5. Deployment — roll out to production, update callback URL.

Timeline

The integration takes 1-2 working days. Over the years, we've implemented GitHub OAuth on dozens of projects and guarantee stable authentication. Contact us for a free consultation — we'll assess your project and offer the best solution.