[SERVER-46498] Put X509 roles in AuthorizationManger's cache Key Created: 28/Feb/20 Updated: 29/Oct/23 Resolved: 03/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.5 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Jackson | Assignee: | Spencer Jackson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Security 2020-03-09 | ||||
| Participants: | |||||
| Description |
|
The results of authorization lookups are dependent on the Keys. Information in the X.509 certificates made available in the SSLPeerInfo may be used to alter the results. As such, it should be in the Key. |
| Comments |
| Comment by Githook User [ 03/Mar/20 ] |
|
Author: {'name': 'Spencer Jackson', 'username': 'spencerjackson', 'email': 'spencer.jackson@mongodb.com'}Message: |
| Comment by Githook User [ 03/Mar/20 ] |
|
Author: {'username': 'spencerjackson', 'name': 'Spencer Jackson', 'email': 'spencer.jackson@mongodb.com'}Message: |