tree 7576b197c2f042f58840347453c1205752293c92
parent 430f9c7c88e9622055655e4f194766b25d7019f3
author CritasWang <critas@outlook.com> 1771925761 +0800
committer CritasWang <critas@outlook.com> 1771925761 +0800

feat(flight-sql): add per-client session isolation and security hardening

- Add x-flight-sql-client-id header support for per-client USE database
  isolation via FlightSqlAuthHandler and ClientIdMiddlewareFactory
- Use \0 (null byte) delimiter in clientSessionCache key to prevent
  username/clientId collision attacks
- Validate clientId: alphanumeric + dash only, max 64 chars, fail-closed
  for non-empty invalid values (SecurityException)
- Add maximumSize(1000) to tokenCache and clientSessionCache to prevent
  resource exhaustion from arbitrary clientIds
- Remove LoginLockManager (userId=-1L caused cross-user lock collision;
  getUserId() is blocking RPC incompatible with directExecutor())
- Remove unused flightClient field from IT
- Add directExecutor() + HTTP/2 flow control window tuning (1MB) on
  NettyServerBuilder to fix end-of-stream mid-frame errors
- Document all functional gaps vs SessionManager.login() (password
  expiration, login lock, checkUser cache-miss risk)

Tests (9/9 pass):
- 5 original Flight SQL query tests
- testUseDbSessionPersistence: USE context persists across connections
- testUseDbWithFullyQualifiedFallback: USE + qualified/unqualified queries
- testUseDbIsolationAcrossClients: Client B fails without USE context
- testInvalidClientIdRejected: non-empty invalid clientId rejected