Remove x509 auth related code in shard merge.

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Server Serverless 2023-09-04
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Suganthi Mani
            Reporter:
            Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: