Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-24599

Add a new property to restore the old behavior for local ACP computing

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 8.10, 9.10, 10.1
    • Fix Version/s: 8.10-HF29, 9.10-HF06, 10.2
    • Component/s: Core
    • Release Notes Summary:
      The nuxeo.security.acl.legacyBehavior property can be used to enable legacy ACL behavior.
    • Tags:
    • Backlog priority:
      800
    • Sprint:
      nxcore 10.2.2, nxcore 10.2.3
    • Story Points:
      2

      Description

      Following NXP-17798, the local ACL is always at the end.
      This is due to this commit:
      https://github.com/nuxeo/nuxeo/commit/cc9b7c5a0f82c622025900341dab4f7f22e8d9a3

      This prevents any custom ACL to be at this position.
      For example, a customer in 6.0 has the following order:

      1. inherited
      2. local
      3. localGroup (the custom one)

      In 7.10 (and later versions) it gives the following:

      1. inherited
      2. localGroup (the custom one)
      3. local

      The code responsible for this is in ACPImpl but this cannot be overriden through a contribution.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day, 1 hour
                  1d 1h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.