Adding Github Registry and Authentication To Laravel 5.2 Image Adding Github Registry and Authentication To Laravel 5.2

Table Of Contents

As part of the ongoing work I’ve been doing on this site, I thought it would be a good idea to totally remove the traditional method of registering and logging in and instead replace that with github authentication. This actively reduces the risks that the site takes with regards to storing passwords and allows me to rely upon a relatively secure authentication method rather than having to roll my own.

Creating a Github Application

In order for us to use Github’s authentication in our application we are going to need to first register this with Github. Navigate to here and fill in the details for your new application.

The callback url should be

Once you’ve done that you should be redirected to a page that shows you the client ID and the secret. Copy these and add them to your .env file in your laravel 5 application:


Next thing we need to do is add this to our config/services.php

'github' => [
      'client_id' => env('GITHUB_ID'),
      'client_secret' => env('GITHUB_SECRET'),
      'redirect' => env('GITHUB_CALLBACK_URL'),

After you’ve done this we should be good to go and can proceed with installing Socialite and configuring our app.

Adding Socialite To Your Laravel 5 Project

In order for us to use Github’s authentication we are going to need to first add Socialite to our Laravel 5 project. We can do this by performing the following composer command:

composer require laravel/socialite

Once this has successfully ran we then need to make some modifications to our config/app.php file.

'providers' => [
  // add our new provider to the providers array
'aliases' => [
  'Socialite' => 'Laravel\Socialite\Facades\Socialite',

Configuring our Routes

In order for visitors to authenticate with github we are going to need a new route that they can navigate to that will trigger out authentication prompt. Navigate to your routes.php file and add the following routes:

Route::get('auth/github', 'Auth\AuthController@redirectToProvider');
Route::get('auth/github/callback', 'Auth\AuthController@handleProviderCallback');

Now that we’ve added these two routes, we now need to add the functions that they call whenever they are hit.

Our AuthController File

Open up your AuthController.php file and add the following 3 functions:

  * Redirect the user to the GitHub authentication page.
  * @return Response
public function redirectToProvider(Request $request)
    return Socialite::driver('github')
        ->with(['redirect_uri' => env('GITHUB_CALLBACK_URL' ) . '?redirect=' . $request->input('redirect')])

  * Obtain the user information from GitHub.
  * @return Response
public function handleProviderCallback(Request $request)
    $user = Socialite::driver('github')->user();
    Session::put('user', $user);

    $redirect = $request->input('redirect');

        return redirect($redirect);

    $authUser = $this->findOrCreateUser($user);

    Auth::login($authUser, true);

    return redirect('home');

  * Return user if exists; create and return if doesn't
  * @param $githubUser
  * @return User
private function findOrCreateUser($githubUser)
    if ($authUser = User::where('github_id', $githubUser->id)->first()) {
        Log::info("User Found");
        return $authUser;

    return User::create([
        'name' => $githubUser->name,
        'email' => $githubUser->email,
        'github_id' => $githubUser->id,
        'avatar' => $githubUser->avatar

Editing the Database Structure

So if we are going to be authenticating people using Github’s OAuth2 then we need to be able to store who we have and haven’t already authenticated. To do this we’ll need to modify the database so that it stores the github_id and any subsequent things like the avatar etc.

In this example I just extended my users table by adding an extra row, I prefer doing it using pure sql rather than migrations:

Pure SQL

ALTER TABLE users ADD github_id INT;

Updating our Users Model

Finally we need to update our User model. Open up app/User.php and change the following

* The attributes that are mass assignable.
* @var array
protected $fillable = ['github_id','name', 'email', 'password'];

Testing it All Works

Now that you’ve configured everything it’s time to check it all works. Navigate to and you should hopefully be redirected to githubs authentication page on which you can allow your app to use your details. This should then return you to your ‘home’ route or whatever other route you wish to route them back to.

If everything works then congratulations, you’ve now succesfully added github authentication to your Laravel application!

Elliot Forbes

Elliot Forbes
Twitter: @Elliot_f

Hey, I'm Elliot and I've been working on TutorialEdge for the last 4 years! If you have any tips or suggestions as to how I can make it better, please let me know in the suggestion box below!

Comments Section