It's not possible to add user/group permissions to a space with hundreds of existing users and/or groups
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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.
*Except Fisheye and Crucible
Summary
If a user or group is added to space permissions that already has hundreds of users and/or groups, the transaction appears to complete without error. However, upon closer inspection, the user or group is not added.
Diagnosis
- The space permissions to which the user or group is being added already has hundreds of other users and/or groups.
- After saving the user or group to the space permissions, the page reloads and no error messages are displayed.
- After the page reloads, the recently added user and/or group permission does not appear.
- The catalina.log will show this message:
10-Aug-9999 20:58:20.930 INFO [http-nio-8090-exec-9] org.apache.tomcat.util.http.Parameters.processParameters 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.
Cause
By default, the Tomcat server limits the number of parameter and value pairs within the HTTP request to 10,000. When saving space permissions, Confluence sends one parameter/value pair for each user and/or group and for each permission. Since each user/group can have multiple permissions, this number of parameter/value pairs can quickly increase beyond the 10,000 limit.
For more details on the Tomcat maxParameterCount parameter, please see: Apache Tomcat 9 Configuration Reference
Solution
Solution 1
If hundreds of users have been added to a space individually, the best option would be to use Groups to provide permissions to Space.
Solution 2
If the option above is not viable, increase the maxParameterCount within Tomcat:
- Stop Confluence
- Add the maxParameterCount parameter to the Tomcat connector in the <confluence-install-folder>/conf/server.xml file. For example:
{code}
<Connector port="8090" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8443" maxParameterCount="15000"/>
{code}
- Start Confluence