项目介绍

stechstudio/filament-impersonate 是一个托管在 GitHub 上的开源项目,主要使用 PHP 编写,目前获得 401 个 Star、94 次 Fork。

仓库全名
stechstudio/filament-impersonate
Star 数
401
Fork 数
94

README 摘要

Filament Impersonate This is a plugin for Filament that makes it easy to impersonate your users. Installation You know the drill: Quickstart 1. Add table action First open the resource where you want the impersonate action to appear. This is generally going to be your UserResource class. Go down to the table method. After defining the table columns, you want to add Impersonate as a new action for the table via…

完整内容见 GitHub 原始 README 或本页 。

常见问题

filament-impersonate 用什么语言开发?

主要使用 PHP 编写,目前有 401 个 Star。

如何获取 filament-impersonate 的源码?

可以直接克隆仓库:git clone https://github.com/stechstudio/filament-impersonate.git,默认分支为 master;安装与运行步骤见仓库 README。

filament-impersonate 最近还在维护吗?

仓库最近一次更新为 3 天前,当前没有未关闭的 Issue;Star 数为 401,可作为社区活跃度的参考。

关于

Filament plugin that makes it easy to impersonate your users

描述取自 GitHub 官方 API,中文内容由 GitRead 中文社区 编辑团队整理。

简要分析

热度分
595
价值分
269
活跃状态
活跃

语言占比

Blade
PHP

Release

README

Filament Impersonate

Latest Version on Packagist Total Downloads Software License

This is a plugin for Filament that makes it easy to impersonate your users.

Installation

You know the drill:

composer require stechstudio/filament-impersonate

Quickstart

1. Add table action

First open the resource where you want the impersonate action to appear. This is generally going to be your UserResource class.

Go down to the table method. After defining the table columns, you want to add Impersonate as a new action for the table via actions method. Your class should look like this:

namespace App\Filament\Resources;

use Filament\Resources\Resource;
use STS\FilamentImpersonate\Actions\Impersonate;

class UserResource extends Resource {
    public static function table(Table $table)
    {
        return $table
            ->columns([
                // ...
            ])
            ->actions([
                Impersonate::make(), // <--- 
            ]);
    }

You can also define a guard and redirectTo for the action:

Impersonate::make()
    ->guard('another-guard')
    ->redirectTo(route('some.other.route'));

If your panel uses ->spa() and the redirect target isn’t a Livewire-aware page, opt out of SPA navigation to force a full page load:

Impersonate::make()
    ->redirectTo(route('some.other.route'))
    ->withoutSpa();

2. Add the page action

Now open the page where you would want the button to appear, this will commonly be EditUser;

Go to the getHeaderActions method and add the Impersonate page action here.

<?php
namespace App\Filament\Resources\UserResource\Pages;

use App\Filament\Resources\UserResource;
use Filament\Resources\Pages\EditRecord;
use STS\FilamentImpersonate\Actions\Impersonate;

class EditUser extends EditRecord
{
    protected static string $resource = UserResource::class;

    protected function getHeaderActions(): array
    {
        return [
            Impersonate::make()->record($this->getRecord()), // <--
        ];
    }
}

Note: you must pass the record in as seen in this example!

3. Add the banner to your non-filament blade layout(s)

If your app is entirely contained within Filament, you’re already done! The banner gets registered automatically.

However, if you impersonate a user and then visit non-Filament pages or layouts, you’ll be stuck. In those cases, you’ll need to display a notice in your app whenever you are impersonating another user.

You can do that by adding <x-impersonate::banner/> to your master layout(s) before the closing </body> tag.

4. Profit!

That’s it. You should now see an action icon next to each user in your Filament UserResource list:

table action

When you click on the impersonate icon you will be logged in as that user, and redirected to your main app. You will see the impersonation banner at the top of the page, with a button to leave and return to Filament:

banner

Configuration

All configuration can be managed with ENV variables, no need to publish and edit the config directly. Just check out the config file.

Facade API

You can use the facade for programmatic impersonation control:

use STS\FilamentImpersonate\Facades\Impersonation;

if (Impersonation::isImpersonating()) {
    Impersonation::leave();
}

Authorization

By default, any authenticated Filament user can impersonate other users. You can restrict this by adding a canImpersonate method to your User model:

class User {

    public function canImpersonate()
    {
        return $this->is_admin;
    }

}

You can also control which targets can be impersonated. Just add a canBeImpersonated method to the user class with whatever logic you need:

class User {

    public function canBeImpersonated()
    {
        // Let's prevent impersonating other users at our own company
        return !str_ends_with($this->email, '@mycorp.com');
    }
    
}
Note 注意

As of 4.0, the plugin detects soft-deleted targets and prevents impersonation. You can set FILAMENT_IMPERSONATE_ALLOW_SOFT_DELETED=true in your .env to override this behavior.

Customizing the banner

The blade component has a few options you can customize.

Style

The banner is dark by default, you can set this to light, or auto.

<x-impersonate::banner style='light'/>

Display name

The banner will show the name of the impersonated user, assuming there is a name attribute. You can customize this if needed:

<x-impersonate::banner :display='auth()->user()->email'/>

Potential Issues and Workarounds

403 when a ListUsers widget has InteractsWithPageTable

TL;DR: Add a guard clause like this to your UserPolicy::viewAny() method:

<?php

use STS\FilamentImpersonate\Facades\Impersonation;

public function viewAny(User $user): bool
{
    if (Impersonation::isImpersonating()) {
        return true;
    }

    // ... Any other checks here
}

The core of this problem is that the Livewire components on the page attempt to re-render before the redirect occurs.

Then, even with a ->redirectTo() set, if your policies prevent the impersonated user from accessing the user list that you’re impersonating from, Filament attempts to re-render the table widgets, triggering a 403.

There’s not much we can do about this, but checking whether the current user is impersonating already will at least avoid the 403.

评论

暂无评论