Nova::userModel() method has hard-coded configuration path

[stevebauman]

• Laravel Version: 8.*
• Nova Version: 4.*
• PHP Version: N/a
• Database Driver & Version: N/A
• Operating System and Version: N/A
• Browser type and version: N/A
• Reproduction Repository: N/A

Description:

I'm the creator of an authentication package that uses a different configuration path than the standard Laravel Eloquent auth config path. Since Laravel Nova has a hard-coded config path to the application user model, Nova retrieves an invalid value and attempts to call methods upon it.

I've had a couple users report this exception:

Call to undefined method LdapRecord\Query\Model\ActiveDirectoryBuilder::getKeyType()

DirectoryTree/LdapRecord-Laravel#423
DirectoryTree/LdapRecord-Laravel#422

Example Configuration From Package

'providers' => [
        // 'users' => [
        //    'driver' => 'eloquent',
        //    'model' => App\Models\User::class,
        // ],

        'users' => [
            'driver' => 'ldap',
            'model' => LdapRecord\Models\ActiveDirectory\User::class,
            'database' => [
                'model' => App\Models\User::class,
                // ...
            ],
        ],
    ],
]

Resolution

It would be useful if users could instead use a callback to retrieve the application's user model.

This callback could also receive the provider and guard for easier retrieval:

public static function resolveUserModelUsing($callback)
{
    static::$userModelResolver = $callback;
}

public function userModel()
{
    $guard = config('nova.guard') ?: config('auth.defaults.guard');

    $provider = config("auth.guards.{$guard}.provider");

    return value(static::$userModelResolver ?? function ($provider) {      
      return config("auth.providers.{$provider}.model");
    }, $provider, $guard);
}

// Override

Nova::resolveUserModelUsing(function ($provider, $guard) { // <-- $guard is optionally included.
    // Using the provider to fetch an alternate config path...
    return config("auth.providers.{$provider}.database.model");

    // Or simply returning the class...
    return App\Models\User::class;
})

Detailed steps to reproduce the issue on a fresh Nova installation:

Use any auth provider without an auth.providers.{$provider}.model configuration path.