Test Atlas Connectivity with server cert missing clientAuth EKU

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Networking, Security
    • None
    • Hide

      Summary of necessary driver changes

      • For the latest version of each driver, run a findOne-style test against an Atlas cluster with a new cert (no clientAuth EKU) on each supported operating system (Linux, Mac, Windows).
      • git blame each driver's TLS impl to look for changes in recent memory and test earlier versions as needed. Additional testing is required if client metadata metrics indicate 5%+ usage and that version's TLS code is different than latest.
      Show
      Summary of necessary driver changes For the latest version of each driver, run a findOne -style test against an Atlas cluster with a new cert (no clientAuth EKU) on each supported operating system (Linux, Mac, Windows). git blame each driver's TLS impl to look for changes in recent memory and test earlier versions as needed. Additional testing is required if client metadata metrics indicate 5%+ usage and that version's TLS code is different than latest.
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This ticket was split from DRIVERS-3424, please see that ticket for a detailed description.

            Assignee:
            Unassigned
            Reporter:
            TPM Jira Automations Bot
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: