Details
-
Task
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
None
-
None
-
Service Arch
Description
As part of moving expectPrefix at the connection level for Atlas proxy connections, we should no longer accept `expectPrefix` from the body of the request since it should be coming from the security token (see SERVER-81544)
Attachments
Issue Links
- depends on
-
SERVER-81544 Track protocol=atlasproxy on client connections
-
- Closed
-
- duplicates
-
SERVER-81548 OpMsgRequest checks for expectPrefix in ValidatedTenancyScope OR command body
-
- Closed
-