[SERVER-11835] mongod starts with invalid (non-existent) saslauthdPath Created: 22/Nov/13 Updated: 06/Dec/22 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | None |
| Fix Version/s: | features we're not sure of |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Adinoyi Omuya | Assignee: | Backlog - Security Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Security
|
| Participants: |
| Description |
|
On an enterprise build, try: mongod --setParameter saslauthdPath=/invalid/saslauthdPath should throw an error but starts without any error/warning. |
| Comments |
| Comment by Adinoyi Omuya [ 22/Nov/13 ] |
|
I think it's helpful to let the user know that the path specified doesn't exist since subsequent attempts to authenticate would fail with an invalid path. |
| Comment by Andy Schwerin [ 22/Nov/13 ] |
|
saslauthd may be started and restarted independently of mongod. Why enforce the order in which the two are started? |