[SERVER-9161] Clean up constants used in security code Created: 28/Mar/13 Updated: 06/Dec/22 Resolved: 01/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, Security |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Backlog - Security Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | neweng, platforms-re-triaged | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Security
|
| Participants: |
| Description |
|
We have constants defined in several places (for example some in authorization_manager.h and others in sasl_client_authenticate.h - even though some of those in sasl_client_authenticate.h aren't sasl-specific). We also have some constants that are duplicates. We just need to generally clean up our constants in the security system. See http://codereview.10gen.com/10014028/ for one example of using constants from SASL code outside of SASL code. |