Version 8 redirects

You can implement and bind your own LoginResponse class (which implements LoginResponse interface) into the container.

Will give it a try later, thanks.

It works:

Just quick test and example for those redirecting depending on role:

<?php

namespace App\Http\Responses;

use Illuminate\Support\Facades\Auth;
use Illuminate\Support\Facades\Session;
use Laravel\Fortify\Contracts\LoginResponse as LoginResponseContract;

class LoginResponse implements LoginResponseContract
{

    public function toResponse($request)
    {
        
        // below is the existing response
        // replace this with your own code
        // the user can be located with Auth facade
        $role = Auth::user()->role;
        $checkrole = explode(',', $role);  // However you get role
       
        if (in_array('admin', $checkrole)) {
            Session::put('isadmin', 'admin');
           return redirect('dog/indexadmin');
        } else {
            return redirect('pet/index');
        }

        
        return $request->wantsJson()
                    ? response()->json(['two_factor' => false])
                    : redirect()->intended(config('fortify.home'));
    }

}

Note

Most will need a leading slash (/) like:

return redirect('/dog/indexadmin');

I don't because I set htacces to skip leading slash.

The process is the same. Just create and bind a LogoutResponse instead

These are the bindings registered by Fortify;

    protected function registerResponseBindings()
    {
        $this->app->singleton(LoginResponseContract::class, LoginResponse::class);
        $this->app->singleton(LockoutResponseContract::class, LockoutResponse::class);
        $this->app->singleton(LogoutResponseContract::class, LogoutResponse::class);
        $this->app->singleton(RegisterResponseContract::class, RegisterResponse::class);
        $this->app->singleton(SuccessfulPasswordResetLinkRequestResponseContract::class, SuccessfulPasswordResetLinkRequestResponse::class);
        $this->app->singleton(FailedPasswordResetLinkRequestResponseContract::class, FailedPasswordResetLinkRequestResponse::class);
        $this->app->singleton(PasswordResetResponseContract::class, PasswordResetResponse::class);
        $this->app->singleton(FailedPasswordResetResponseContract::class, FailedPasswordResetResponse::class);
    }

@snapey did you see answer on other post where I asked could you do a pull request to include this?

Thanks...

@snapey

This is works, but only if disabled two-factor authentication. My app responds like this.

Is there something wrong? Is it the same for you when you use two-factor authentication?

    public function toResponse($request)
    {
        $redirect = config('fortify.home');

        // Only if two factor authentication is disabled
        $check = Auth::user()->hasAnyRole([
            "admin",
            "maintainer",
        ]);

        if ($check) {
            $redirect = route("admin.dashboard");
        }

        return redirect($redirect);

        // return $request->wantsJson()
        //     ? response()->json(['two_factor' => false])
        //     : redirect()->intended(config('fortify.home'));
    }

My app responds like this.

like what?

@assoft

If two-factor authentication is enabled, it always goes to the "fortify.home" @snapey

Yes, can confirm to @assoft

There is no Contracts\TwoFactorLoginResponse thingy to bind with custom Response. (There is one for TwoFactorChallengeViewResponse only.)

So, when user login successfully, then when 2fa is enabled, laravel will not use LoginViewResponse.

The \Laravel\Fortify\src\Http\Responses\TwoFactorLoginResponse.php is where fortify redirects to dashboard. Now, this cannot be used to bind like contracts.

I added a feature request on the Fortify project https://github.com/laravel/fortify/issues/31

@nuish @assoft

They have been quite proactive in plugging gaps so it might not take long to resolve.

Precisely @snapey - excellent post on your blog 👍

@assoft @nuish

I created a PR to add the TwoFactorLoginResponse also, and had it accepted this morning. I don't know when it will be released.

@snapey Yes… I follow you. Thank you for efforts. MERGED 👍

I know these fixes put my mind at ease with the new jetstream.

Updated Laravel Jetstream v1.2.0

I've tested and verified it works.

Thank you @snapey

Enjoy.

public function boot()
{
    $this->configurePermissions();

    Jetstream::deleteUsersUsing(DeleteUser::class);

    // register new LoginResponse
    $this->app->singleton(
        \Laravel\Fortify\Contracts\LoginResponse::class,
        \App\Http\Responses\LoginResponse::class
    );

    $this->app->singleton(
        \Laravel\Fortify\Contracts\TwoFactorLoginResponse::class,
        \App\Http\Responses\TwoFactorLoginResponse::class
    );
}

@braffzachlin exactly the same, you just bound it in a different provider

Can someone post a complete tutorial on this please.... I understand the concept, but i'm not sure where to do a check for authenticated user role. Also what migrations modification is needed to the database? Add another "user type" column to users table with let's say 0 for regular users and 1 for admins?

The laravel from scratch series has several videos on authentication and authorization and this is a free video series.

have you got 3 role authentication?

With a switch case, would it work for more roles?

example 4 roles.

super admin, admin, master and user

@javieralex an example:

• Bob is an admin

• Suzy is admin and does bookkeeping

• Mary is a bookkeeper only

• If Bob is logged in, Bob can only do admin stuff and all access to user stuff. But Bob cannot mess with bookkeeping.

• If Suzy is logged in she can access admin stuff and bookkeeping and accounting stuff.

• If Mary is logged in she cannot mess with admin stuff, but has access to bookkeeping and accounting stuff.

So I just check at method level if the logged in users role can or cannot access that method / function.

So in pseudocode:

public function makeInvoice()
    {
        if (a required role of bkeep is not true here) {   // bkeep = bookkeeper
            return redirect('somewhere'); // whereever you redirect to if not authorized
        }
        // Rest of method here is accomplished if 
        // the logged in user has the required role of 'bkeep'.
    }

It's good to use Authorization with query scopes to fine tune.

Another example:

public function update(Request $request, Post $post) {
    if ($post->author !== auth()->user()->id || auth()->user()->cannot('edit posts'))
        abort(404);// or redirect, or whatever action 
    }
    //rest of method if all okay
}

I usually like protecting methods rather than messing around with several middleware setups.

But just my opinion.

Hi, can you help me? In jetstreams we have a default navigation drop down menu, how can I change according to the user's role, I already tried directly in the view with a condition and directly in app.blade. I would appreciate your help

On your RouteServiceProvider class and boot method, you can programmatically set what will be value of the "HOME" constant.

after rewrite ResponseLogin how to redirect to hme page blade? I use this code in ResponseLogin.php:

return $request->wantsJson()
            ? response()->json(['two_factor' => false])
            : redirect()->intended("/");

and my home page is the blade. Unfortunately, it opens the home page in a pop-up dialog. and doesn't redirect to home with refresh page.