[SERVER-54085] Remove server parameter tenantMigrationDisableX509Auth Created: 27/Jan/21  Updated: 27/Aug/23  Resolved: 24/Aug/23

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Cheahuychou Mao Assignee: [DO NOT USE] Backlog - Server Serverless (Inactive)
Resolution: Won't Do Votes: 0
Labels: pm-1791_non-cloud-blocking, pm-1791_other_required
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-54893 Make tenant_migration_recipient_rollb... Closed
Related
related to SERVER-80412 Complete TODO listed in SERVER-54085 Closed
related to SERVER-80454 Remove x509 auth related code in shar... Closed
is related to SERVER-54084 Add server parameter tenantMigrationD... Closed
Assigned Teams:
Serverless
Backport Requested:
v5.0
Sprint: Sharding 2021-05-17
Participants:

 Description   

SERVER-54084 adds tenantMigrationDisableX509Auth to allow Cloud to test tenant migration without setting x509 authentication. It should be removed once Cloud is ready to test tenant migration with x509 authentication.



 Comments   
Comment by Suganthi Mani [ 24/Aug/23 ]

Discussed with Cloud and closing it as won't do because Cloud has decided not use x509 auth for donor <-> recipient communication, instead continue to use keyFile auth (see this comment). This applies to legacy tenant migration and split/merge protocols.

For future reference, please note that although CLOUDP-85552 has done the automation support for X509 in donor <-> recipient communication, the control plan hasn't been addressed yet (CLOUDP-85552). However, CLOUDP-185580 will reverse the automation effort.

Comment by Suganthi Mani [ 03/Mar/23 ]

christopher.caplinger@mongodb.com or didier.nadeau@mongodb.com Could you one of you take a look at this ticket if you have time?

Generated at Thu Feb 08 05:32:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.