[SERVER-33123] Mongos noscripting command line and configuration Created: 05/Feb/18 Updated: 29/Oct/23 Resolved: 22/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.4 |
| Type: | Bug | Priority: | Trivial - P5 |
| Reporter: | Stephen Jamieson | Assignee: | Benjamin Caimano (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Platforms 2018-03-26 |
| Participants: | |
| Case: | (copied to CRM) |
| Description |
|
mongos --help lists --noscripting as a valid parameter despite not being functional on a mongos. Tested with $where --help output:
running with --noscripting:
test with $where:
If security.javascriptEnabled is in the configuration file for the mongos, the following error blocks startup.
When security.javascriptEnabled is set on a shard, the option functions as expected.
Tested against 3.4.10 and 3.6.2. I will file a docs ticket if this option should not be allowed on a mongos. |
| Comments |
| Comment by Githook User [ 24/Jul/18 ] |
|
Author: {'name': 'Asya Kamsky', 'email': 'asya999@gmail.com', 'username': 'asya999'}Message: Mongos does not support --noscripting see https://jira.mongodb.org/browse/SERVER-33123 |
| Comment by Githook User [ 22/Mar/18 ] |
|
Author: {'email': 'ben.caimano@10gen.com', 'name': 'Ben Caimano'}Message: Hid --noscripting, added and hid security.javascriptEnabled, warned on |
| Comment by Benjamin Caimano (Inactive) [ 16/Mar/18 ] |
|
It appears that `--noscripting` is explicitly unsupported in the `mongos` source code. I'll be looking into suppressing the argument in the help. Additionally, I'll try to make the parameter in the configuration warn instead of block. |