Layout problems due to a cookie size after installation of third party SSO
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
問題
Browsing through the UI after installing third-party SAML SSO for JIRA display problem will be visible.
診断
環境
- JIRA with SAML SSO for JIRA
Diagnostic Steps
Checking the HAR file 400 errors will be visible.
400 BAD REQUEST
If you receive this error frequently, the best thing to do is to delete the Cookies for that particular domain. Let us say, if you are receiving this error when you visit any page on say, example.com, then you should delete all the Cookies of example.com from your browser’s cache.
原因
Header size is too big for certain requests. Increasing the value on Tomcat should help in this case.
ソリューション
Increase or add "maxHttpHeaderSize" size to "16000" in used connector in the <Jira-install>/conf/server.xml like this:
<Connector port="8090" connectionTimeout="20000" maxThreads="200" minSpareThreads="10" enableLookups="false" acceptCount="10" URIEncoding="UTF-8" /><Connector port="8090" connectionTimeout="20000" maxThreads="200" minSpareThreads="10" enableLookups="false" acceptCount="10" URIEncoding="UTF-8" maxHttpHeaderSize="16000"/>