-
Type: User story
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Retention
-
Release Notes Summary:Nuxeo Retention compliance mode renamed as strict mode
-
Epic Link:
-
Tags:
-
Upgrade notes:
-
Team:PLATFORM
-
Sprint:nxplatform #91, nxplatform #92
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
- is related to
-
NXP-32089 Strict Mode Set Up with both the flags
- Resolved
-
NXDOC-2605 Retention - Mention nuxeo.conf property for choosing the mode
- Resolved
-
NXP-31861 Retention - Object lock should follow AWS configuration
- Resolved
-
NXP-32090 Strict Mode Set Up with nuxeo.retention.strictmode.enabled=true
- Resolved