Laravel 11 Upgrade Problems

[JoeyofBladez]

Laravel: v11.5.0
ldaprecord-laravel: v3.3.2

I have been using ldaprecord-laravel smoothly on a web application but after upgrading to Laravel 11 (released last month), I am seeing the following exception whenever a composer or artisan command is run:

   InvalidArgumentException

  Authentication user provider [ldap] is not defined.

  at vendor/laravel/framework/src/Illuminate/Auth/CreatesUserProviders.php:43
     39▕
     40▕         return match ($driver) {
     41▕             'database' => $this->createDatabaseProvider($config),
     42▕             'eloquent' => $this->createEloquentProvider($config),
  ➜  43▕             default => throw new InvalidArgumentException(
     44▕                 "Authentication user provider [{$driver}] is not defined."
     45▕             ),
     46▕         };
     47▕     }

I've cross-checked available documentation at https://ldaprecord.com/docs/laravel/v3/auth/database/configuration and this is my auth.php file:

// config/auth.php
	'providers' => [
        'users' => [
            'driver' => 'ldap',
            'model' => App\Ldap\User::class,
            'rules' => [],
            'database' => [
                'model' => App\Models\User::class,
                'sync_passwords' => false,
                'sync_attributes' => [
                    'name' => 'cn',
                    'email' => 'uid',
                    'custom_user_id' => 'customUserId'
                ],
                'sync_existing' => [
                    'email' => 'uid',
                    'custom_user_id' => 'customUserId'
                ],
                'password_column' => false,
            ],
        ]
	],

Is there no compatibility with Laravel 11 available yet, or are there config changes that need to be made? If I revert composer.json to use my current Laravel 10 and associated packages, the application works perfectly fine and has for almost a year now. Thanks in advance for anyone who can provide insight.

[stevebauman]

Hi @JoeyofBladez,

Can you post your entire config/auth.php file?

[JoeyofBladez]

<?php

return [

    /*
    |--------------------------------------------------------------------------
    | Authentication Defaults
    |--------------------------------------------------------------------------
    |
    | This option controls the default authentication "guard" and password
    | reset options for your application. You may change these defaults
    | as required, but they're a perfect start for most applications.
    |
    */

    'defaults' => [
        'guard' => 'web',
        'passwords' => 'users',
    ],

    /*
    |--------------------------------------------------------------------------
    | Authentication Guards
    |--------------------------------------------------------------------------
    |
    | Next, you may define every authentication guard for your application.
    | Of course, a great default configuration has been defined for you
    | here which uses session storage and the Eloquent user provider.
    |
    | All authentication drivers have a user provider. This defines how the
    | users are actually retrieved out of your database or other storage
    | mechanisms used by this application to persist your user's data.
    |
    | Supported: "session"
    |
    */

    'guards' => [
        'web' => [
            'driver' => 'session',
            'provider' => 'users',
        ],
    ],

    /*
    |--------------------------------------------------------------------------
    | User Providers
    |--------------------------------------------------------------------------
    |
    | All authentication drivers have a user provider. This defines how the
    | users are actually retrieved out of your database or other storage
    | mechanisms used by this application to persist your user's data.
    |
    | If you have multiple user tables or models you may configure multiple
    | sources which represent each model / table. These sources may then
    | be assigned to any extra authentication guards you have defined.
    |
    | Supported: "database", "eloquent"
    |
    */

	'providers' => [
        'users' => [
            'driver' => 'ldap',
            'model' => App\Ldap\User::class,
            'rules' => [],
            'database' => [
                'model' => App\Models\User::class,
                'sync_passwords' => false,
                'sync_attributes' => [
                    'name' => 'cn',
                    'email' => 'uid',
                    'custom_user_id' => 'customUserId'
                ],
                'sync_existing' => [
                    'email' => 'uid',
                    'custom_user_id' => 'customUserId'
                ],
                'password_column' => false,
            ],
        ]
	],

    /*
    |--------------------------------------------------------------------------
    | Resetting Passwords
    |--------------------------------------------------------------------------
    |
    | You may specify multiple password reset configurations if you have more
    | than one user table or model in the application and you want to have
    | separate password reset settings based on the specific user types.
    |
    | The expire time is the number of minutes that each reset token will be
    | considered valid. This security feature keeps tokens short-lived so
    | they have less time to be guessed. You may change this as needed.
    |
    */

    'passwords' => [
        'users' => [
            'provider' => 'users',
            'table' => 'password_resets',
            'expire' => 60,
            'throttle' => 60,
        ],
        'minPasswordLength' => env('MIN_PASSWORD_LENGTH', 12)
    ],

    /*
    |--------------------------------------------------------------------------
    | Password Confirmation Timeout
    |--------------------------------------------------------------------------
    |
    | Here you may define the amount of seconds before a password confirmation
    | times out and the user is prompted to re-enter their password via the
    | confirmation screen. By default, the timeout lasts for three hours.
    |
    */

    'password_timeout' => 10800,

];

[stevebauman]

Thanks @JoeyofBladez. I'm not able to replicate this in a fresh Laravel application after installing and configuring LdapRecord-Laravel.

Can you share the entire stack trace of the exception?

Also, does this occur when you run any artisan command, or just LDAP specific commands?

[JoeyofBladez]

@stevebauman See below stack trace. It is not very informative on the surface but I appreciate your help looking into this and your responsiveness, so I can provide any more details that would be helpful to you. Below are the results of the php artisan command, and this is consistent with other php artisan commands such as php artisan serve and php artisan cache:clear.

joeyofbladez@web-ubuntu:~/joey-app-core$ php artisan serve
#0 /home/joeyofbladez/joey-app-core/vendor/laravel/framework/src/Illuminate/Auth/AuthManager.php(128): Illuminate\Auth\AuthManager->createUserProvider('...')
#1 /home/joeyofbladez/joey-app-core/vendor/laravel/framework/src/Illuminate/Auth/AuthManager.php(97): Illuminate\Auth\AuthManager->createSessionDriver('...', Array)
#2 /home/joeyofbladez/joey-app-core/vendor/laravel/framework/src/Illuminate/Auth/AuthManager.php(71): Illuminate\Auth\AuthManager->resolve('...')
#3 /home/joeyofbladez/joey-app-core/vendor/laravel/framework/src/Illuminate/Auth/AuthManager.php(352): Illuminate\Auth\AuthManager->guard()
#4 /home/joeyofbladez/joey-app-core/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php(357): Illuminate\Auth\AuthManager->__call('...', Array)
#5 /home/joeyofbladez/joey-app-core/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php(531): Illuminate\Support\Facades\Facade::__callStatic('...', Array)
#6 /home/joeyofbladez/joey-app-core/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php(496): Illuminate\Foundation\Exceptions\Handler->context()
#7 /home/joeyofbladez/joey-app-core/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php(373): Illuminate\Foundation\Exceptions\Handler->buildExceptionContext(Object(Error))
#8 /home/joeyofbladez/joey-app-core/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php(337): Illuminate\Foundation\Exceptions\Handler->reportThrowable(Object(Error))
#9 /home/joeyofbladez/joey-app-core/vendor/nunomaduro/collision/src/Adapters/Laravel/ExceptionHandler.php(46): Illuminate\Foundation\Exceptions\Handler->report(Object(Error))
#10 /home/joeyofbladez/joey-app-core/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(621): NunoMaduro\Collision\Adapters\Laravel\ExceptionHandler->report(Object(Error))
#11 /home/joeyofbladez/joey-app-core/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(200): Illuminate\Foundation\Console\Kernel->reportException(Object(Error))
#12 /home/joeyofbladez/joey-app-core/artisan(35): Illuminate\Foundation\Console\Kernel->handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))

Additionally, I get this exception when I run composer install as well when running the postAutoloadDump script. I'm wondering if something is not being included properly? It seems like any artisan or composer command will trigger this. I just don't understand why it doesn't happen with ldaprecord-laravel ^2.5 on laravel/framework ^10.0 on the pre-upgrade project state.

> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi

   InvalidArgumentException

  Authentication user provider [ldap] is not defined.

  at vendor/laravel/framework/src/Illuminate/Auth/CreatesUserProviders.php:45
     41▕
     42▕         return match ($driver) {
     43▕             'database' => $this->createDatabaseProvider($config),
     44▕             'eloquent' => $this->createEloquentProvider($config),
  ➜  45▕             default => throw new InvalidArgumentException(
     46▕                 "Authentication user provider [{$driver}] is not defined."
     47▕             ),
     48▕         };
     49▕     }

      +5 vendor frames

  6   app/Logging/MysqlHandler.php:37
      Illuminate\Support\Facades\Facade::__callStatic()
      +11 vendor frames

  18  artisan:35
      Illuminate\Foundation\Console\Kernel::handle()

Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1

[JoeyofBladez]

Thanks for your willingness to help on this. My error logger was then trying to call Auth::id() to get the current user's ID but throwing an exception on that since Sanctum and LdapRecord were not setting themselves up properly... I had error handling for this returning 0 if the user is not authenticated, but the authentication services themselves were not instantiating properly so looks like I need another try/catch there... With that I then moved on to two easily solved issues:

1. Sanctum 4.0 no longer loads migrations automatically, so the ignoreMigrations function was removed. We were calling this so I just removed the function call in that service provider's code.
2. LdapRecord renamed a function getEventDispatcher to getDispatcher, so I updated that service provider's code.

Both are standard upgrade procedures and while the Sanctum issue wasn't explicitly stated, looking at the source code and seeing it removed along with the migration info made sense with how Laravel's v11 upgrade guide states that it won't do automatic migrations anymore, making the function obsolete. The LdapRecord guide has a nice clean table of renamed functions, so thanks for that!

[stevebauman]

Nice @JoeyofBladez, glad you were able to discover and rectify those issues.

Thanks for the detailed reply that may help others in the future, appreciate it! 🙏