-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: 8.0.0
-
Component/s: None
-
None
-
Server Security
-
ALL
-
- Downgrade to FCV to 7.0
- Run set_audit_config_direct.js
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
In the 8.0 branch, if a user starts a node at FCV 7.0, the feature flag AuditConfigClusterParameter is not enabled, which prevents the use of the new setClusterParameter command for audit config.
However, the legacy setAuditConfig command is also unavailable when the feature flag is enabled, and currently rejects execution even at FCV 7.0, due to the flag being implicitly active.
This results in a no-op state at FCV 7.0:
- Users cannot use the new audit config command (due to FCV < 7.1).
- And they cannot use the legacy command (due to the flag being treated as enabled at FCV 7.0, the feature flag check ignores the FCV).
The request is to revisit the validation logic inside setAuditConfig to allow legacy command use when setClusterParameter is not yet available.