[SERVER-44385] root no longer has privileges to run setProfilingLevel on config/local dbs Created: 02/Nov/19 Updated: 27/Oct/23 Resolved: 05/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging, Security |
| Affects Version/s: | 4.0.7 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | aa aaaaa | Assignee: | Eric Sedor |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Hi, Dear mongo team!
The mongo version is v4.0.10 So I changed the version to v4.0.2 the problem go away. If this version's bug ? |
| Comments |
| Comment by aa aaaaa [ 06/Nov/19 ] |
|
Get it! Thank you so much ! Have a good day ! |
| Comment by Eric Sedor [ 05/Nov/19 ] |
|
Hi again 648813099@qq.com, This change in behavior occurred with The dbAdmin role includes the enableProfiler action. You can assign this role on the config db for a user if you truly need to enable profiling on the config db. Sincerely, |
| Comment by Eric Sedor [ 05/Nov/19 ] |
|
Hi 648813099@qq.com, It looks like this behavior changed starting in 4.0.7. We have reproduced, we are investigating, and we will get back to you if any questions come up. Note that in general, profiling on the config database should not be necessary. Sincerely, |