[SERVER-37735] [3.6] Ensure the full logical session id is included in commands sent by the ShardingTaskExecutor Created: 24/Oct/18  Updated: 29/Oct/23  Resolved: 24/Oct/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.6.8
Fix Version/s: 3.6.9

Type: Bug Priority: Major - P3
Reporter: Blake Oler Assignee: Blake Oler
Resolution: Fixed Votes: 0
Labels: SWNA
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-36874 Fatal Assertion 40526 while migrating... Closed
Related
is related to SERVER-35323 sessionId matching ignores userId par... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2018-11-05
Participants:
Case:

 Description   

Some commands (including listCollections and listIndexes) forward the logical session id sent by the client. The client's logical session id will not include the information for the logged in user – the user information is collected from the operationContext on a mongos/mongod. If a command forwards the logical session id to a mongod without attaching the user information, the mongod will infer the system user instead of the logged in user.

This ticket will backport a section of SERVER-35323. With this section, the ShardingTaskExecutor will verify that the user information is included in any commands sent with a logical session id. The ShardingTaskExecutor will emplace the user information onto the command object if needed.



 Comments   
Comment by Githook User [ 24/Oct/18 ]

Author:

{'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}

Message: SERVER-37735 Ensure the full logical session id is included in commands sent by the ShardingTaskExecutor
Branch: v3.6
https://github.com/mongodb/mongo/commit/c23ef8117d14b50d560202c7d0c4ed0c8cb9948d

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