Description of problem:
A customer had a cockpit login issue. This login issue happened when the longer HTTP GET request was received. 

This customer configured SSO login with Kerberos for cockpit. Some user could log into the cockpit with SSO enabled, but other user could not login.

The following is the sequence I found when the problem happened.

1)  The browser sent GET method with /cockpit/login to cockipt-ws
2)  cockpit-ws created a cockpit-session process
3)  cockpit-session sent to cockpit-ws:
{"command":"authorize","cookie":"sessionXXXXXXXXXXXXXXX","challenge":"*"}
4)  cockpit-ws sent to cockpit-session:
{"command":"authorize","cookie":"sessionXXXXXXXXXXXXXXX","response":"Negotiate"}
5)  cockpit-session sent to cockpit-ws:
{"command":"authorize","cookie":"sessioXXXXXXXXXXXXXXXX","challenge":"Negotiate"}
6)  cockpit-ws sent to browser:  "HTTP/1.1 401 Authentication required" and "WWW-Authenticate: Negotiate"
7)  browser sent to cockpit-ws:  "GET /cockpit/login HTTP/1.1" and "Authorization: Negotiate YIILc..."

The size of the last GET request was 4101 bytes, and cockpit-ws didn't pass the Authorization data into cockpit-session.

This is the problem of the request buffer size in cockpit-ws. Now it's 4096.
So, it cannot process the request longer than 4096.

The customer confirmed that the problem was fixed by a test package to increase the buffer size into 8192.

I'll attach the patch on this bugzilla.

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 7

How reproducible:
Always reproduced with a specific user in customer's system only.

Steps to Reproduce:
1. Setup cockpit SSO configuration.
2. Make a larger HTTP request than 4096 to cockpit.
   Not sure if we can do it by intent. 

In the customer's case, the data following "Authorization: Negotiate" was too long. 


Actual results:
cockpit login didn't work with SSO with some users.

Expected results:
cockpit login works with SSO with any user.

______________________________
Acceptance Criteria (Proposal)

Given Cockpit SSO with kerberos is set, users can authenticate via kerberos
Corner case: user can log in even if HTTP request larger than 4096
(Both should be covered by automated regression test)