[DOCS-11453] Noscripting not available in Ops Manager 3.6 Created: 14/Mar/18 Updated: 29/Oct/23 Resolved: 02/May/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Ops Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Stephen Jamieson | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 5 years, 41 weeks ago |
| Epic Link: | DOCSP-1743 |
| Story Points: | 0.1 |
| Description |
|
In Ops Manager 3.6, noscripting is no longer available as an advanced option. Instead the option is security.javascriptEnabled. For 3.4, only noscripting is available. I believe the https://docs.opsmanager.mongodb.com/v3.6/reference/cluster-configuration-process-options/ page should be updated, however there may be more references to noscripting elsewhere. |
| Comments |
| Comment by Githook User [ 02/May/18 ] |
|
Author: {'email': 'tony.sansone@mongodb.com', 'name': 'Tony Sansone', 'username': 'atsansone'}Message: ( |
| Comment by Githook User [ 02/May/18 ] |
|
Author: {'email': 'tony.sansone@mongodb.com', 'name': 'Tony Sansone', 'username': 'atsansone'}Message: ( |