Associating Custom Field to Screen Results in XSRF Security Token Missing error

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: 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 は除く

問題

Attempting to associate Custom fields to a Screen leads to an XSRF token error, as seen below in the UI:

The following appears in the atlassian-jira.log

2019-11-05 08:51:10,591 https-jsse-nio-8443-exec-1 INFO username 111x1111x1 xxxx x.x.x.x /secure/admin/AssociateFieldToScreens.jspa [c.a.j.web.action.XsrfErrorAction] The security token is missing for 'username'. User-Agent : 'Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.90 Safari/537.36'

診断

環境

  • Occurs on a custom field that has 1000+ screens already associated with it

  • Instance has 10,000+ screens

Diagnostic Steps


The atlassian-jira.log may contain the following entries on the first occurrence of the problem:

org.apache.tomcat.util.http.Parameters processParameters
INFO: More than the maximum number of request parameters (GET plus POST) for a single request ([10,000]) were detected. Any parameters beyond this limit have been ignored. To change this limit, set the maxParameterCount attribute on the Connector.
 Note: further occurrences of this error will be logged at DEBUG level.


In the HAR file, on AssociateFieldToScreens request, the total rows in formData exceed 10,000 rows which are the list of parameters in the particular request. Example:


原因

The parameters count exceed the default configured in Tomcat, which is 10,000.

回避策

Go to a screen and add a custom field from there.

ソリューション

Adding and modifying the maxParameterCount parameter within the server.xml file will allow a larger HTML request to process. By default, this parameter is set to 10,000 and can be incrementally increased to find an optimal setting for the problematic HTML request:

  1. Jira を停止します。
  2. Edit server.xml to make sure the connector has the maxParameterCount configuration, for example: 

    <Connector port="8080"
                       maxThreads="150"
                       minSpareThreads="25"
                       connectionTimeout="20000"
                       enableLookups="false"
                       maxHttpHeaderSize="8192"
                       protocol="HTTP/1.1"
                       useBodyEncodingForURI="true"
                       acceptCount="100"
                       disableUploadTimeout="true"
                       relaxedPathChars="[]|" 
                       relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;"
                       maxParameterCount="10100" />
  3. Jira の起動





最終更新日 2020 年 11 月 23 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.