Uploaded image for project: 'Ratis'
  1. Ratis
  2. RATIS-1747

Support keyManager and trustManager in tlsConfig

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.0.0, 2.5.0
    • security
    • None

    Description

      Ratis use the security materials passed by Ozone to establish tls connection. Currently, there are two ways to configure tls. For cert, one is cert file based, another is  cert objects. For privateKey, one is private key file, another is  private key object.

       

      This task aims to support the third way to configure tls. That is, pass in a KeyManager and trustManager object for key and cert.  The motivation of this is we want to support certificate dynamic reloading in Ozone when certificate is going to expire and a new certificate is generated to replace the old one.

      Attachments

        1. 785_review.patch
          30 kB
          Tsz-wo Sze

        Issue Links

          Activity

            People

              Sammi Sammi Chen
              Sammi Sammi Chen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 2.5h
                  2.5h