[SERVER-12559] GLE does not report auth failures for certain commands Created: 31/Jan/14  Updated: 10/Dec/14  Resolved: 14/Mar/14

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

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Spencer Brody (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-12419 mongos GLE does not work correctly if... Closed
Operating System: ALL
Participants:

 Description   

Other failures at the command level are probably also not reported. This leads to some inconsistency in that some errors are reported via GLE and others are not when using GLE after commands like dropCollection.

Non-regression.



 Comments   
Comment by Spencer Brody (Inactive) [ 14/Mar/14 ]

I am inclined to not fix this at all and leave it as-is. This is because
a) it's not a regression - no users can be relying on GLE reporting auth failures after commands, as they haven't ever in the past
b) This doesn't prevent using GLE for write concern after these commands
c) GLE is going away soon anyway, so it seems weird to add more dependencies on it now.

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