You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 0.40.1 if you connect to an auth service that returns a redirect via a location header then the browser receives the location header and redirects as expected. In 0.50.0-rc1 the location header is not sent -- instead a HREF response is sent.
To Reproduce
On Ambassador 0.40.x, configure external authentication. Ensure the external authentication does a redirection based on the Location header.
Upgrade to Ambassador 0.50.0-rc1
Attempt to authenticate
Response to browser does not include a Location header. HREF is returned on the webpage.
Expected behavior
Ambassador returns Location header as this was the behavior in 0.40.x
Versions (please complete the following information):
Ambassador: 0.50.0-rc1
Kubernetes environment [e.g. Minikube, bare metal, Google Kubernetes Engine] kops
Version [e.g. 1.8.1] 1.11.5
Additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
In 0.40.1 if you connect to an auth service that returns a redirect via a location header then the browser receives the location header and redirects as expected. In 0.50.0-rc1 the location header is not sent -- instead a HREF response is sent.
To Reproduce
Response to browser does not include a Location header. HREF is returned on the webpage.
Expected behavior
Ambassador returns Location header as this was the behavior in 0.40.x
Versions (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: