Corrected QA Mail Application URL and Login Redirect
Executive summary
Fixed a typo in the QA environment configuration that produced an invalid Mail application domain. The Mail app address and the default post-login redirect now point to the correct QA host, restoring access to Mail in the QA environment.
Why this was needed
The QA build configuration contained a misspelled hostname (cortex-maillqa with a doubled "l") for two settings: the Mail application URL and the default redirect destination used after sign-in. Because the domain did not resolve correctly, users in QA could be sent to a broken Mail address when navigating to Mail or after logging in.
Client / user impact
QA testers and stakeholders can now reach the Mail application at its correct address, and the post-login redirect lands users on a working page. This change affects only the QA environment; Production and other environments were not impacted. No application functionality changes — this restores expected navigation.
Technical scope
- Updated
.github/workflows/docker-ecr.yml(CI/CD build configuration) for the QA environment. - Corrected
NEXT_PUBLIC_MAIL_APP_URLfromhttps://cortex-maillqa.datagainservices.comtohttps://cortex-mailqa.datagainservices.com. - Corrected
NEXT_PUBLIC_DEFAULT_REDIRECT_URLfrom the same misspelled host tohttps://cortex-mailqa.datagainservices.com. - Two lines changed; no application code or business logic modified.
Risk & mitigation
Low risk. The change is a one-character hostname correction in QA build-time environment variables, scoped to the QA workflow only. Mitigation: requires a fresh QA deployment for the corrected values to take effect; verify the new domain resolves and serves the Mail app before sign-off.
QA validation focus
- Trigger a QA build/deploy so the updated environment variables are baked in.
- Navigate to the Mail application in QA and confirm it loads at
https://cortex-mailqa.datagainservices.com. - Log in and confirm the default post-login redirect lands on the working Mail host (no broken/unreachable page).
- Confirm other QA app URLs (SSO, Vendor, Admin) still resolve correctly and were not affected.