Custom LoginController for Nova

You can copy the file: "nova/resources/views/auth/login.blade.php" to your own apps resources folder. Put it in the exact same folder structure as in the /nova folder. Then edit that file in your resources folder and change the login route on the login form's method action to the route you want to use.

If you want I can walk you through it on https://devallies.com.

The moment you run php artisan make:auth in your nova powered fresh app, nova will default to the auth solution provided via controllers in app/Http/Controllers/Auth, this means you pretty much can implement the same business logic. The only thing that requires some thought is the login screen as it's going to default to the generated one, but it's pretty easy to overwrite based on the nova login screen... only a coupe of routes need to be changed to reflect the routes generated by Laravel.

Thanks for the responses, much appreciated. The issue is not the login page so much but modifying the authentication middleware/guard. This it self would not be such a struggle if I wasn't using Laravel Nova as it's LoginController is buried away.

I am still working through documentation on guards, middleware etc, trying to determine the best way to make this happen.

The requirements have extended a little so now I need to authenticate 2 different types of user via an external API and then site admin via the local DB. Again this not to hard for me to manager with Laravel but after adding Nova things are not the same as they ever was.

Hi I know this post is a few weeks old, but I came here with a similar question and this is how I solved my problems.

Look at the routes where you would like to overload the controllers from using artisan.

$php artisan route:list

Add a new route for this route with the same name to your own routes/web.php pointing to your own custom implementation of that controller in your project.

In my case. Route::post('nova/login', 'Nova\LoginController@login')->name('nova.login');

add a loginController at: app/Http/Controllers/Nova/LoginController.php

Hope this helps.

I had actually thought about doing that but for some reason didn't try it. Thanks for the input Martin, mutch appreciated

@mrwilde @martinfolkerts

I know this is old, but I just found a solution that works better for me.

In the Nova Service Provider, you can alias Nova's Login Controller for your own, meaning when the routing layer creates the Login Controller, it's using yours instead of Nova's.

Example:

    /**
     * Bootstrap any application services.
     *
     * @return void
     */
    public function boot()
    {
        parent::boot();

        $this->app->alias(
            \App\Http\Controllers\Nova\LoginController::class,
            \Laravel\Nova\Http\Controllers\LoginController::class
        );
    }

@tylernathanreed

overriding the entry in the service container makes a lot of sense. Thanks for the reply.

I went with the following:

modified: app/Providers/NovaServiceProvider.php
──────────────────────────────
@ NovaServiceProvider.php:32 @ class NovaServiceProvider extends NovaApplicationServiceProvider
    protected function routes()
    {
        Nova::routes()
                // remove Nova's auth routes, so as to use the default
                // updated the nova nav item to link to the default logout as well
                // ->withAuthenticationRoutes()
                // ->withPasswordResetRoutes()
                ->register();
    }

──────────────────────────────
modified: resources/views/vendor/nova/partials/user.blade.php
──────────────────────────────
@ user.blade.php:10 @
<dropdown-menu slot="menu" width="200" direction="rtl">
    <ul class="list-reset">
        <li>
            <a
                href="{{ url('/logout') }}"
                class="block no-underline text-90 hover:bg-30 p-3"
                onclick="event.preventDefault(); document.getElementById('logout-form').submit();"
            >
                {{ __('Logout') }}
            </a>
 
            <form id="logout-form" class="hidden" action="{{ url('/logout') }}" method="POST">
                {{ csrf_field() }}
            </form>
        </li>
    </ul>
</dropdown-menu>

Liking how @mdeclaire disabled the original routes in the NovaServiceProvider->routes. But I prefer not to edit vendor files. Went with a redirect of the /nova/logout route in my web.php routes file instead:

Route::get('nova/logout', function () {
    return redirect('/logout');
})->name('nova.logout');