It does not work with Multi-Tenant app about filament-impersonate HOT 3 CLOSED

Multi-tenancy can be implemented in 100 different ways. I don't know how yours works, I can't tell you what needs to be handled.

The underlying impersonate package does fire some events when impersonation happens, maybe you can listen for those events and wire up the appropriate tenant that way?

https://github.com/404labfr/laravel-impersonate?tab=readme-ov-file#events

from filament-impersonate.

in my case, I have 2 panels, one with multi-tenancy and the other without. When I impersonate a user that does not belong to a tenant, I get memory leak. Then I added the user to a tenant and then it worked as normal.

from filament-impersonate.

Hey @altomar

I did not hit the memory issues but here is what worked for me in case it helps you.

In your web.php, define a custom route for impersonate.

Route::get('/impersonate/{user}', ImpersonateController::class)->name('impersonate');

Create the ImpersonateController.

use App\Models\User;
use Filament\Support\Concerns\EvaluatesClosures;
use Illuminate\Http\RedirectResponse;
use Illuminate\Http\Request;
use STS\FilamentImpersonate\Concerns\Impersonates;

class ImpersonateController extends Controller
{
    use EvaluatesClosures; // We need this trait in order use the impersonate feature from the plugin
    use Impersonates;

    public function __invoke(Request $request, User $user): RedirectResponse
    {
        abort_unless(auth()->check() && auth()->user()->is_admin, 403);

        return $this->impersonate($user); // we are using the function from the plugin.
    }
}

Finally in UserResource, pass the custom url to Impersonate action.

->actions([
        Impersonate::make()
            ->url(fn (User $record) => route('impersonate', $record)),
])

from filament-impersonate.