[SERVER-45300] mongokerberos should not fail if KRB5_CONFIG is unset Created: 26/Dec/19 Updated: 29/Oct/23 Resolved: 03/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Security |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Jackson | Assignee: | Adam Cooper (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Security 2019-01-13 |
| Participants: |
| Description |
|
On servers, the mongokerberos tool checks if the KRB5_CONFIG environment variable is set. If it is unset, it will fail. If it is set it will, instead of using consuming it, access the Kerberos configuration using the profile API. We should unconditionally consume the profile API without checking this variable. |
| Comments |
| Comment by Githook User [ 03/Jan/20 ] |
|
Author: {'name': 'Adam Cooper', 'email': 'adam.cooper@mongodb.com', 'username': 'super-cooper'}Message: |