[SERVER-54254] Make internalSecurity global a ServiceContext decoration Created: 03/Feb/21 Updated: 30/Apr/21 Resolved: 30/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Benjamin Caimano (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Sprint: | Security 2021-03-08, Security 2021-03-22, Security 2021-04-05, Security 2021-04-19, Security 2021-05-03 | ||||
| Participants: | |||||
| Description |
|
We have a global variable called internalSecurity declared here and initialized here. Given that this has to be used with either storage or the network (and thus a ServiceContext), we should convert it to be a ServiceContext decoration. There might be an opportunity to consolidate it into the AuthorizationManager as well, since it is already a decoration. |