Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Service Arch
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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~~)

depends on

SERVER-81544 Track protocol=atlasproxy on client connections

Closed

duplicates

SERVER-81548 OpMsgRequest checks for expectPrefix in ValidatedTenancyScope OR command body

Closed

Assignee:: [DO NOT USE] Backlog - Service Architecture
Reporter:: Mathis Bessa (Inactive)
Participants:: [DO NOT USE] Backlog - Service Architecture, Mathis Bessa
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: Oct 03 2023 03:57:13 PM UTC
Updated:: Oct 04 2023 01:01:05 AM UTC
Resolved:: Oct 03 2023 04:31:57 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates