Skip to:
I've noticed in AKS deployments where we have https+DNS, when my session times out and I get taken to the page that says:
Authentication failed: invalid session. Please click here to log into ECL Watch.
When I click on the "Please click here to log into ECL Watch" it redirects me back to login with :80 (port 80) appended to the URL which it is not listening on, so it breaks.
As an example, for us-fcrathor-dev, it redirects to:https://eclwatch.us-fcrathor-dev.azure.lnrsg.io:80/
Discussed with Tony. We may remove the port from the redirect URL or change it to the default port (443).
The port is read from HTTP Host header. Seems working for bare-metal environment, not for AKS?
I should take a look where the port comes from.
This seems like it might not be an ECL Watch issue directly; it is the response from CEspHttpServer::sendSessionReloadHTMLPage in https://github.com/hpcc-systems/HPCC-Platform/blob/candidate-8.10.x/esp/bindings/http/platform/httpservice.cpp#L1870 or perhaps there is an unexpected configuration issue with the https+DNS set up? That function is always appending a port to the url in question.
I've noticed in AKS deployments where we have https+DNS, when my session times out and I get taken to the page that says:
Authentication failed: invalid session. Please click here to log into ECL Watch.
When I click on the "Please click here to log into ECL Watch" it redirects me back to login with :80 (port 80) appended to the URL which it is not listening on, so it breaks.
As an example, for us-fcrathor-dev, it redirects to:
https://eclwatch.us-fcrathor-dev.azure.lnrsg.io:80/