Overview
This article describes the process to follow when many users are unable to log in to the instance getting 400 Bad Request error and the customer is on Kerberos SSO.
Environment
Jive On-Premise
Process
After setting the LimitRequestFieldSize value to 65536 in httpd.conf of apache, make sure that the maxHttpHeaderSize also matches this size on the Tomcat Connector.
- With the
server.xmlfiles, please change:
From:
<Connector
port="${http.port}" protocol="HTTP/1.1" address="${http.addr}" redirectPort="443"
URIEncoding="UTF-8" connectionTimeout="20000">
</Connector>
To:
<Connector
port="${http.port}" protocol="HTTP/1.1" address="${http.addr}" redirectPort="443"
URIEncoding="UTF-8" connectionTimeout="20000" maxHttpHeaderSize="65536">
</Connector> - Perform a full restart of the web app nodes for the changes to take effect.
Confirmation
The user will be able to log in without getting a 400 Bad Request error.
Comments
0 comments
Article is closed for comments.