Remove the fake permissions sets used to workaround too long headers
Description
Environment
None
Potential Workaround
None
Checklist
hideTestRail: Results
Activity
Show:

Marc Johnson January 29, 2024 at 10:09 AM
bq. I'm not very familiar with permissions at this level. What's the best way for me to check to see if this ticket is still needed?
This has a purely technical impact and can only really be identified by checking the module descriptor
These types of permission sets are still present, and typically start with modperms.circulation...
like this example

Stephanie Buck January 25, 2024 at 9:46 PM
, I'm not very familiar with permissions at this level. What's the best way for me to check to see if this ticket is still needed?
Details
Details
Assignee
Unassigned
UnassignedReporter

Priority
Development Team
Vega
Parent
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created June 19, 2020 at 11:28 AM
Updated January 29, 2024 at 10:09 AM
TestRail: Cases
TestRail: Runs
In order to workaround the challenge that including many permissions in the
modulePermissions
property caused headers to be generated that were rejected by Netty as being too long, the permissions were moved to fake permission sets.Now that Okapi 3.x does this automatically (according to this comment), these can now be removed.