Custom Tenant Finder using authenticated user about laravel-multitenancy

[masterix21]

Skip the finder and add two listeners for these events:

• Illuminate\Auth\Events\Login
• Illuminate\Auth\Events\Logout

When the login event will be fired, do your $tenant->makeCurrent(), and when the logout event will be fired, do your $tenant->forgot().

I think it’s better for you, try and give me feedback.

[masterix21]

If you call request()->auth() before the StartSession middleware, you'll get null always. I can suggest using another approach: instead of work with a Finder, write a middleware (in web, after StartSession) to find your tenant. It will work.

[masterix21]

@dambridge, the package works if you set a tenant "as current": it does not care if you do it from a middleware or a task.

[sandulat]

@masterix21 @freekmurze If I do the $tenant->makeCurrent() in the login event listener, the tenant is being set, however, after I'm redirected, it is not being persisted and it becomes null. Is there any step that I'm missing? Or is this something on my side?

Basically I'm just trying to switch the tenant on the session level, not domain level.

I'm not sure if this package persists the tenant in the session. If not, I've tried to manually store the tenant id in the session, when the MadeTenantCurrentEvent is fired. However, the session is not being set in the TenantFinder and I can't read the id.

[masterix21]

Last but not least, add a listener to Illuminate\Auth\Events\Authenticated event... it's another solution ;)

[henryavila]

Just to register, the middleware approach gave me the needed flexibility. Worked perfectly.
I set the tenant before the return $next($request);

[dambridge]

Sorry for the necro bump, just curious to see what you ended up doing. I too want to abandon the whole subdomain thing and ultimately be able to attach users to multiple tenants.

Question: if we just check for a tenant id in middleware, are we not losing some part of the identification pipeline this package needs?