Skip to content
This repository has been archived by the owner on Dec 21, 2023. It is now read-only.

upstream sent too big header while reading response header from upstream error while SSO logout #4662

Closed
1 of 12 tasks
jskelin opened this issue Jul 15, 2021 · 0 comments · Fixed by #4663
Closed
1 of 12 tasks
Labels
area:api type:bug Something is not working as intended/documented
Milestone

Comments

@jskelin
Copy link
Contributor

jskelin commented Jul 15, 2021

Your issue may already be reported! Please search on the issue tracker before creating a new one.

Environment

  • Client OS: (e.g., Linux, macOS, Windows): Lonux
  • Keptn Version (keptn version): 0.8.6
  • Kubernetes Cloud Provider (e.g., GKE, AKS): GKE
  • Kubernetes version (kubectl version): ??

Affected Component

  • Docs
  • CLI
  • Kubernetes Integration
  • Openshift Integration
  • Helm
  • Istio
  • Bridge
  • Approval
  • Datastore
  • REST API
  • eventbroker / distributor
  • jmeter

Describe the bug
Logout action results in http 502.
Bridge je setted to use SSO.

To Reproduce

Steps to reproduce the behavior:

  1. login
  2. got to upper left corner and open menu
  3. click logout

Expected behavior

User should be redirect to SSO system in which he can do logout.

Current behavior
User is not redirected to SSO service. Instead user land on error page (HTTP 502) generated by nginx.

Screenshots

Additional context

@agrimmer agrimmer added type:bug Something is not working as intended/documented area:api labels Jul 15, 2021
@agrimmer agrimmer added this to the 0.8.7 milestone Jul 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area:api type:bug Something is not working as intended/documented
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants