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

Rename compliance mode as strict mode

    XMLWordPrintable

    Details

    • Type: User story
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2023.1, 2021.41
    • Component/s: Retention
    • Release Notes Summary:
      Nuxeo Retention compliance mode renamed as strict mode
    • Upgrade notes:
      Hide

      The nuxeo.conf property nuxeo.retention.compliance.enabled has been deprecated in favor of nuxeo.retention.strictmode.enabled.
      When both properties are configured, nuxeo.retention.strictmode.enabled takes precedence.

      Show
      The nuxeo.conf property nuxeo.retention.compliance.enabled has been deprecated in favor of nuxeo.retention.strictmode.enabled . When both properties are configured, nuxeo.retention.strictmode.enabled takes precedence.
    • Team:
      PLATFORM
    • Sprint:
      nxplatform #91, nxplatform #92

      Description

      Since NXP-31861, compliance with SEC-17A4 can be achieved using governance mode and the appropriate S3 bucket configuration. Keeping a mode called "compliance" makes it confusing.

      AC

      • Compliance mode is renamed to "strict" mode
      • nuxeo.conf property nuxeo.retention.compliance.enabled is deprecated
      • nuxeo.retention.compliance.enabled property is replaced with nuxeo.retention.strictmode.enabled (name change)
      • when both properties are configured, nuxeo.retention.strictmode.enabled takes precedence

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: