stancl/tenancy Path Identification
Hi!
I need some advice regarding Filament v3 together with stancl/tenancy.
For security reasons I am using stancl/tenancy with one database per Tenant.
The issue I have is, that I use path identification, instead of subdomain identification. So a path looks like: example.com/<tenant_id>/<panel>/<resource>
I cannot access that route. I think I need to modify the Filament routing somehow, that first the tenant identification is read and the middleware is loaded to modify the database context and then execute the normal routing.
Does anyone have any advice on that for me? Any comment is highly appreciated!
I need some advice regarding Filament v3 together with stancl/tenancy.
For security reasons I am using stancl/tenancy with one database per Tenant.
The issue I have is, that I use path identification, instead of subdomain identification. So a path looks like: example.com/<tenant_id>/<panel>/<resource>
I cannot access that route. I think I need to modify the Filament routing somehow, that first the tenant identification is read and the middleware is loaded to modify the database context and then execute the normal routing.
Does anyone have any advice on that for me? Any comment is highly appreciated!
