[SERVER-5083] Include database name in auth log message Created: 24/Feb/12 Updated: 03/Jan/18 Resolved: 17/May/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging, Security |
| Affects Version/s: | 2.0.2 |
| Fix Version/s: | 2.1.2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jared D. Cottrell | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| Description |
|
It would be useful to include the database name in auth log messages. For example, if we have a user "someuser" in the database "somedb", the log message would currently read (2.0.3-rc1): authenticate: { authenticate: 1, nonce: "abcd1234", user: "someuser", key: "abcd1234abcd1234" }That might become: authenticate: { authenticate: 1, nonce: "abcd1234", db: "somedb", user: "someuser", key: "abcd1234abcd1234" }or maybe: authenticate: { authenticate: 1, nonce: "abcd1234", user: "somedb.someuser", key: "abcd1234abcd1234" } |
| Comments |
| Comment by auto [ 17/May/12 ] |
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: |
| Comment by Eliot Horowitz (Inactive) [ 24/Feb/12 ] |
|
doesn't make sense to change the document as you suggest, but could easily add to log message |