[SERVER-32086] Suppress LDAP user cache invalidation log message by default Created: 27/Nov/17  Updated: 30/Oct/23  Resolved: 26/Jan/18

Status: Closed
Project: Core Server
Component/s: Security
Affects Version/s: None
Fix Version/s: 3.4.11, 3.6.3, 3.7.2

Type: Improvement Priority: Major - P3
Reporter: Spencer Jackson Assignee: Mark Benvenuto
Resolution: Fixed Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.6, v3.4
Sprint: Platforms 2018-01-29
Participants:
Case:

 Description   

Currently, the server flushes the LDAP user cache on a periodic basis, and emits a log message.

Invalidating user cache entries of external users

Because the period may be short, we should put this on a non-default log level.



 Comments   
Comment by Githook User [ 26/Jan/18 ]

Author:

{'name': 'Mark Benvenuto', 'username': 'markbenvenuto', 'email': 'mark.benvenuto@mongodb.com'}

Message: SERVER-32086 Suppress LDAP user cache invalidation log message by default

(cherry picked from commit 014b60425ab21830a7914e64b414e10657c9bee7)
Branch: v3.4
https://github.com/10gen/mongo-enterprise-modules/commit/eacb111e4a0a5c849981e239bd82d2fd1efffbd7

Comment by Githook User [ 26/Jan/18 ]

Author:

{'name': 'Mark Benvenuto', 'username': 'markbenvenuto', 'email': 'mark.benvenuto@mongodb.com'}

Message: SERVER-32086 Suppress LDAP user cache invalidation log message by default

(cherry picked from commit 014b60425ab21830a7914e64b414e10657c9bee7)
Branch: v3.6
https://github.com/10gen/mongo-enterprise-modules/commit/278cdb188c349c24dd60f30d5fe4f496064af6a6

Comment by Githook User [ 26/Jan/18 ]

Author:

{'name': 'Mark Benvenuto', 'username': 'markbenvenuto', 'email': 'mark.benvenuto@mongodb.com'}

Message: SERVER-32086 Suppress LDAP user cache invalidation log message by default
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/014b60425ab21830a7914e64b414e10657c9bee7

Comment by krishna kotaru [ 29/Dec/17 ]

Please fix this in future releases

Generated at Thu Feb 08 04:29:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.