ansible/awx

SAML Login - 502 Bad Gateway - upstream sent too big header

Open

#3,836 opened on May 6, 2019

View on GitHub
 (6 comments) (1 reaction) (0 assignees)Python (3,333 forks)batch import
component:apicomponent:authenticationhelp wantedtype:bug

Repository metrics

Stars
 (13,071 stars)
PR merge metrics
 (Avg merge 24d 6h) (30 merged PRs in 30d)

Description

ISSUE TYPE
  • Bug Report
SUMMARY

I am trying to login with SAML and although my user logs in successfully I am receiving 502 error. Same thing does not happen with other users.

Logs Sample:

2019-05-06 09:11:40,603 INFO     awx.sso.views User **** logged in
2019/05/06 09:11:40 [error] 136#0: *2704 upstream sent too big header while reading response header from upstream, client: 172.19.0.7, server: _, request: "GET /sso/complete/ HTTP/1.1", upstream: "uwsgi://127.0.0.1:8050", host: "*******", referrer: "*****" [pid: 140|app: 0|req: 400/1218] 172.19.0.7 () {54 vars in 1863 bytes} [Mon May  6 09:11:40 2019] GET /sso/complete/ => generated 0 bytes in 92 msecs (HTTP/1.1 301) 10 headers in 5267 bytes (1 switches on core 0)
ENVIRONMENT
  • AWX version: 4.0.0
  • AWX install method: docker on linux
  • Ansible version: 2.5.1
  • Operating System: Ubuntu 18.04
  • Web Browser: Firefox, Chromium
ADDITIONAL INFORMATION

Based on Google search I am suspecting that an increase in proxy_buffer_size is required to nginx configuration of awx_web, but I am opening the issue to be sure.

Contributor guide

Research direction
Inspect the nginx configuration for awx web and increase proxy buffer size to avoid upstream sent too big header error. The default buffer size may be too small for SAML response headers.
Tech stack
pythondocker
Domain
backendinfrastructure
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
DockerNginx
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70