Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.50.0-rc1 on api v0 no longer returns location for authentication requests #1054

Closed
flands opened this issue Dec 20, 2018 · 1 comment
Closed
Milestone

Comments

@flands
Copy link
Contributor

flands commented Dec 20, 2018

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

  • 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

@flands
Copy link
Contributor Author

flands commented Dec 20, 2018

/cc @kflynn

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants