Filament login with multiple databases

@experimento Thank you for your reply, do you have any idea to simplify this logic single codebase with multiple databases ?

When I redirect the login page I got an error The page isn’t redirecting properly

@Tarantula About the redirection error: Please check that your Authentication routes are public and not blocked by Auth Middleware. Here is a reference link for this issue: https://laracasts.com/discuss/channels/general-discussion/the-page-isnt-redirecting-properly

About helping you with logic for multiple dynamic databases, that is beyond my capabilities. I have never used dynamic switching databases in Laravel. I also recommend @tray2 's advice.

@experimentor I do not change any routes, its all default routes of filament ?

@Tray2 Thank you for your reply, but my bussiness logic is more complicated than add a tenant_id in every table. Do you have any idea about why the middleware doesn't work properly in this case ?

@Tarantula Either your auth check fails cause you don't have a logged in user, or it fails because you don't have a company set in the session.

I still don't see any complexity that couldn't be solved in a single database. If it's security concerns, then I would setup subdomains, and a database for each subdomain, and a application instance for each as well.

@Tray2 there are some reasons that I use this logic, for example as you mentioned security, restore backups, imports, accessibility from some third parties and so. But this logic is not very complicated as you said. I created the solution about that in my API services, I use as subdomain with different branch for my mobile applications.

The solution is

public function login(Request $request)
{

    $credentials = $request->only('email', 'password');

    $loginService = new LoginService();

    $databases = LoginService::getDatabases($credentials);

    foreach ($databases as $database) {
        if (!GlobalHelper::databaseExist($database->database_name)) {
            continue;
        }

        config(['database.connections.mysql.database' => $database->database_name]);
        DB::purge('mysql'); // Clear the previous connection
        DB::reconnect('mysql'); // Reconnect to the new database
        if ($loginService->attempt($credentials)) {
            $user = UserService::getUserByEmail($credentials['email']);
            Auth::login($user);
            $token = JWTHelper::encode([
                'id' => auth()->user()->id,
                'exp' => time() + 28800,
                'company' => $database
            ]);
            return $this->sendResponse(['token' => $token]);
        }
    }

    return $this->sendError(__('messages.incorrect_login'), '', 404);
}

And for other request I use this middleware

public function handle(Request $request, Closure $next): Response
{
	$token = $request->bearerToken();					
     if (!$token) {
        return response()->json(['error' => 'Token not provided'], 401);
    }
    try {
        $decoded = JWTHelper::decode($token);
        $database = $this->getDatabase($decoded->database);
        config(['database.connections.mysql.database' => $database_name]);
        DB::purge('mysql'); // Clear the previous connection
        DB::reconnect('mysql'); // Reconnect to the new database
        Auth::login(UserService::getUserById($decoded->id));
        $request->merge((array)$decoded);
    } catch (\Exception $e) {
        return response()->json(['error' => $e->getMessage()], 401);
    }

    return $next($request);

}

entire project work perfectly, but this logic doesn't work in filament, and I don't know why. In filament the token doesn't exist and I put the database in session and check it in future request in middleware, but sessions doesn't exist when arrived in middleware? I check also Filament::auth()->user() also doesn't exist, but the login process finished successfully. Is it terminated somewhere ? Maybe there are some other logic behind the filament that I don't know, because in normal conditions I will able to check Filament::auth()->user() in middleware after login also redirect in login page correctly. I think there is an issue about order of middleware