[SERVER-80635]  Use AuthPrevalidated for auth-specific de/serialization Created: 31/Aug/23  Updated: 29/Oct/23  Resolved: 26/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: Hugh Tong (Inactive) Assignee: Hugh Tong (Inactive)
Resolution: Fixed Votes: 0
Labels: ntdi_must_have
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-74896 Remove NamespaceString::createNamespa... Closed
depends on SERVER-81035 Create catalog-specific deserializer ... Closed
is depended on by SERVER-73113 Allow only specific global dbs to be ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2023-09-18, Server Serverless 2023-10-02
Participants:

 Description   

A number of call sites are left that de/serialize in non-standard ways.  Auth has special requirements for de/serialization that may not necessarily be used to access a tenant-scoped namespace, for example creating initial users without tenantIds, creating certificates for auth commands, or pattern matching.

We should use the AuthPrevalidated serialization context built in SERVER-74896 (built for pattern matching) wherever we are de/serializing for auth-specific functionality.



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

Author:

{'name': 'Hugh Tong', 'email': 'hugh.tong@mongodb.com', 'username': 'cortrain'}

Message: SERVER-80635 Use AuthPrevalidated for auth-specific de/serialization
Branch: master
https://github.com/mongodb/mongo/commit/337b3a9ab5cd69e8a0bb411097dd7a0d29342d8b

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