Customizing Logout about fortify

[ali-alharthi]

Fortify has the following in its config file: 'guard' => 'web'.
I am sure it only uses that guard for everything it does including the logout 👍🏼
This is what Fortify does in the destroy method a.k.a logout:

    /**
     * Destroy an authenticated session.
     *
     * @param  \Illuminate\Http\Request  $request
     * @return \Laravel\Fortify\Contracts\LogoutResponse
     */
    public function destroy(Request $request): LogoutResponse
    {
        $this->guard->logout();
        $request->session()->invalidate();

        $request->session()->regenerateToken();

        return app(LogoutResponse::class);
    }

I believe @taylorotwell built Fortify to be the official Laravel package for authentication. However, consider it as a skeleton, so you can implement your logic by extending classes or simply build a package that consumes in the way you want. Like Jetstream for example.

[driesvints]

Hi there,

Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

• Laracasts Forums
• Laravel.io Forums
• StackOverflow
• Discord
• Larachat
• IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!

Thanks.

[digenPrime]

I want to add an activity and save that activity in database such that "@username has logged out at H:i:s". Can someone tell me how to do override the logout functionality in the above code that @ali-alharthi has provided? @driesvints @ali-alharthi.

[cartayapardo]

Hello, I am using fortify and it happens that when I logout and try to login with another user, I access with the previous user and not with the new one. This does not always happen, what can be wrong?

[oldravian]

this issue should be open. how to overwrite the method mentioned by @ali-alharthi

[ali-alharthi]

@digenPrime You should read more about events. It should direct you to the correct way.
@ChaudharyHabib This isn't an issue as explained by @driesvints
Nevertheless, you can overwrite it by simply, use a custom routes and use you custom controller that extends Fortify's controller or simply build yours. I wouldn't go into deep but here is a key thing: Fortify::ignoreRoutes();.