[SERVER-17507] MongoDB3 enterprise AuditLog Created: 07/Mar/15 Updated: 18/Sep/15 Resolved: 09/Mar/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | 3.0.0 |
| Fix Version/s: | 3.0.1, 3.1.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cory Morales | Assignee: | Amalia Hawkins |
| Resolution: | Done | Votes: | 0 |
| Labels: | ET, MTC | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Completed: | |||||||||
| Steps To Reproduce: | 1. In your mongoDB config yaml set up audit logging like so ' 2.) db.auth('','') with incorrect credentials and see that the failure is not logged in the AuditLog like it was before |
||||||||
| Sprint: | Security 1 04/03/15 | ||||||||
| Participants: | |||||||||
| Description |
|
The AuditLog is not logging authentication failures in 3.0 enterprise and only logging the successes. This was working fine in version 2.6 enterprise. |
| Comments |
| Comment by Githook User [ 09/Mar/15 ] |
|
Author: {u'username': u'hawka', u'name': u'Amalia Hawkins', u'email': u'amalia.hawkins@10gen.com'}Message: (cherry picked from commit cb126b88afd72a2bcfa225e21870f7eaa4fffc9d) |
| Comment by Amalia Hawkins [ 09/Mar/15 ] |
|
Thanks for bringing this to our attention! |
| Comment by Githook User [ 09/Mar/15 ] |
|
Author: {u'username': u'hawka', u'name': u'Amalia Hawkins', u'email': u'amalia.hawkins@10gen.com'}Message: |