[SERVER-15360] User document changes made on a 2.4 primary and replicated to a 2.6 secondary don't make the 2.6 secondary invalidate its user cache Created: 23/Sep/14  Updated: 02/Feb/15  Resolved: 23/Sep/14

Status: Closed
Project: Core Server
Component/s: Security
Affects Version/s: 2.6.5
Fix Version/s: 2.6.5

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-14887 Allow user document changes made on a... Closed
Tested
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

User document changes made to non-admin system.users collections don't get detected as affecting authorization data and thus the user cache is not invalidated, leading to stale user definitions on the secondary



 Comments   
Comment by Githook User [ 23/Sep/14 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-15360 Make sure user cache is invalidated on 2.6 secondaries replicating from a 2.4 primary
Branch: v2.6
https://github.com/mongodb/mongo/commit/e9cc37d2b51cc63e907be8d76be5feff08113b35

Comment by Spencer Brody (Inactive) [ 23/Sep/14 ]

Fix is 2.6-only, as we don't support replicating from 2.4 in 2.8

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