[SERVER-34952] Require validators for non-boolean server parameters Created: 11/May/18  Updated: 06/Dec/22  Resolved: 09/Dec/21

Status: Closed
Project: Core Server
Component/s: Usability
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Judah Schvimer Assignee: Backlog - Security Team
Resolution: Won't Do Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-34345 Make it easier to provide validation ... Closed
is related to DOCS-12039 Document valid values for cursorTimeo... Closed
is related to SERVER-30387 maxLogSizeKB parameter should only be... Closed
is related to SERVER-30388 ttlMonitorSleepSecs parameter should ... Closed
is related to SERVER-30389 Simple and generic way to restrict se... Closed
Assigned Teams:
Server Security
Participants:
Case:

 Description   

SERVER-34345 makes it easy to add validators for server parameters. We have many unvalidated server parameters which let users accidentally cause undefined behavior in their clusters.



 Comments   
Comment by Kevin Pulo [ 07/Jun/18 ]

See SERVER-30389 for a (slightly outdated) list of affected parameters. Also SERVER-30387 and SERVER-30388 are two specific cases.

Generated at Thu Feb 08 04:38:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.