[SERVER-5847] Increase log level on authenticate commands done for internal authentication Created: 15/May/12  Updated: 06/Dec/22  Resolved: 30/May/19

Status: Closed
Project: Core Server
Component/s: Logging, Security
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Minor - P4
Reporter: Spencer Brody (Inactive) Assignee: Backlog - Security Team
Resolution: Done Votes: 9
Labels: neweng, platforms-re-triaged
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-5952 Remove authenticate messages from --q... Closed
Assigned Teams:
Server Security
Sprint: Server 2.7.5
Participants:

 Description   

When using authentication with replica sets or sharding, there is a lot of messages in the logs on the mongods that look like

Wed May  9 14:48:11 [conn241]  authenticate: { authenticate: 1, nonce:
"b489d14f5732414", user: "__system", key:
"7a6ad96f3a481312fe03e9ed5bf59ae5" }

These messages are from the internal authentication used for nodes and mongos to authenticate their connections to each other. We probably still want to log authentication requests from the user at the default log level, but the internal authentication messages just fill the logs with a lot of unnecessary noise.



 Comments   
Comment by Spencer Jackson [ 30/May/19 ]

My understanding is that these messages are both valuable and occur less frequently due to improvements in replication and networking. Because there have been no recent comments, I'm going to resolve as Gone Away. If anyone disagrees, please feel free to reopen.

Comment by Rob LaRubbio [ 16/May/12 ]

Is it possible to set a log level for user authentications? In our deployment we have a multi-tenant app that authenticates against the db frequently and not being able to disable the user auth messages causes a lot of noise in our logs.

Generated at Thu Feb 08 03:10:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.