KMS providers should allow all Nodejs TLS options

XMLWordPrintableJSON

    • Not Needed
    • 🔵 Done
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      Use Case

      Users are unable to configure TLS options for KMS requests beyond a hard-coded list of tlsCAFile, tlsCertificateKeyFile, and tlsCertificateKeyFilePassword (hard-coded in both TS, and enforced with runtime logic).  Users might want to provide other Nodejs supported TLS options to configure KMS requests.

       

      User Experience

      • With the exception of our "invalid TLS options" (hard-coded into the state machine), users should be able to provide any Node.js TLS option to configure TLS for KMS requests.

      Dependencies

      n/a.

      Risks/Unknowns

      None.

      Acceptance Criteria

      Implementation Requirements

      •  

      Testing Requirements

      • tbd

      Documentation Requirements

      n/a

      Follow Up Requirements

      n/a

            Assignee:
            Unassigned
            Reporter:
            Bailey Pearson
            None
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: