noscripting configuration option not available in YAML configuration file

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.6.2, 2.7.1
    • Affects Version/s: 2.6.0
    • Component/s: Admin
    • None
    • Fully Compatible
    • ALL
    • Server 2.7.1
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Issue Status as of May 29, 2014

      ISSUE SUMMARY
      Server-side execution of JavaScript can't be disabled via a YAML configuration file, as the noscripting option is not properly recognized.

      USER IMPACT
      mongod does not run when the noscripting option is used in a YAML format configuration file. When the option is removed from the file, mongod runs with server-side JavaScript execution enabled.

      WORKAROUNDS
      Pass the --noscripting option, or revert to a 2.4 configuration file format

      AFFECTED VERSIONS
      MongoDB production releases 2.6.0 and 2.6.1 are affected by this issue.

      FIX VERSION
      The fix is included in the 2.6.2 production release.

      RESOLUTION DETAILS
      The noscripting option is now recognized when used in the YAML configuration file.

      Original description

      There's no way to disable server-side JavaScript using the new YAML configuration file format.

            Assignee:
            Shaun Verch (Inactive)
            Reporter:
            Jon Rangel (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: