fix: cluster topology connect fails with NOAUTH when username is empty string (#252)

When connecting to a discovered cluster node via the Cluster Topology page,
credentials were silently dropped if username was an empty string (e.g. the
ElastiCache 'default' user).

The condition `primary.username && primary.password` short-circuits to false
when username is "", so neither username nor password was sent in the
connectPending payload, causing a NOAUTH error on the server side.

Fix: gate only on password presence and default username to empty string.

Also includes a Dockerfile fix to install ca-certificates for TLS connections.

Signed-off-by: Alexey Temnikov <attemnik@amazon.com>

Author: alexey-temnikov

apps/frontend/src/components/cluster-topology/cluster-node.tsx

@@ -43,8 +43,8 @@ export function ClusterNode({
       const connectionDetails: ConnectionDetails = {
         host: primary.host,
         port: primary.port.toString(),
-        ...(primary.username && primary.password && {
-          username: primary.username,
+        ...(primary.password && {
+          username: primary.username ?? "",
           password: await secureStorage.encrypt(primary.password),
         }),
         tls: primary.tls,

docker/Dockerfile.app

@@ -16,6 +16,9 @@ RUN npm run build:all
 # -------- Production Runtime --------
 FROM node:22-bookworm-slim
 
+# Install CA certificates for TLS connections to ElastiCache
+RUN apt-get update && apt-get install -y ca-certificates && update-ca-certificates && rm -rf /var/lib/apt/lists/*
+
 WORKDIR /app
 
 ENV NODE_ENV=production