Filament•2mo ago

canAccessPanel() Not being called

I am triying to secure access but my canAccessPanel() is not being called. I am using FilamentUser contract in User. And below is my code. to test i am always retirnung false but i am still able to access panel. I cleared all caches.

    public function canAccessPanel(Panel $panel): bool
    {
        dd('canAccessPanel is being called!');
        return false;

        $panelId = $panel->getId();
        if ($panelId === 'labaiq-team') {
            return $this->user_type === 'platform_team_member' && str_ends_with($this->email, '@labaiq.com') && $this->email_verified_at;
        }

        if($panelId === 'user' || $panelId === 'company'){

            return $this->user_type === 'general_user';
        }


        return false;
    }

    public function canAccessPanel(Panel $panel): bool
    {
        dd('canAccessPanel is being called!');
        return false;

        $panelId = $panel->getId();
        if ($panelId === 'labaiq-team') {
            return $this->user_type === 'platform_team_member' && str_ends_with($this->email, '@labaiq.com') && $this->email_verified_at;
        }

        if($panelId === 'user' || $panelId === 'company'){

            return $this->user_type === 'general_user';
        }


        return false;
    }

Solution:

Error was due to using the Custom authentication middleware in all my panels. I had commented out Authenticate::class from all auth middleware. Filament native authenticate middleware calls canAccessPanel() method directly. Whereas I implemented CustomAuthenticate::class and removed filament one which caused and issue. Fix was to include this below peice of code in my CustomAuthentciate. ```$panel = Filament::getCurrentPanel(); abort_if( $user instanceof FilamentUser ? (! $user->canAccessPanel($panel)) :...

Jump to solution

6 Replies

Dennis Koch•2mo ago

Is your environment local?

PritborOP•2mo ago

Hi @Dennis Koch . I tested in both local and production.

Tin•2mo ago

I suggest looking if you have a piece of code that does this:

Gate::before(function ($user, $ability) {
    return $user->super_admin == 1 ? true : null;
});

But that is just a hunch

Dennis Koch•2mo ago

Do you implement the interface on the user model?

PritborOP•2mo ago

Hi @Dennis Koch I have custom authenticate middleware. Can this be an issue? Unable to figureout issue.

 use Illuminate\Auth\Middleware\Authenticate as Middleware;




class CustomAuthenticate extends Middleware
{

    public function handle($request, Closure $next, ...$guards)
    {

        if (!Auth::check()) {
            // Save the intended URL in the session
            session(['url.intended' => $request->url()]); // Save intended URL

            session()->flash('open_authentication_modal', true);
            // Handle AJAX (JSON) request case
            if ($request->expectsJson()) {
                return response()->json(['message' => 'Unauthorized.'], 401);
            }

            // Return null to allow the modal to open without redirecting
            return redirect('/'); // Redirect to the home page
        }

        return $next($request); // Continue processing the request
    }
}

 use Illuminate\Auth\Middleware\Authenticate as Middleware;




class CustomAuthenticate extends Middleware
{

    public function handle($request, Closure $next, ...$guards)
    {

        if (!Auth::check()) {
            // Save the intended URL in the session
            session(['url.intended' => $request->url()]); // Save intended URL

            session()->flash('open_authentication_modal', true);
            // Handle AJAX (JSON) request case
            if ($request->expectsJson()) {
                return response()->json(['message' => 'Unauthorized.'], 401);
            }

            // Return null to allow the modal to open without redirecting
            return redirect('/'); // Redirect to the home page
        }

        return $next($request); // Continue processing the request
    }
}

I am using like

            ->authMiddleware([
                // Authenticate::class,
                CustomAuthenticate::class,
                EnsureUserHasVerifiedEmailMobile::class,
            ], isPersistent: true)

            ->authMiddleware([
                // Authenticate::class,
                CustomAuthenticate::class,
                EnsureUserHasVerifiedEmailMobile::class,
            ], isPersistent: true)

in all panels. Yes I checked. CanAccessPanel is now called when i commented out my Customauthenticate::class and reused filament Authenticate::class. not sure how to fix this. Thsnks I got the fix. I implemented

        $panel = Filament::getCurrentPanel();

        abort_if(
            $user instanceof FilamentUser ?
                (! $user->canAccessPanel($panel)) :
                (config('app.env') !== 'local'),
            403,
        );

        $panel = Filament::getCurrentPanel();

        abort_if(
            $user instanceof FilamentUser ?
                (! $user->canAccessPanel($panel)) :
                (config('app.env') !== 'local'),
            403,
        );

in my CustomAuthenticate middleware and it did what i needed.

Solution

Pritbor•2mo ago

$panel = Filament::getCurrentPanel();

        abort_if(
            $user instanceof FilamentUser ?
                (! $user->canAccessPanel($panel)) :
                (config('app.env') !== 'local'),
            403,
        );

$panel = Filament::getCurrentPanel();

        abort_if(
            $user instanceof FilamentUser ?
                (! $user->canAccessPanel($panel)) :
                (config('app.env') !== 'local'),
            403,
        );

Gaming

Programming

canAccessPanel() Not being called

Did you find this page helpful?