[SERVER-80454] Remove x509 auth related code in shard merge. Created: 26/Aug/23  Updated: 29/Oct/23  Resolved: 29/Aug/23

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

Type: Task Priority: Major - P3
Reporter: Suganthi Mani Assignee: Suganthi Mani
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-80496 Remove tenantMigrationDisableX509Auth... Open
is related to SERVER-54085 Remove server parameter tenantMigrati... Closed
is related to SERVER-80412 Complete TODO listed in SERVER-54085 Closed
Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2023-09-04
Participants:

 Description   

Cloud is going to continue use keyFile auth for donor <-> recipient communication and have no intentions to transition to x509 auth. On top of it, our x509 auth code is already broken on tenant migration donor (Example: SERVER-69978 made changes to donor to use async rpc api, and not auth supported _recipientCmdExecutor)and shard merge recipient (backup cursor traffic). So, it's better to remove the dead code from Server to improve clarity. (See SERVER-54085 for additional info).

This will also help us to run tenant migration integration tests with auth config that's used in Serverless production.



 Comments   
Comment by Githook User [ 28/Aug/23 ]

Author:

{'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com', 'username': 'smani87'}

Message: SERVER-80454 Remove x509 auth related code in shard merge.
Branch: master
https://github.com/mongodb/mongo/commit/6c926973c3b4c0ec57cdde64cd67e64bcaed1944

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