M8F-56: Fix local development issue by updating Vite host and backend proxy configuration

[sonal-aot]

JIRA Ticket

M8F-56

Description

Fix infinite login redirect loop when running frontend locally via npm start.

Problem

The Vite dev server proxy in extensions/frontend/vite.config.ts had the backend
proxy target hardcoded to http://localhost:8000. When the backend runs on a
non-localhost IP (e.g., http://192.168.1.77:8000), all proxied API requests
(/v1.0/*) were sent to the wrong host, causing every call to fail with a
connection error → 401 Unauthorized → redirect to login → infinite redirect loop.

This issue did not affect Docker because Docker uses nginx for routing internally,
bypassing the Vite proxy entirely.

Fix

The proxy target is now dynamically resolved from the root .env file using the
existing M8FLOW_BACKEND_URL_FRONTEND / M8FLOW_BACKEND_URL variables — the same
values already used for the backend itself.

// Before — hardcoded, breaks non-localhost setups
target: `http://localhost:${backendPort}`

// After — reads real backend URL from .env
const backendUrl =
  rootEnv.M8FLOW_BACKEND_URL_FRONTEND ||
  rootEnv.M8FLOW_BACKEND_URL ||
  process.env.M8FLOW_BACKEND_URL ||
  `http://localhost:${backendPort}`;

proxy: { '/v1.0': { target: backendUrl } }

Type

• Feature
• Bug fix
• Documentation
• Other

Changes

• Backend
• Frontend
• Documentation

Testing

Local Dev (npm start)

• Started the backend on http://192.168.1.77:8000 (non-localhost IP)
• Ran npm start from extensions/frontend/
• Opened http://localhost:8001 in the browser
• Logged in via Keycloak — login completed successfully without redirect loops
• Verified API calls (/v1.0/permissions-check, /v1.0/status) returned 200 OK
  with the Authorization token correctly attached in request headers
• Confirmed no infinite login redirects in the browser Network tab

Docker (regression check)

• Built and ran the full stack via Docker Compose
• Login and API calls continued to work as expected — no regression

Related Issues

Closes M8F-56

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[andrepestana-aot]

Looks good.