[SERVER-74811] Use explicit tenantIds in change_stream_change_collection_role_auth.js Created: 13/Mar/23  Updated: 29/Oct/23  Resolved: 11/Sep/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Janna Golden Assignee: Sebastien Mendez
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-81027 Re-enable change_stream_cluster_param... Closed
Assigned Teams:
Query Execution
Backwards Compatibility: Fully Compatible
Sprint: QE 2023-05-15, QE 2023-05-29, QE 2023-06-12, QE 2023-06-26, QE 2023-07-24, QE 2023-08-07, QE 2023-08-21, QE 2023-09-04, QE 2023-09-18
Participants:

 Description   

The test change_stream_change_collection_role_auth.js enables the multitenancySupport server parameter, but it also uses the `internalChangeStreamUseTenantIdForTesting` flag to avoid needing to send tenantIds in the requests directly. PM-2346 is making it such that requests are required to contain a tenantId when running with multitenancySupport enabled. This test should send tenantIds in the requests (using either $tenant or a security token) rather than relying on `internalChangeStreamUseTenantIdForTesting` to inject tenantIds at lower layers in the server.



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

Author:

{'name': 'Sebastien Mendez', 'email': 'sebastien.mendez@mongodb.com', 'username': 'rakiz'}

Message: SERVER-74811 Use explicit tenantId in change_stream_change_collection_role_auth.js
Branch: master
https://github.com/mongodb/mongo/commit/bcb75057c7d66113d439ea75e99b922224e64aad

Comment by Janna Golden [ 15/Mar/23 ]

sebastien.mendez@mongodb.com - just a heads up that we're planning to temporarily disable this test in SERVER-73112, so this ticket should re-enable it if SERVER-73112 is completed first. Otherwise, if this is done first, I'll make sure we don't disable it.

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