Four problems you inherit the moment your SQL client runs on a server
A desktop database client makes two demands nobody writes down: every laptop has to reach the production network, and every laptop has to hold a copy of every credential. Move the client onto a server next to the data and both demands disappear. The credential lives in one place instead of sixty. The network path becomes a deployment topology instead of a VPN grant per person. That is the trade.…
Running a SQL client on a server instead of a desktop machine introduces four key problems. First, the trust boundary shifts from the OS user on a laptop to the server process, which now has to verify the identity of each caller to the database. Second, the server must manage a single credential for all connections rather than distributing credentials to each laptop.
Third, the network path transitions from a per-person VPN connection to a shared server topology for all database access. Fourth, desktop apps have no cookies or ambient authority, while browser-based clients do, requiring additional security measures like origin comparison. These issues were encountered while building LibreDB Studio, and two of them were initially addressed incorrectly.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
